Getting Error after Con Job

[Andrew JamesParticipant]

Hi,

I’ve got Wp-cron disabled and running the cron jobs from cron tab in cpanel.

The cron runs every 15 minutes to keep wordpress happy.

At the end of the cron job that runs the daily backup I am getting the following in a report email:

I have been blocked from reporting the SQL error!!!!!!

It starts:

mysqldump: Couldn’t execute ‘SE LE CT /*!40001 SQL_NO_CACHE */

I have remove Updraft re-downloaded reinstalled it, it then updated.

Set up a new timed backup.

I still get this error.

This has only started in the last couple of days.

How do I fix this?

Thanks in advance for your help.

Cheers,

Andy

[Andrew JamesParticipant]

This reply has been marked as moderator-only.

[Andrew JamesParticipant]

Noo spaces in the select

The rest is:

option_id, option_name, option_value, autoload FROM wp_options WHERE WHERE option_name NOT LIKE “updraft_jobdata_%” AND option_name NOT LIKE “_site_transient_update_%”‘: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘WHERE option_name NOT LIKE “updraft_jobdata_%” AND option_name NOT LIKE “_sit…’ at line 1 (1064)

[Andrew JamesParticipant]

There are 2 WHERE WHERE in the select!!!

[Bryle CroduaModerator]

Hi Andrew,

I will ask our development team to check on this.

Best Wishes,
Bryle

[Andrew JamesParticipant]

Thanks Bryle!

[Bryle CroduaModerator]

Hi Andrew,

There will be a delay on this as our developers are not available on a weekend.

Will follow up on Monday.

Thanks,
Bryle

[Andrew JamesParticipant]

Any progress on this?

[Dee NutbourneModerator]

Hi Andrew,

Apologies for the delay.

Please could you send us a copy of the full backup log for the latest failed backup?
The contents will be too long to post here directly, but you can upload the file to an online service and post the link here. You can also mark your reply as ‘private’.

Best Wishes,
Dee

[Andrew JamesParticipant]

This reply has been marked as private.

[Dee NutbourneModerator]

Hi Andy,

Thank you.

We believe that we have found the cause of the error, and a fix will be included in our next release.

Best Wishes,
Dee

[Dee NutbourneModerator]

This reply has been marked as private.

[Andrew JamesParticipant]

This reply has been marked as private.

[Andrew JamesParticipant]

Hi Dee,

Yesterday I swapped in the new backup.php file.

Did a manual backup, all looked OK.

Backup off the Cron job last night completed without generating the error.

Complete site backed up including 325,000 products in 1 minute 42 seconds.

Very Happy.

Cheers,

Andy

[Author]

Posts