WHM plugins problem

Are you logged-in to WHM via a username of "root" (i.e., the server administrator), or are you logged-in to WHM via a reseller username (any username other than "root")? Please note that certain plug-ins may only be accessible when logged-in as "root" (i.e., the server administrator).

If you have root SSH access, please check the following log files:

Code:

/usr/local/cpanel/logs/access_log
/usr/local/cpanel/logs/error_log

Via root SSH access, the following command may be used to monitor the aforementioned log files for new entries while accessing the plug-ins via WHM to trigger any possible error or related informational messages:

Code:

# tail -fvn0 /usr/local/cpanel/logs/access_log /usr/local/cpanel/logs/error_log

 

The information posted by thewebhosting is not accurate; please note the following corrections and clarification:

• Given the provided access URL for WHM one can know it does not involve Apache because the cPanel/WHM port number is explicitly defined in the address; Apache would only be involved if both the port number is not explicitly defined in the URL and if a proxy sub-domain is used for access (e.g., "whm.domain.tld").
• The suggested log file path is not of Apache but rather it is for the Exim MTA, that is, the SMTP mail server.
• The correct location of the Apache error log is at the following file system path:
  
  Code:

  /usr/local/apache/logs/error_log

• To elaborate further, the individual per-domain Apache access logs are stored in the following directory:
  
  Code:

  /usr/local/apache/domlogs/

 

Depending on how in-depth or how complex the issue may be; if there is a future problem with Perl scripts or modules I would suggest trying the following command via root SSH access to perform a general check as a possible corrective measure:

Code:

# /scripts/checkperlmodules --full

If that alone does not fix it and if the issue involves a missing Perl module; here is an example of what to look for and how to attempt a correction. Please note the Perl module name may be different; in this case I used an example based on something that could be seen if there is a missing Perl module when attempting to run EasyApache via root SSH access.

Example error detail, indicating a possible missing Perl module:

Code:

Can't locate Acme/Spork.pm in @INC

Example command to confirm the existing module version or see if it might be missing:

Code:

# /scripts/perlmods -l | grep -ai "Acme::Spork"

Example corrective measure:

Code:

# /scripts/perlinstaller Acme::Spork

Example corrective measure (with optional "force" switch):

Code:

# /scripts/perlinstaller --force Acme::Spork