Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:php:503-errors [2018/10/02 15:47]
Lisa Clarke [Misconfiguration of lsphp external application] Proofread
+++ litespeed_wiki:php:503-errors [2019/01/25 15:40]
Jackson Zhang
@@ Line 199: / Line 199: @@
 ==== CloudLinux Limits Reached =====
-For CloudLinux users, if a site is limited by either the amount of memory or the number of processes, then the user will receive 503 errors because the server cannot execute the script. Increasing the limits on memory and number of processes for that CageFS user may fix the problem.
+For CloudLinux users, if a site is limited by either the amount of memory or the number of processes, then the user will receive 503 errors because the server cannot execute the script. Increasing the limits on memory and number of processes for that CageFS user may fix the problem. To understand why LVE may cause such error, please refer to [[https://docs.cloudlinux.com/index.html?lve.html|CloudLinux LVE documentation]].
+  If the site is limited by CPU or IO, then the site will start responding slower.
+  If the site is limited by memory or number of processes limits, then the user will recieve 500 or 503 errors that server cannot execute the script.
 ==== PHP memory_limit reached ====
@@ Line 343: / Line 347: @@
 After (re)installation of LiteMage Cache extension in Magento Connect manager or enable other modules in Magento 2, Magento site may be placed in maintenancence mode and couldn't be accessed and may give 503 errors.  Please refer [[litespeed_wiki:cache:litemage:troubleshooting:connect-cache-session-cleaning-error|this]] for details.
+==== CloudLinux Imunify360 error ====
+Check ''stderr.log''. It shows:
+<code>
+  *** Error in 'lsphp:/home/ukrainia/public_html/index.php': malloc(): memory corruption (fast): 0x00007fa380d45e40 ***
+  ======= Backtrace: =========
+  /lib64/libc.so.6(+0x7f574)[0x7fa37c07f574]
+  /lib64/libc.so.6(+0x82c90)[0x7fa37c082c90]
+  /lib64/libc.so.6(__libc_malloc+0x4c)[0x7fa37c0857dc]
+  /opt/cpanel/ea-php54/root/usr/lib64/php/modules/i360.so(+0xb80b)[0x7fa375fbe80b]
+  /opt/cpanel/ea-php54/root/usr/lib64/php/modules/i360.so(map_increment_int_+0xa2)[0x7fa375fbeaa2]
+</code>
+If you try the following:
+**/opt/cpanel/ea-php54/root/usr/lib64/php/modules>** ''mkdir backup''
+**/opt/cpanel/ea-php54/root/usr/lib64/php/modules>** ''mv i360.so backup/''
+**/opt/cpanel/ea-php54/root/usr/lib64/php/modules>** ''ls -l i360.so backup/''
+You will get this result:
+  ls: cannot access i360.so: No such file or directory
+  backup/:
+  total 88
+  -rwxr-xr-x 1 root root 86568 Nov 15 12:37 i360.so
+The issue is fixed by disabling CloudLinux's ''i360.so''. This is a CloudLinux bug. Please be aware that it may have been fixed by the CloudLinux team by the time you read this wiki, but it was a cause of 503 errors at one time.
 ===== Advanced Troubleshooting Guide =====
@@ Line 442: / Line 475: @@
 This backtrace shows us that the program crashed soon after accessing the opcode cache. This suggests that the issue is with the opcode cache. The user can then try upgrading the opcode cache or changing their PHP version. If neither of those work, the user should try to disable the opcode cache.
+===== LSWS ''Auto Fix 503 Error'' feature =====
+In LSWS Admin Console, there is a feature ''Auto Fix 503 Error''. It specifies whether to try to fix the "503 Service Unavailable" error by restarting the server gracefully. A "503" error is usually caused by malfunctioning external applications and a web server restart can often fix the error temporarily. If enabled, the server will restart automatically whenever there are more than 30 "503" errors within a 30 seconds span. This feature is enabled by default and you can disable it from LSWS Admin -> Server -> General -> Auto Fix 503 Error -> No.
+{{ :litespeed_wiki:php:auto-fix-503-error.png?800 |}}
+''Auto Fix 503 Error'' is not a permanate fix, but only a tmp fix by restarting Web Server. You should not reply this feature to fix the 503 errors, and going through the above steps to find a permanate fix is always recommended.
 ===== Real World Examples =====