Differences

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

--- litespeed_wiki:config:understanding_500 [2018/05/16 15:10]
Jackson Zhang [Run out of Memory on php.ini]
+++ litespeed_wiki:config:understanding_500 [2018/05/16 18:28]
Lisa Clarke Proofreading
@@ Line 1: / Line 1: @@
 ====== Understanding 500 Internal Server Error ======
-The 500 status code, or Internal Server Error, means that server cannot process the request for an unknown reason. Sometimes this code will appear when more specific 5xx errors are more appropriate.
+The 500 status code, or "Internal Server Error," means that the server cannot process the request for an unknown reason. Sometimes this code will appear when more specific 5xx errors are more appropriate.
-This most common cause for this error is server misconfiguration (e.g. a malformed .htaccess file) or missing packages (e.g. trying to execute a PHP file without PHP installed properly), permission or ownership changes, Improperly configured php.ini, a PHP upgrade ...etc, anything can trigger a 500 error in a website. The impact of the error can vary based on the cause that triggered it.
+The most common causes for this error are server misconfiguration (e.g. a malformed ''.htaccess'' file), missing packages (e.g. trying to execute a PHP file without PHP installed properly), permission or ownership changes, improperly configured ''php.ini'', a PHP upgrade, etc. //Anything// that the server doesn't know how to handle can trigger a 500 error in a website. The impact of the error can vary based on the event that triggered it.
-error is not a LiteSpeed web server specific error. If you use a control panel like cpanel, you can try the same steps with apache. Most likely Apache will return the same 500 error as LSWS. You will need to find out the reason which causes the problem. If it does not happen to apache server but only on LSWS, you can log a ticket with us for further investigation.
+error is not a LiteSpeed Web Server specific error. If you use a control panel like cPanel, you can try the same steps with Apache. Most likely, Apache will return the same 500 error as LSWS. You will need to find root cause of the problem. If it does not happen to Apache server but only on LSWS, you can [[https://store.litespeedtech.com/store/clientarea.php|log a ticket with us]] for further investigation.
-To troubleshoote 500 error, first to check whether the error affects just one site or every site in the server. Depending on the impact of the error, we debug further. If only one domain it affected, it can be pin-pointed to the specific script error or permission issues. If multiple domains show 500 error, it could be due to some server wide setting change or update.
+To troubleshoot a 500 error, first check whether the error affects just one site or every site in the server. Depending on the impact of the error, you can debug further. If only one domain is affected, it can be pin-pointed to a specific script error or permission issue. If multiple domains show a 500 error, it could be due to some server wide setting change or update.
-You can check server error_log , stderr.log or PHP error-log(normally located where the PHP script running) to see if there is any hint of the error. During the troubleshooting, you may want to ensure PHP error reporting is on in php.ini. Please reverse them back when you done with debuging.
+You can check the server ''error_log'', ''stderr.log'' or PHP error log (normally located where the PHP script is running) to see if there is any hint of the error. During the troubleshooting, you may want to ensure PHP error reporting is on in ''php.ini''. Please reverse the settings back when you're done with debuging.
   error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT  ->   error_reporting = E_ALL
   display_errors = Off -> display_errors = On
   display_startup_errors = Off -> display_startup_errors = On
-Please be aware that not all 500 errors log into the logs and it is common that you don’t see any hint in log files, which will make the troubleshooting more difficult then you expected.
+Please be aware that not all 500 errors appear in the logs and it is common not to see any hint in log files This makes troubleshooting more difficult.
-This will list some of the common reasons/examples, which may help you during the troubleshooting processes.
+Here are some of the common reasons/examples, which may help you during the troubleshooting process.
-=====   permission or ownership changes =====
+===== Permission or Ownership Changes =====
- Permission or ownership changes may cause 500 error. For example, to enable LiteMage extension to your Magento installation through ssh, you will need to run as user. However, if you run command incorrectly as the root user, Magento front end may return 500 instantly. The fix is to reverse file ownership and permission back to the original.
+ Permission or ownership changes may cause 500 error.
+ For example, to enable the LiteMage extension in your Magento installation through SSH, you will need to run a a non-root user. However, if you run the command incorrectly as the root user, the Magento front end may return 500 instantly. The fix is to reverse file ownership and permissions back to the original user.
-===== faulty .htaccess =====
+===== Faulty .htaccess =====
-There is a huge range of things .htaccess can do and isn't difficult to use, however, if you do not enter the syntax correctly it can result in a Server 500 Error.
+There is a huge range of things ''.htaccess'' can do and it isn't difficult to use, however, if you do not enter the syntax correctly it can result in a Server 500 Error.
 For example,
-  RewriteRule ^(.*) http://www.example.com/$1 [P]  <- wrong , will bring site to 500 error
+  RewriteRule ^(.*) http://www.example.com/$1 [P]
-changed to
+Will cause a 500 error. But change it to
-RewriteRule (.*) http://www.example.com/$1 [R=301,L]   <- will fix the issue
+  RewriteRule (.*) http://www.example.com/$1 [R=301,L]
-To confirm whether a misconfiguration .htaccess is the cause of the 500 Internal Server error, either remove or rename the .htaccess file temporarily and then try to reload the page.
+And that will fix the issue.
-=====  Improperly configured php.ini =====
+To confirm whether a misconfiguration in ''.htaccess'' is the cause of the 500 Internal Server error, either remove or rename the .htaccess file temporarily and then try to reload the page.
-Improperly configured php.ini may lead to 500 error.
-For example, set the following in php.ini
- open_basedir = "/path/to/folder"
-However /path/to/folder directory does not exist at all in the system, it will cause 500 error.
-===== Bad PHP code =====
+=====  Improperly Configured php.ini =====
-Bad php code will bring website to 500 immediately.
+An improperly configured ''php.ini'' may lead to 500 error.
-For example, right syntax should be like:
+For example, set the following in ''php.ini'':
+  open_basedir = "/path/to/folder"
+If the ''/path/to/folder'' directory does not exist, it will cause a 500 error.
+===== Bad PHP Code =====
+Bad PHP code will bring a website to 500 immediately.
+For example, the right syntax should be:
    $this->getResponse()->setRedirect(Mage::getBaseUrl()) ;
-If “$” is removed somehow:
+If the “$” is removed somehow:
     this->getResponse()->setRedirect(Mage::getBaseUrl()) ;
-It will bring website to 500 immediately.
+It will bring the website to 500 immediately.
-This is only one of the examples. Many times, wrong syntax PHP error will lead to 500 error.
+This is only one example. Many times, wrong PHP syntax will lead to a 500 error.
-===== PHP handler not set =====
+===== PHP Handler Not Set =====
-On Plesk, PHP handler not set , prompt 500 error
+On Plesk, if a PHP handler is not set, it will prompt a 500 error.
-===== CloudLinux LVE limit reached =====
+===== CloudLinux LVE Limit Reached =====
-When using CloudLinux, If the site is limited by memory or number of processes limits, then the user may receive 500 errors that server cannot execute the script.
+When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html| Learn more.]]
-https://docs.cloudlinux.com/index.html?lve.html
+===== PHP Upgrade =====
+Sometimes if PHP upgrades with a bug, it may cause a 500 error.
-===== PHP upgrade =====
+===== Unsupported Version of PHP =====
-Sometimes PHP upgrade with bug may cause 500 error.
+Unsupported PHP version used by the site/theme/plugin/module may lead to a 500 error.
-===== Unsupport version of PHP =====
+===== PHP Coding Timing Out =====
-unsupport php version by the site/theme/plugin/module may lead to 500 error.
+If your PHP script makes external network connections, the connections may time out. If too many connections are attempted and time out, this will cause a "500 Internal Server Error." To prevent these time outs and errors, make sure that PHP scripts are coded with some timeout rules. Typically, it's difficult to catch a timeout error when connecting to a database or remote resources, as they effectively freeze the script.
+===== Syntax or Coding Errors in Your CGI/Perl Script =====
+If it is a web page ending in ''.cgi'' or ''.pl'' that is producing the error, check your script for errors.
-===== PHP coding timing out =====
+===== Out of Memory in php.ini =====
-If your PHP script makes external network connections, the connections may time out. If too many connections are attempted and time out, this will cause a "500 Internal Server Error." To prevent these time outs and errors, you'll want to make sure that PHP scripts be coded with some timeout rules. Typically, however, catching a timeout error when connecting to a database or externally to remote resources are difficult. They, in effect, freeze the script from continuing to run.
+In this example, we checked ''stderr'':
+  tail /var/log/httpd/stderr.log
-===== SYNTAX OR CODING ERRORS IN YOUR CGI/PERL SCRIPT =====
-If it is a web page ending in .cgi or .pl that is producing the error, check your script for errors.
-===== Run out of Memory on php.ini =====
-check stderr,
- tail /var/log/httpd/stderr.log
 -03-01 12:07:03.573 [STDERR] Tue Mar  1 12:07:03 2016 (12700): Fatal Error Unable to allocate shared memory segment of 134217728 bytes: shmat: Cannot allocate memory (12)
-Further check phpinfo page and memory limit was set to “128M” only.  While opcode cache sonsution is “128M”.
+We further checked the phpinfo page and found the memory limit was set to “128M” only. Opcode cache solution is “128M” by itself, and so there is no memory left for anything else. This leads to a 500 error.
-Which leads to 500 error.
+Increase the PHP memory limit from “128M” to 1024M” to fix the issue.
-Increate php memory limit from “128M” to 1024M” then fix the issue.
+===== Too Many PHP Processes ==
+If there are too many processes in the server queue, it could exceed resources and lead to a 500 error.
+===== Apache Running as SuEXEC while LSWS not on cPanel =====
+In a cPanel/WHM environment, Apache runs as SuEXEC, however LSWS doesn’t.
-===== too many php processes =====
+-03-10 15:39:45.601 [NOTICE] [173.245.52.237:51548] [STDERR] PHP Warning: require_once(/home/demowebsites/public_html/goodmail/wp-config.php): failed to open stream: Permission denied in /home/demowebsites/public_html/goodmail/wp-load.php on line 37
-If too many processes in the server queue, it could exceed resources and lead to 500 error.
+-03-10 15:39:45.601 [NOTICE] [173.245.52.237:51548] [STDERR] PHP Fatal error: require_once(): Failed opening required '/home/demowebsites/public_html/goodmail/wp-config.php' (include_path='.:/opt/cpanel/ea-php70/root/usr/share/pear') in /home/demowebsites/public_html/goodmail/wp-load.php on line 37
-===== PHP open_basedir may cause 500 error =====
+It is necessary to keep LSWS set the same as Apache. Enable LSWS PHP SuEXEC to fix the issue.
-When php open_basedir enabled, it may lead to 500 error.  Try to turn off open_basedir for that domain to see how it is going.
-The following error log captured with openlitespeed when PHP open_basedir intentionally set to a non-exist folder /111, phpinfo page returns 500 error.
+=====  Run Out of Swap Space =====
--05-16 10:59:51.391153 [NOTICE] [192.168.0.198:14271] [STDERR] PHP Warning:  Unknown: open_basedir restriction in effect. File(/usr/local/lsws/Example/html/phpinfo.php) is not within the allowed path(s): (/111) in Unknown on line 0
+Checking ''error.log'' shows:
--05-16 10:59:51.391251 [NOTICE] [192.168.0.198:14271] [STDERR] PHP Warning:  Unknown: failed to open stream: Operation not permitted in Unknown on line 0
+  Failed to obtain or reinitialize VMemBuf. possibly running out of swap space
--05-16 10:59:51.391263 [NOTICE] [192.168.0.198:14271] [STDERR] PHP Fatal error:  Unknown: Failed opening required '/usr/local/lsws/Example/html/phpinfo.php' (include_path='.:/usr/local/lib/php') in Unknown on line 0
-===== apache run as SuEXEC while LSWS not on cpanel =====
-On a cpanel/WHM environment, apache runs as SuEXEC , however LSWS doesn’t.
--03-10 15:39:45.601 [NOTICE] [173.245.52.237:51548] [STDERR] PHP Warning: require_once(/home/demowebsites/public_html/goodmail/wp-config.php): failed to open stream: Permission denied in /home/demowebsites/public_html/goodmail/wp-load.php on line 37
+error is returned. Relocating the LSWS swap directory to a partition with enough space will fix the issue.
--03-10 15:39:45.601 [NOTICE] [173.245.52.237:51548] [STDERR] PHP Fatal error: require_once(): Failed opening required '/home/demowebsites/public_html/goodmail/wp-config.php' (include_path='.:/opt/cpanel/ea-php70/root/usr/share/pear') in /home/demowebsites/public_html/goodmail/wp-load.php on line 37
-Need to keep LSWS to the same setting to apache. Enabled LSWS PHP SuEXEC and fixed the issue.
+===== Missing PHP Packages =====
+Installing PrestaShop returns a 500 error in Chrome. Check the error log and it shows ''php70-json'' package is missing. Install the missing packages and the 500 error is gone.
- =====  Run out of swap space =====
+===== Missing Opcode Cache Module =====
+A WordPress site returns a 500 error when using go2pay, but there is no hint in the server ''error_log'', ''stderr.log'' or PHP ''error_log''. Upgrading the PHP version and adding the opcode cache module fixes the issue. Some applications or plugins may need opcode cache to run.
-Check error.log, it shows: "Failed to obtain or reinitialize VMemBuf. possibly running out of swap space” and return 500 error. Relocating LSWS swap directory to a partition with enough space will fix the issue.
+===== PHP Module Code Conflicting =====
+Magento returns a 500 error and shows a module conflict.
-===== Missing php packages =====
+  a:5:{i:0;s:54:"Mage registry key "umm_top_menu_exists" already exists";i:1;s:4439:"#0 /home/yourhome/public_html/app/Mage.php(223): Mage::throwException('Mage registry k...')
-Install prestashop but 500 returns in Chrome. Check error log and it shows php70-json package missing. Install the missing packages and 500 is gone.
+  #1 /home/yourhome/public_html/app/design/frontend/ultimo/default/template/infortis/ultramegamenu/mainmenu.phtml(54): Mage::register('umm_top_menu_ex...', true)
+  #2 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(241): include('/home/furnishyo...')
+  #3 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(272): Mage_Core_Block_Template->fetchView('frontend/ultimo...')
+  #4 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(286): Mage_Core_Block_Template->renderView()
+  #5 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(923): Mage_Core_Block_Template->_toHtml()
+  #6 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Text/List.php(43): Mage_Core_Block_Abstract->toHtml()
+  #7 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(923): Mage_Core_Block_Text_List->_toHtml()
+  #8 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(641): Mage_Core_Block_Abstract->toHtml()
+  #9 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(585): Mage_Core_Block_Abstract->_getChildHtml('topMenu', true)
-===== missing opcode cache module =====
+===== Disable/Enable Some Magento Modules =====
-A wordpress site returned 500 error when using go2pay, but there is no hint in server error_log, stderr.log or PHP error_log. Upgrading php version and adding opcode cache module fix the issue. Some applications or plugins may need opcode cache to run.
+When disabling ''extendare_EWCore.xml'' by changing from “True” to “false, it shows a 500 error.
+Remove Magento cache files and fix the problem:
-===== PHP module code complicting =====
-Then run magento, it returns 500 error and show module conflicting
-a:5:{i:0;s:54:"Mage registry key "umm_top_menu_exists" already exists";i:1;s:4439:"#0 /home/yourhome/public_html/app/Mage.php(223): Mage::throwException('Mage registry k...')
- #1 /home/yourhome/public_html/app/design/frontend/ultimo/default/template/infortis/ultramegamenu/mainmenu.phtml(54): Mage::register('umm_top_menu_ex...', true)
- #2 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(241): include('/home/furnishyo...')
- #3 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(272): Mage_Core_Block_Template->fetchView('frontend/ultimo...')
- #4 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Template.php(286): Mage_Core_Block_Template->renderView()
- #5 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(923): Mage_Core_Block_Template->_toHtml()
- #6 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Text/List.php(43): Mage_Core_Block_Abstract->toHtml()
- #7 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(923): Mage_Core_Block_Text_List->_toHtml()
- #8 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(641): Mage_Core_Block_Abstract->toHtml()
- #9 /home/yourhome/public_html/app/code/core/Mage/Core/Block/Abstract.php(585): Mage_Core_Block_Abstract->_getChildHtml('topMenu', true)
-===== disabling/enable some magento modules =====
-When disabling extendare_EWCore.xml by changing from “True” to “false, it shows 500 error.
-Remove magento cache files and fix the problem.
   rm -rf var/cache/*
-===== some mod security rules may cause 500 error =====
+===== Some mod_security Rules May Cause a 500 Error =====
-Add java script to a wordpress plugin, but it causes 500 error. Enable LSWS debug logging and found:
+Adding Javascript to a WordPress plugin causes a 500 error. Enable LSWS debug logging and find:
+<code>
 -05-12 04:13:16.673307 [NOTICE] [47.22.54.182:54823#APVH_latampolitics.carinsurancegeorgia.org] mod_security rule [Id '2000145'] triggered! [Sat May 12 04:13:16 2018] [error] [client 47.22.54.182] ModSecurity: Access denied with code 500, [Rule: 'REQUEST_URI|REQUEST_BODY' '<space:(script|about|applet|activex|chrome) >.(script|about|applet|activex|chrome)space: >'] [id "2000145"] [rev "1"] [msg "xss"] [severity "CRITICAL"]
+</code>
+A mod_security rule lead to the 500 error. Disable that mod_security rule to fix the issue.
-Mod_security rule leads to 500 error.  Try to disable that mod security rule and fix the issue.
+===== Hacked Site =====
+If your site is being hacked, it may trigger a 500 error.
-===== hacked site =====
-If your site is being hacked, it may trigger 500 error.