Use the following command to strace the PHP process to find out what happened: You likely need some knowledge and experience to understand what the log entries mean it can even be a challenge locating the relevant sections of the log. Just be prepared that the strace log may be extremely long and overwhelming. If there is a core file generated and you've tried all of the above methods without finding a solution, try to strace the PHP process for a hint. Reporting the bug to PHP is an option, but a solution may not be provided in a timely manner. You can disable the module or change to another PHP version without the bug. Even if you find an internal PHP bug causing the crash, there are limited actions you can take. If PHP crashes, you can enable a core dump and use GDB to debug the core file. The comprehensive guide above lists the most likely reasons you'd receive a 503 error, but in some circumstances, it may be difficult to locate the root cause. Now you should no longer see a 503 error because LSPHP can open more files on your system. If it does kill the process you may receive an email or an entry in /var/log/lfd.log with the following message: If a LSPHP process takes too long to complete it is possible that the PT_USERTIME feature will be called to kill the process. CSF/LFD has two settings that can kill a LSPHP process: PT_USERTIME and PT_FORKBOMB. These programs may be killing the process before it finishes. If you have CSF/LFD installed they may be causing the 503 error. If the stderr.log does not provide any insight then you can try to increase the max execution time by following the steps in the Control guide. These errors will often be explained in your stderr.log. If you have a max execution time that is not high enough to handle long running requests then you may get the following error in your web server error log: error: Connection reset by peer! and have a value of 0, meaning that the process never finished the request. Now that everything has been set up, navigate to Actions and press the icons next to Restart Detached PHP Processes.Change the following settings, then click Save.Now click Edit for PHP Handler Defaults.Next, navigate to Configuration > Server > PHP.Go to your Web Admin console ( ) and log in.If you have increased the memory limit in php.ini and confirmed you are not hitting a LVE limit then it is possible LSPHP needs to increase its virtual memory. To adjust the limits follow CloudLinux's guide. Here shows accounts that have hit a limit, depending on what limit the account has hit you should adjust the limit.
If you are running CloudLinux and Lightweight Virtual Environment (LVE) it is possible that you are hitting the limits set by that account. You can add/delete/modify this line inside of your. LiteSpeed cPanel Administrator's Handbook - LiteSpeed Documentation
0 kommentar(er)
