Ahmed Khan

Hi @zweersmuziek,

Have you tried the solutions i proposed?

These error logs point to two distinct, yet often related, bottlenecks on your WordPress site: a conflict with your background backup scheduler and a database connection lock-up that happens right as your pages finish loading.

The first error is directly related to your backup system. The code letters “abwp” stand for Akeeba Backup WordPress. The log shows that the plugin is attempting to reschedule a background event to run every sixty seconds, but WordPress is repeatedly failing to save this event to the database. Running a backup check or routine every single minute is incredibly resource-intensive and often hits server memory or database blocks, which causes the database to reject the command entirely. To fix this, you will want to log into your WordPress admin dashboard, navigate to your Akeeba Backup settings, and check your automatic or scheduled backup intervals. Adjusting this frequency to something more realistic, like once a day or once a week, should stop this error from recurring.

The remaining errors regarding commands being out of sync are a classic MySQL database issue. This error occurs when a plugin starts a database query but fails to fully retrieve or release the results before WordPress attempts to run a new query on that same connection. In your case, this is triggering during the shutdown hook, specifically when the EWWW Image Optimizer plugin is filtering the page output to handle lazy loading and above-the-fold images. Because EWWW leaves the database connection busy, the native WordPress system cron is blocked when it tries to update its background tasks at the end of the page load, resulting in a cascade of database failures.

To resolve the database sync issue, start by updating EWWW Image Optimizer to its latest version, as developers regularly release patches for these types of query timing conflicts. You can also temporarily disable the “lazy load” or “above-the-fold” features in the EWWW settings to see if the errors immediately stop.

The most robust way to solve this permanently is to stop WordPress from running background tasks through your visitors’ browsers. By default, WordPress spawns a background cron process every time someone visits a page, which is why this is colliding with your image optimizer at the end of a page load. You can disable this default behavior by adding the line define( 'DISABLE_WP_CRON', true ); to your wp-config.php file. Once disabled, log into your web hosting control panel and set up a real system cron job to trigger your wp-cron.php file every ten minutes. This completely decouples your scheduled tasks from page loads, which relieves database pressure and naturally prevents these command conflicts from happening.