PHP suEXEC Max Conn should always be set to a value that is less than the CloudLinux user account EP limit. If the PHP suEXEC Max Conn limit is reached, another php connection will be created. Under normal circumstances, this value should not exceed 50. In these cases, LSWS might return 500 or 503 errors.įor shared hosting environments, PHP suEXEC Max Conn should not be set too high. When that happens, the NPROC counter is incremented. Once the limit is reached, no new processes can be created (until another one dies). NPROC controls the total number of processes within an LVE.
Limits on entry processes(EP) control the number of entries into an LVE. The limit will be 4x for a Web Host Enterprise license, and so on.
#LITESPEED WEB SERVER A2HOSTING PROFESSIONAL#
Thus, if you have a Web Host Professional license, this limit will be doubled. This limit is per user per lshttpd process. PHP suEXEC Max Conn is a LiteSpeed Web Server setting which specifies the maximum number of concurrent PHP processes that can be created by LSWS for each user when running PHP scripts in suEXEC mode. If the site has limits set on memory or its number of processes, then the user will receive 500 or 503 errors that the server cannot execute the script. If the site is limited by CPU or IO, then the site will start responding slower. This results in very heavy sites slowing down and returning 508 errors without impacting other users. If the limit is reached, then mod_hostinglimits will not be able to place web server processes into the LVE and will return a 508 error. LVE is a kernel-level technology developed by the CloudLinux team.Įach LVE limits the amount of entry processes (web server processes entering into the LVE) to prevent a single site exhausting all web server processes.
LiteSpeed Web Server's PHP suEXEC Max Conn setting should always be set to a value less than the CloudLinux LVE EP limit.
#LITESPEED WEB SERVER A2HOSTING UPDATE#
The first trouble-shooting step when CageFS is used, is to force update the cage, and turn off/on CafeFS for that user. If Zend Opcache has a permission issue, other opcode cache may have it as well.Ĭheck if the CloudLinux CageFS was setup correctly since other users do not have the same error.Īfter remounting CageFS, the website works fine. If process 18989 does get the same error, it is definitely an issue relating to opcache. 17:28:51.070 Wed May 27 17:28:51 2015 ( 19046 ): Fatal Error Unable to create lock file: Bad file descriptor ( 9 ) These are from another process. 17:28:51.069 Unable to create lock file: Permission denied LiteSpeed Memcached LiteSpeed Memcached.LSCache Developers Guide LSCache Developers Guide.LSCache Without a Plugin LSCache Without a Plugin.Avoid app frequently stopping and starting.CloudLinux CloudLinux Table of contents.WHM LiteSpeed Plugin WHM LiteSpeed Plugin.External Applications External Applications.LiteSpeed Web Server LiteSpeed Web Server.
0 kommentar(er)
