Skip to main content

Error 500 is not being logged

Comments

4 comments

  • SS-Maddy
    Hello Rudolf, From your message, I believe it could be because of a plugin or a script running on those pages alone ? Did you explore that possibility ? I understand the situation and we had a couple of similar cases, but following the options and tips mentioned in the Wordpress KB, especially the SCRIPT_DEBUG helped. - Debugging in WordPress | WordPress.org
    0
  • rudolfl
    Hi, It is most likely a plugin causing this. Page is a generic one from Wordpress (custom post creation), but one of the plugins is likely to act on it. As this is a live site, I am a bit hesitant to start disabling plugins. I am trying to duplicate the site at the moment, so I will be able to do a bit of destructive testing. SCRIPT_DEBUG variable only really applies to debugging JS and CSS -- this one forces Wordpress to supply normal, non-compressed version of those scripts. Still not explaining why error does not appear in logs. I thought it should be reflected in one of the logs. Rudolf
    0
  • Daniel Berthiaume
    On a scenario we've saw in the past, the culprit was the Apache LogLevel setting. Just in case, you can double check in your WHM (Apache configuration -> Global Configuration) and look at the LogLevel setting. Your should make sure the LogLevel is at "warn" so that most regular errors will be logged in "/usr/local/apache/logs/error_log" file.
    0
  • cPanelLauren
    If you're running PHP-FPM you'll find that there is an error log for PHP-FPM in /home/user/logs/domain_tld.php.error.log
    0

Please sign in to leave a comment.