Differences

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

--- litespeed_wiki:php:503-errors [2018/11/19 14:54]
Jackson Zhang [Magento 503 error]
+++ litespeed_wiki:php:503-errors [2020/02/11 14:26] (current)
Jackson Zhang [Magento 503 error]
@@ Line 344: / Line 344: @@
   - Comment out the ''extension_dir'' line to let PHP pick a default.
+==== ''Too many open files'' error may cause 503 error ====
+If you found there are a lot of ''Too many open files!'' errors, which cause 503 errors.
+<code>
+  grep "Too many open files" error_log
+-08-01 21:58:03.511076 [INFO] [319934] [157.33.150.151:49873-1#APVH_pcrm.lidopiegade.lv:lsapi] connection to [uds://tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock] on request #0, confirmed, 0, associated process: 0, running: 0, error: Too many open files!
+-08-01 21:58:03.511078 [INFO] [319934] [uds://tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock] Connection error: Too many open files, adjust maximum connections to 4!
+-08-01 21:58:03.511085 [NOTICE] [319934] [APVH_lidopiegade_Sulsphp56:]: Failed to open pid file [/tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock.pid]: Too many open files
+-08-01 21:58:03.511087 [ERROR] [319934] [APVH_lidopiegade_Sulsphp56:]: Failed to lock pid file for [/tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock]: Too many open files
+-08-01 21:58:03.809177 [ERROR] [319934] [HTAccess] Failed to open [/home/zazzybab/public_html/girls/shannon-stewart/.htaccess]: Too many open files
+-08-01 21:58:03.810914 [ERROR] [319934] [46.51.216.186:63901] /home/zazzybab/public_html/girls/shannon-stewart/shannon-stewart-playboy-33645.jpg: open() failed, 24:Too many open files
+-08-01 21:58:05.072915 [NOTICE] [319934] [APVH_lidopiegade_Sulsphp56:]: Failed to open pid file [/tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock.pid]: Too many open files
+-08-01 21:58:05.072918 [ERROR] [319934] [APVH_lidopiegade_Sulsphp56:]: Failed to lock pid file for [/tmp/lshttpd/APVH_lidopiegade_Suea-php56.sock]: Too many open files
+-08-01 21:58:05.072932 [NOTICE] [319934] [APVH_birkenfelds_Sulsphp56:]: Failed to open pid file [/tmp/lshttpd/APVH_birkenfelds_Suea-php56.sock.pid]: Too many open files
+-08-01 21:58:05.072934 [ERROR] [319934] [APVH_birkenfelds_Sulsphp56:]: Failed to lock pid file for [/tmp/lshttpd/APVH_birkenfelds_Suea-php56.sock]: Too many open files
+-08-01 21:58:05.072949 [NOTICE] [319934] [APVH_vairaksaules_Sulsphp56:]: Failed to open pid file [/tmp/lshttpd/APVH_vairaksaules_Suea-php56.sock.pid]: Too many open files
+-08-01 21:58:05.072951 [ERROR] [319934] [APVH_vairaksaules_Sulsphp56:]: Failed to lock pid file for [/tmp/lshttpd/APVH_vairaksaules_Suea-php56.sock]: Too many open files
+</code>
+You may want to check the current ulimit:
+  ulimit -n
+you may consider to increase to a much higher value like:
+  ulimit -n 3276800
+Check [[litespeed_wiki:config:increasing-os-file-descriptor-limit|this wiki]] for details.
 ==== Magento 503 error ====
 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.
+==== Some buggy application plugin may cause 503 error ====
+Some buggy application plugin, such as WordPress sportspress plugin used to cause 503 errors. Uninstall all or most of WordPress or other applications' plugins, then installing them back one by one may be a good approach to locate the problematic plugin.
 ==== CloudLinux Imunify360 error ====
-check stderr.log, it shows:
-  *** Error in `lsphp:/home/ukrainia/public_html/index.php': malloc(): memory corruption (fast): 0x00007fa380d45e40 ***
+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]
@@ Line 356: / Line 388: @@
   /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
+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:
-  /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/:
@@ Line 367: / Line 405: @@
   -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.
+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.
+==== Plesk 503 error ====
+Some versions of Plesk PHP, such as php71 and php56, have a buggy APCu module that may cause a 503 error on LSWS. Generally, only one object cache or value cache should be enabled. Enabling two or more may cause conflicts between modules.  Disabling the APCu module should fix the problem.
+Navigate to **Plesk Admin > Tools and configuration > PHP configuration > 7.1.x FastCGI application**. Unselect ''apcu'' and press the **TO ACCEPT** button.
+{{ :litespeed_wiki:php:plesk-503-disable-apcu.png?800 |}}
+==== CPanel WebDisk 503 Errors ====
+You might see some errors like the following:
+-03-12 12:14:00.324041 [INFO] [51.68.79.11:54920:proxy] connection to [127.0.0.1:2077] on request #1, confirmed, 0, associated process: 0, running: 0, error: Connection refused!
+-03-12 12:14:00.324165 [INFO] [51.68.79.11:54920:proxy] connection to [127.0.0.1:2077] on request #1, confirmed, 0, associated process: 0, running: 0, error: Connection refused!
+-03-12 12:14:00.324194 [NOTICE] [51.68.79.11:54920:proxy] Max retries has been reached, 503!
+-03-12 12:14:00.324206 [INFO] [http://127.0.0.1:2077] request force stop: too many 503 errors
+Check ''/etc/apache2/conf/httpd.conf'':
+   ProxyPass "/___proxy_subdomain_webdisk" "http://127.0.0.1:2077" max=1 retry=0
+The errors are coming from cPanel WebDisk service. If this service generates too many 503 errors, you might consider disabling it. To disable cPanel WebDisk, you can log into WHM and disable **cPanel DAV Daemon** in the **Service Manager**.
+==== chroot is Enabled in LSWS =====
+It is not recommended to use ''chroot'' at all. If enabled, it may lead to a 503 error. To fix the problem, in the LiteSpeed Web Server WebAdmin Console, navigate to **Server > General** and set **Enable chroot** to ''No''.
 ===== Advanced Troubleshooting Guide =====
@@ Line 466: / Line 526: @@
 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.
+===== The "Auto Fix 503 Error" Feature =====
+In LiteSpeed Web Server's WebAdmin Console, there is a feature to **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 **Auto Fix 503 Error** is set to ''Yes'', the server will restart automatically whenever there are more than 30 "503" errors within a 30 seconds span. This feature is enabled by default, but you can disable it by navigating to **LSWS Admin -> Server -> General** and setting **Auto Fix 503 Error** to ''No''.
+{{ :litespeed_wiki:php:auto-fix-503-error.png?800 |}}
+**Auto Fix 503 Error** is not a permanent fix. You should not rely on this feature to fix recurring 503 errors. Going through the above steps to find a permanent fix is always recommended.
 ===== Real World Examples =====