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 [2018/11/19 14:57]
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>
+then
+  /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/
+  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. Please be aware that the bug could have been fixed by CloudLinux team when the time you read this wiki but it used to be a case to cause 503 error.
 ===== Advanced Troubleshooting Guide =====