Support » Plugin: UpdraftPlus WordPress Backup Plugin » Updarft backup fails

Viewing 15 replies - 1 through 15 (of 21 total)
  • Having the same issue, originally thought it was an issue connecting to Google Drive until I looked at the logs. It seems disabling and removing the plugin then doing a reinstall does not solve anything.

    Plugin Author David Anderson

    (@davidanderson)

    Hi,

    Please upgrade to the latest – http://downloads.wordpress.org/plugin/updraftplus.1.1.10.zip – which may have fixed your error.

    Also, please read the plugin FAQ before your next support request!

    If you find UpdraftPlus useful, please consider a donation: http://david.dw-perspective.org.uk/donate – statistics to date: 13,000 downloads, $25 total donations.

    David

    Updated to the newest version 1.1.10 (which was not available yesterday) and still can not get the backup to work. Here is the log file:

    Fri, 04 Jan 2013 20:56:56 +0000 PHP version: 5.3.14 WordPress version: 3.5 Updraft version: 1.1.10 Backup files: 1 (schedule: weekly) Backup DB: 1 (schedule: daily)
    Fri, 04 Jan 2013 20:56:56 +0000 Another backup job (12c2102a371e) of the same type () appears to now be running – terminating our run (apparent race condition)

    I had posted the content of the log file for 12c2102a371e in the other thread which has been closed…

    Plugin Author David Anderson

    (@davidanderson)

    Try this:
    http://downloads.wordpress.org/plugin/updraftplus.1.1.11.zip

    It’s somewhat superfluous to inform me that it wasn’t available yesterday; having uploaded it 10 minutes ago I knew that. 😉

    Have a similar issue with a previous backup preventing a new backup run. Previous backup did not complete due to an ftp issue apparently.

    ri, 04 Jan 2013 20:53:03 +0000 PHP version: 5.2.9 WordPress version: 3.5 Updraft version: 1.1.10 Backup files: 1 (schedule: manual) Backup DB: 1 (schedule: manual)
    Fri, 04 Jan 2013 20:53:03 +0000 Another backup job (19d701babb39) of the same type () appears to now be running – terminating our run (apparent race condition)

    previous backup log log.19d701babb39.txt
    ….
    Wed, 12 Dec 2012 15:40:48 +0000 Saving backup history
    Wed, 12 Dec 2012 15:40:48 +0000 Beginning dispatch of backup to remote
    Wed, 12 Dec 2012 15:40:48 +0000 Cloud backup: FTP
    ends here

    How can I clear the previous backup running flag?

    Kevin

    Plugin Author David Anderson

    (@davidanderson)

    Hi kjcmalden,

    Please upgrade to version 1.1.11 – http://downloads.wordpress.org/plugin/updraftplus.1.1.11.zip

    David

    sorted! thank you

    Plugin Author David Anderson

    (@davidanderson)

    You are welcome. If you find UpdraftPlus useful, please consider a donation: http://david.dw-perspective.org.uk/donate – statistics to date: 13,000 downloads, $25 total donations.

    David

    Updated to version x.x.11 and it runs the backup…but it appears to stalled, I see about 15 MB of backup files on the server in the Updraft folder, but nothing on my Google drive. Here is the log file associated with these backups:

    Fri, 04 Jan 2013 21:28:15 +0000 PHP version: 5.3.14 WordPress version: 3.5 Updraft version: 1.1.11 Backup files: 1 (schedule: weekly) Backup DB: 1 (schedule: daily)
    Fri, 04 Jan 2013 21:28:15 +0000 Processed schedules. Tasks now: Backup files: 1 Backup DB: 1
    Fri, 04 Jan 2013 21:28:15 +0000 In case we run out of time, scheduled a resumption at: 300 seconds from now
    Fri, 04 Jan 2013 21:28:15 +0000 Beginning backup of directories
    Fri, 04 Jan 2013 21:28:15 +0000 No backup of plugins: excluded by user’s options
    Fri, 04 Jan 2013 21:28:15 +0000 Beginning backup of themes
    Fri, 04 Jan 2013 21:28:19 +0000 Created themes zip – file size is 1248067 bytes
    Fri, 04 Jan 2013 21:28:19 +0000 Beginning backup of uploads
    Fri, 04 Jan 2013 21:28:20 +0000 Created uploads zip – file size is 3130627 bytes
    Fri, 04 Jan 2013 21:28:20 +0000 Beginning backup of other directories found in the content directory
    Fri, 04 Jan 2013 21:28:20 +0000 Looking for candidates to back up in: /home/content/17/7232417/html/ffextensiongurublog/wp-content
    Fri, 04 Jan 2013 21:28:20 +0000 index.php: skipping: excluded by options
    Fri, 04 Jan 2013 21:28:20 +0000 themes: skipping: this is the themes directory
    Fri, 04 Jan 2013 21:28:20 +0000 plugins: skipping: this is the plugins directory
    Fri, 04 Jan 2013 21:28:20 +0000 uploads: skipping: this is the uploads directory
    Fri, 04 Jan 2013 21:28:20 +0000 upgrade: skipping: excluded by options
    Fri, 04 Jan 2013 21:28:20 +0000 advanced-cache.php: adding to list
    Fri, 04 Jan 2013 21:28:20 +0000 wp-cache-config.php: adding to list
    Fri, 04 Jan 2013 21:28:20 +0000 cache: skipping: excluded by options
    Fri, 04 Jan 2013 21:28:20 +0000 updraft: skipping: this is the updraft directory
    Fri, 04 Jan 2013 21:28:20 +0000 Created other directories zip – file size is 2573 bytes
    Fri, 04 Jan 2013 21:28:20 +0000 Beginning backup of database
    Fri, 04 Jan 2013 21:28:20 +0000 Table wp_commentmeta: Total rows added: 1823
    Fri, 04 Jan 2013 21:28:21 +0000 Table wp_comments: Total rows added: 3902
    Fri, 04 Jan 2013 21:28:21 +0000 Table wp_links: Total rows added: 7
    Fri, 04 Jan 2013 21:28:21 +0000 Table wp_options: Total rows added: 394
    Fri, 04 Jan 2013 21:28:22 +0000 Table wp_postmeta: Total rows added: 5189
    Fri, 04 Jan 2013 21:28:24 +0000 Table wp_posts: Total rows added: 3755
    Fri, 04 Jan 2013 21:33:34 +0000 Resume backup (1): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:33:34 +0000 Resuming backup: resumption=1, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:33:34 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:33:34 +0000 There were no files that needed uploading; backup job is finished
    Fri, 04 Jan 2013 21:38:49 +0000 Resume backup (2): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:38:49 +0000 Resuming backup: resumption=2, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:38:49 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:38:49 +0000 There were no files that needed uploading; backup job is finished
    Fri, 04 Jan 2013 21:43:49 +0000 Resume backup (3): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:43:49 +0000 Resuming backup: resumption=3, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:43:49 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:43:49 +0000 There were no files that needed uploading; backup job is finished
    Fri, 04 Jan 2013 21:48:58 +0000 Resume backup (4): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:48:58 +0000 Resuming backup: resumption=4, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:48:58 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:48:58 +0000 There were no files that needed uploading; backup job is finished
    Fri, 04 Jan 2013 21:54:14 +0000 Resume backup (5): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:54:14 +0000 Resuming backup: resumption=5, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:54:14 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:54:14 +0000 There were no files that needed uploading; backup job is finished
    Fri, 04 Jan 2013 21:59:18 +0000 Resume backup (6): begin run (will check for any remaining jobs)
    Fri, 04 Jan 2013 21:59:18 +0000 Resuming backup: resumption=6, nonce=f2ff727221cb, begun at=1357334895
    Fri, 04 Jan 2013 21:59:18 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Fri, 04 Jan 2013 21:59:18 +0000 There were no files that needed uploading; backup job is finished

    FWIW my DB is about 56 MB, I don’t know it this causing an issue or not…

    Plugin Author David Anderson

    (@davidanderson)

    Looks like the PHP script stops running before it finishes writing out the database file. What’s your server’s maximum execution time for PHP scripts? Whatever it is, it isn’t enough, and that’s not a bug in UpdraftPlus – whatever plugin you deploy to back up your database will hit the same problem and there’s nothing that I as a plugin author can do about it.

    That explains a lot. The default value was 30, I have bumped it up to 1200 now (which I have confirmed via phpinfo.php file I uploaded). Still seems to run into some type of problem about not finding “record in database with this timestamp” and it is still trying to finish the other unsuccessful backup jobs. Looking at the log file of a successful backup of my other WP site, it seems like it doesn’t make it out of the wp_post table of the DB.

    Sat, 05 Jan 2013 00:09:11 +0000 PHP version: 5.3.14 WordPress version: 3.5 Updraft version: 1.1.11 Backup files: 1 (schedule: weekly) Backup DB: 1 (schedule: daily)
    Sat, 05 Jan 2013 00:09:11 +0000 Processed schedules. Tasks now: Backup files: 1 Backup DB: 1
    Sat, 05 Jan 2013 00:09:11 +0000 In case we run out of time, scheduled a resumption at: 300 seconds from now
    Sat, 05 Jan 2013 00:09:11 +0000 Beginning backup of directories
    Sat, 05 Jan 2013 00:09:11 +0000 No backup of plugins: excluded by user’s options
    Sat, 05 Jan 2013 00:09:11 +0000 Beginning backup of themes
    Sat, 05 Jan 2013 00:09:12 +0000 Created themes zip – file size is 1248067 bytes
    Sat, 05 Jan 2013 00:09:12 +0000 Beginning backup of uploads
    Sat, 05 Jan 2013 00:09:13 +0000 Created uploads zip – file size is 3130627 bytes
    Sat, 05 Jan 2013 00:09:13 +0000 Beginning backup of other directories found in the content directory
    Sat, 05 Jan 2013 00:09:13 +0000 Looking for candidates to back up in: /home/content/17/7232417/html/ffextensiongurublog/wp-content
    Sat, 05 Jan 2013 00:09:13 +0000 index.php: skipping: excluded by options
    Sat, 05 Jan 2013 00:09:13 +0000 themes: skipping: this is the themes directory
    Sat, 05 Jan 2013 00:09:13 +0000 plugins: skipping: this is the plugins directory
    Sat, 05 Jan 2013 00:09:13 +0000 uploads: skipping: this is the uploads directory
    Sat, 05 Jan 2013 00:09:13 +0000 upgrade: skipping: excluded by options
    Sat, 05 Jan 2013 00:09:13 +0000 advanced-cache.php: adding to list
    Sat, 05 Jan 2013 00:09:13 +0000 wp-cache-config.php: adding to list
    Sat, 05 Jan 2013 00:09:13 +0000 cache: skipping: excluded by options
    Sat, 05 Jan 2013 00:09:13 +0000 updraft: skipping: this is the updraft directory
    Sat, 05 Jan 2013 00:09:13 +0000 Created other directories zip – file size is 2573 bytes
    Sat, 05 Jan 2013 00:09:13 +0000 Beginning backup of database
    Sat, 05 Jan 2013 00:09:13 +0000 Table wp_commentmeta: Total rows added: 1823
    Sat, 05 Jan 2013 00:09:14 +0000 Table wp_comments: Total rows added: 3902
    Sat, 05 Jan 2013 00:09:14 +0000 Table wp_links: Total rows added: 7
    Sat, 05 Jan 2013 00:09:14 +0000 Table wp_options: Total rows added: 400
    Sat, 05 Jan 2013 00:09:14 +0000 Table wp_postmeta: Total rows added: 5189
    Sat, 05 Jan 2013 00:09:16 +0000 Table wp_posts: Total rows added: 3755
    Sat, 05 Jan 2013 00:10:12 +0000 Resume backup (4): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:10:12 +0000 Resuming backup: resumption=4, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:10:12 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:10:12 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:10:55 +0000 Resume backup (2): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:10:55 +0000 Resuming backup: resumption=2, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:10:55 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:10:55 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:14:13 +0000 Resume backup (1): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:14:13 +0000 Resuming backup: resumption=1, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:14:13 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:14:13 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:15:16 +0000 Resume backup (5): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:15:16 +0000 Resuming backup: resumption=5, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:15:16 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:15:16 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:15:58 +0000 Resume backup (3): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:15:58 +0000 Resuming backup: resumption=3, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:15:58 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:15:58 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:19:37 +0000 Resume backup (2): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:19:37 +0000 Resuming backup: resumption=2, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:19:37 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:19:37 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:20:20 +0000 Resume backup (6): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:20:20 +0000 Resuming backup: resumption=6, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:20:20 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:20:20 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:21:06 +0000 Resume backup (4): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:21:06 +0000 Resuming backup: resumption=4, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:21:06 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:21:06 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:24:50 +0000 Resume backup (3): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:24:50 +0000 Resuming backup: resumption=3, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:24:50 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:24:50 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:25:31 +0000 Resume backup (7): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:25:31 +0000 Resuming backup: resumption=7, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:25:31 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:25:31 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:26:11 +0000 Resume backup (5): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:26:11 +0000 Resuming backup: resumption=5, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:26:11 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:26:11 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:30:33 +0000 Resume backup (4): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:30:33 +0000 Resuming backup: resumption=4, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:30:33 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:30:33 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:30:33 +0000 Resume backup (8): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:30:33 +0000 Resuming backup: resumption=8, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:30:33 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:30:33 +0000 There were no files that needed uploading; backup job is finished
    Sat, 05 Jan 2013 00:31:18 +0000 Resume backup (6): begin run (will check for any remaining jobs)
    Sat, 05 Jan 2013 00:31:18 +0000 Resuming backup: resumption=6, nonce=d2d4d8c823ba, begun at=1357344551
    Sat, 05 Jan 2013 00:31:18 +0000 Error: Could not find a record in the database of a backup with this timestamp
    Sat, 05 Jan 2013 00:31:18 +0000 There were no files that needed uploading; backup job is finished

    Thanks for all your help thus far.

    Plugin Author David Anderson

    (@davidanderson)

    Hi,

    The “Could not find a record” parts can be ignored – that is expected, backup jobs do not become resumable until a later stage than yours is reaching. If you look at the timings on your log, you can see that the abortion is not happening because of a timeout, unless your timeout is very short, which is possible – PHP’s max_execution_time is not the only timeout that can be applied; your webserver may be applying one by another mechanism. Two things you can do: 1) Check with your hosting provider and 2) Find your PHP error log and see if anything is in there. The UpdraftPlus log is only showing an untimely abortion, but you’d need to see the PHP error log to find out why, or otherwise learn that your hosting provider is for some reason only allowing your scripts to execute for a maximum of 5 seconds.

    Plugin Author David Anderson

    (@davidanderson)

    P.S. Your other alternative is to fund me to make UpdraftPlus backup runs resumable at an earlier stage; but as said in the FAQ, I don’t consider it a bug if your hosting provider resource-starves you so that would be a premium feature request rather than a bug fix.

    I should mention that the other site is on the same provider and server for that matter and the script runs fine. However, that site is very small compared to this one. But I noticed reviewing the logs on that one the script does it work in 4-seconds. Seems on main site it runs for about 8-seconds and gets most of the way through the DB and dies.

    I will need to send a support ticket to my hosting provider to find out why the error logs are not working correctly. I can see log files being generated but they are empty. I will also ask about other timeouts. The ticket has been sent, but I don’t expect a reply for at least 24-hours.

    In regards to the funding option can you please provide more info.

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘Updarft backup fails’ is closed to new replies.