Error 500/503 due cron job / edit.phpp?

503 errors like (in the log files)

[05/Mar/2019:16:30:33 +0100] “POST /wp-cron.php?doing_wp_cron=1551799831.0321960449218750000000 HTTP/1.1” 503 1266 “https://…..de/wp-cron.php?doing_wp_cron=1551799831.0321960449218750000000” “WordPress/5.1; https://…..de”

[05/Mar/2019:16:33:25 +0100] “GET / HTTP/1.1” 503 1266 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +https://www.google.com/bot.html)”
– – [05/Mar/2019:16:34:38 +0100] “POST /wp-cron.php?doing_wp_cron=1551800076.3861389160156250000000 HTTP/1.1” 503 1266 “https://…..de/wp-cron.php?doing_wp_cron=1551800076.3861389160156250000000” “WordPress/5.1; https://…..de”

Error 500:

Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log.

If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

503 error:

The 503 service unavailable error occurs when your web server is unable to get a proper response from a PHP script. This PHP script could be a WordPress plugin, a theme, or a misbehaving custom code snippet.
– If the error is caused by heavy usage, a server glitch, server temporarily offline for maintenance, the server too busy or concurrent request limit exceeded, or a DDoS attack, then it could automatically disappear in a few minutes.
– However, if it is caused by bad code on your website, then it will keep occurring unless you find and disable the code that’s causing it.

To troubleshoot, try:
– Deactivate plugins, switch theme, reinstall WP
– Review https://www.wpbeginner.com/wp-tutorials/how-to-fix-503-service-unavailable-error-in-wordpress/
– If these methods fail to resolve the error, then try contacting your hosting provider.

EDIT:
CRON: There is also this Ticket about cron. See if your issue is the same as described in this Ticket: #44818: cron: preventing duplicate events fails when the first event is too far in the past

• This reply was modified 6 years ago by t-p.
• This reply was modified 6 years ago by t-p.
• This reply was modified 6 years ago by t-p.

@t-p
Thanks a lot.
I have disabled the plugin WP Optimize because it deletes database entries like old revisions etc. I have heard that this can cause this.
Also, your hint with the cron ticket might also apply. But I am not that good in programming. And I don’t know if this also applies to what WP Optimize is doing with older revisions, but it seems at least a possibility. But then, it is also good that I have disabled the plugin.
I have asked the hosting provider to further check log files the next few days and also have a look on the PHP memory usage, which was also too high.