Have a new toner cartridge ready.Īnd replace the old image drums with new ones after a message for replacement of image drum appears. The toner indicated on the screen is low. Press the power button to turn off the machine, and then back on. To delete the data without printing, press «CANCEL» button. To manually print, press «ON LINE» button. If the same error occurs, contact your dealer. PHP Short open tag used when not being enabled in php.Detected an abnormality of internal database.Īfter pressing, the data will be deleted, and then reboot. Sometimes it may return 500 error when accessing /phpinfo.php if some restriction set there but not always.Ī typing error : in phpinfo page, which should be, will lead to 500 error. When ssh login as root to server, go to document root and create phpinfo.php, the phpinfo.php file will be owned by root:root instead of user:user. Sometimes we need to check phpinfo page during the troubleshooting. phpinfo.php owned by root instead of user ¶ The fix is to reverse file ownership and permissions back to the original user. However, if you run the command incorrectly as the root user, the Magento front end may return 500 instantly. Permission or ownership changes may cause 500 error.įor example, to enable the LiteMage extension in your Magento installation through SSH, you will need to run a a non-root user. Here are some of the common reasons, and a few examples, which may help you during the troubleshooting process. This makes troubleshooting more difficult. Please be aware that not all 500 errors appear in the logs and it is common not to see any hint in log files. Please revert the settings back when you're done with debuging. During the troubleshooting, you may want to ensure PHP error reporting is on in php.ini. 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. If multiple domains show a 500 error, it could be due to some server wide setting change or update. If only one domain is affected, it can be pin-pointed to a specific script error or permission issue. Depending on the impact of the error, you can debug further. To troubleshoot a 500 error, first check whether the error affects just one site or every site in the server. If it does not happen to Apache server but only on LSWS, you can log a ticket with us for further investigation.
You will need to find root cause of the problem. Most likely, Apache will return the same 500 error as LSWS. If you use a control panel like cPanel, you can try the same steps with Apache. The impact of the error can vary based on the event that triggered it.ĥ00 error is not a LiteSpeed Web Server specific error.
Anything that the server doesn't know how to handle can trigger a 500 error in a website. trying to execute a PHP file without PHP installed properly), permission or ownership changes, improperly configured php.ini, a PHP upgrade, etc. The most common causes for this error are server misconfiguration (e.g.
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.
PHP Code with wrong php configuration settings.PHP Short open tag used when not being enabled in php.ini.Incorrect Rewrite Rules misplace in differernt directories.Different level of Rewrite rules misplaced to the wrong level.phpinfo.php owned by root instead of user.WHM LiteSpeed Plugin WHM LiteSpeed Plugin.External Applications External Applications.LSCache Developers Guide LSCache Developers Guide.
LSCache Without a Plugin LSCache Without a Plugin.LiteSpeed Memcached LiteSpeed Memcached.Advanced Configuration Options for LSCache Storage and Policy Settings.LiteSpeed Web Server LiteSpeed Web Server.