mod_lsapi
Flood of 503 Service Temporarily Unavailable Errors on Many Sites
Collapse
X
-
After enabling mod_lsapi most of the sites on the server are throwing 503 temporarily unavailable errors. Checking the CloudLinux stats in cPanels web host manager all the user accounts given a hefty amount and not are hitting their thresholds. Checking the Apache error_log file I am seeing flooding of the following error:
[Wed Jan 14 23:23:54 2015] [error] [client xxx.xxx.xxx.xxx] mod_lsapi: [host http://www.adomain.com] Could not connect to lsphp backend: connect to lsphp failed: 2 No such file or directory
[Wed Jan 14 23:23:54 2015] [error] [client xxx.xxx.xxx.xxx] mod_lsapi: [host http://www.adomain.com] Could not stat script filename (/home/username/public_html/index.php): errno 2
What would cause this ? All these sites load perfectly fine with ruid2 but I would like to use the memory limits and cagefs of CloudLinux.
Thank you. -
Hello,
looks like that mod_lsapi can access to target php file. Can you write to helpdesk of CloudLinux? We need to investigate the trouble more detail (we need to check config files for vhost and mod_lsapi and rights for scripts).Comment
-
> Could not connect to lsphp backend: connect to lsphp failed: 2 No such file or directory
Does the following directory exist? /tmp/lshttpd
Code:stat /tmp/lshttpd
Comment
Comment