kernel: LVE: Can’t enter to lve from slave context

These kind of error can be seen in /var/log/messages in a cpanel cloudlinux based server which will be filling the /var/log/messages quickly.

This can be caused due to below reasons :

1. You are running php as CGI and if that is the case, you can ignore this error and you can get this fixed by simply upgrading to the latest LVE kernel.

2. This happens due to conflict between mod_hostinglimits and mod_fcgid . In such cases, try disabling the mod_hostinglimits and see if that resolves the issue. If it fixes the issue, then

Edit “/usr/local/apache/conf/modhostinglimits.conf” and remove the handlers which are handled by mod_fcgid.

(I simply commented the AllowedHandlers line completely which stopped those errors)

Read more

Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp

The other day we faced an issue with the memory and the exact error was can be described as below:

[Mon Sep 30 10:00:29 2013] [error] [client 117.196.128.34] (12)Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/unier/public_html/index.php
[Mon Sep 30 10:00:29 2013] [error] [client 117.196.128.34] File does not exist: /home/unier/public_html/500.shtml

On the first look, we should check the Apache conf for any memory limits set  in the Apache configuration file.  You can check this using the below command

# grep RLimitMEM /usr/local/apache/conf/httpd.conf

If you are seeing any result like the below one,  try disabling or removing the line in the httpd.conf file, and restarting Apache.

Read more

SecurityException in Application.cpp:175: Calling user is not webserver user / SuPHP / cPanel

We were ended-up in this message after running EasyApache on one of our cPanel servers with mod_suphp. If we set the PHP handler to DSO, PHP applications were working fine; but when we try to switch the handler to SuPHP it started showing the above error message with 500 error code.

The actual cause for this error is given in the messsage in fact, which is “Calling user is not webserver user”. As per the security standards of SuPHP, the user invoking SuPHP must be defined in suphp.conf file and should match the user invoking it. So for a cPanel server, it should be call by the HTTP user which is “nobody”. In our case it was set to “apache” even there is no active “apache” user on a cPanel server. I met this error on a latest cPanel build; so I guess this is a bug with their latest EA3. To correct the issue, I set the value of “webserver_user” to “nobody” in /opt/suphp/etc/suphp.conf and restarted apache service.

Read more