• Resolved Thomas Dalgaard

    (@coolfortheblind)


    Hi!
    I got this error when trying to do a backup. Everything else worked ok except when uploading to Dropbox. The error showed up in the log twice, but the job completed.
    Debug informations are pasted below:

    WordPress version: 4.7.5
    BackWPup version: 3.4.1
    PHP version: 5.6.30  (64bit)
    MySQL version: 10.1.24-MariaDB-cll-lve
    cURL version: 7.53.1
    cURL SSL version: OpenSSL/1.0.1e
    Server self connect: Response Test O.K.
    Server: LiteSpeed
    Operating System: Linux
    PHP SAPI: litespeed
    Maximum execution time: 9999 seconds
    Alternative WP Cron: Off
    Disabled WP Cron: Off
    CHMOD Dir: 0755
    Server Time: 5:5
    Blog Time: 07:05
    Blog Timezone: Europe/Copenhagen
    Blog Time offset: 2 hours
    Blog language: da-DK
    MySQL Client encoding: utf8
    PHP Memory limit: 1024M
    WP memory limit: 40M
    WP maximum memory limit: 1024M
    Memory in use: 14.25 MB
    Loaded PHP Extensions:: Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, SourceGuardian, Zend Guard Loader, Zend OPcache, bcmath, bz2, calendar, ctype, curl, date, dba, dom, enchant, ereg, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, ionCube Loader, json, ldap, libxml, litespeed, mbstring, mcrypt, memcache, mhash, mysql, mysqli, mysqlnd, odbc, openssl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, session, shmop, snmp, soap, sockets, sqlite3, standard, suhosin, sysvmsg, sysvsem, sysvshm, tidy, timezonedb, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib
Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @coolfortheblind, can you verify that you have enough space in Dropbox? Also, are you getting any other warnings or errors besides this? I’ve seen this happen if Dropbox has to make multiple attempts to upload the same file.

    I have the exact same issue. I have plenty of space (10GB) on Dropbox, the job completes, the file appears on dropbox, yet I get that error… I’m just afraid the backup file might be corrupted 🙁

    I’ve attached the log below:

    
    [16-Jul-2017 23:57:22] Archive size is 123.29 MB.
    [16-Jul-2017 23:57:22] 6301 Files with 168.08 MB in Archive.
    [16-Jul-2017 23:57:22] 1. Try to send backup file to Dropbox …
    [16-Jul-2017 23:57:22] Authenticated with Dropbox of user: Diogo Nunes
    [16-Jul-2017 23:57:22] Uploading to Dropbox …
    [16-Jul-2017 23:57:22] Beginning new file upload session
    [17-Jul-2017 00:03:40] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [17-Jul-2017 00:03:40] 2. Try to send backup file to Dropbox …
    [17-Jul-2017 00:03:41] Authenticated with Dropbox of user: Diogo Nunes
    [17-Jul-2017 00:03:41] Uploading to Dropbox …
    [17-Jul-2017 00:11:36] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [17-Jul-2017 00:11:36] 3. Try to send backup file to Dropbox …
    [17-Jul-2017 00:11:36] Authenticated with Dropbox of user: Diogo Nunes
    [17-Jul-2017 00:11:36] Uploading to Dropbox …
    [17-Jul-2017 00:18:45] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [17-Jul-2017 00:18:45] 4. Try to send backup file to Dropbox …
    [17-Jul-2017 00:18:46] Authenticated with Dropbox of user: Diogo Nunes
    [17-Jul-2017 00:18:46] Uploading to Dropbox …
    [17-Jul-2017 00:19:15] Finishing upload session with a total of 123 MB uploaded
    [17-Jul-2017 00:19:18] ERROR: Uploaded file size and local file size don't match.
    [17-Jul-2017 00:19:18] 5. Try to send backup file to Dropbox …
    [17-Jul-2017 00:19:19] Authenticated with Dropbox of user: Diogo Nunes
    [17-Jul-2017 00:19:19] Uploading to Dropbox …
    [17-Jul-2017 00:19:19] One old log deleted
    [17-Jul-2017 00:19:19] ERROR: Job has ended with errors in 1347 seconds. You must resolve the errors for correct execution.
    

    Those retry warnings, I always had them. As a workaround I had to increase the timeout for the plugin to ignore those timeouts.

    • This reply was modified 7 years, 3 months ago by dialex.

    Hi @dialex, the timeout warning is your issue. What is your maximum script execution time set to under BackWPup > Settings > Jobs?

    0 seconds, so no timeout right? I had to, otherwise the job would always fail due to timeouts. What should I do?

    Hi @dialex, actually that’s a misconception. The plugin doesn’t try to set the php maximum time limit, so all setting it to 0 does is allow the script to run until PHP’s time limit is reached.

    I’d set it to something low like 20 seconds and see what it does.

    Oh. I had no idea about that. I made the change, the job executed without warnings or errors. It also finished 10 times faster!!

    Thank you so much. It’s solved. Maybe you could add a UI hint on that field to prevent users from making the same mistake I did 😛

    Thanks @dialex, so happy it’s working!

    Yeah it’s a common mistake and we should probably add something to dispel that, or even do what users expect and call set_time_limit(0) when it is 0. It’s something I’ve thought about. We’ll definitely take it into consideration.

    Thread Starter Thomas Dalgaard

    (@coolfortheblind)

    Hi!

    I got it to work, but I had to change the compression format from zip to tar.gzip, that has worked almost any time for me.
    However I had one instance where my backup file was corrupted when I tried to download it from Dropbox.
    How can I find out if there is any chance for this for a future backup?This time I was lucky that I had a backup hosted at a test-site, but that is not how I would like to have my backups working for the future… I tried downloading the same tar.gz file with Safari and Google Chrome on my Mac but every time the file was broke and couldn’t be extracted so I could restore from that. I have only seen this once, but hope I will never see it again.
    Thanks for a great plugin though, it has saved my bacon a lot since I found it a few years ago!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ERROR: Uploaded file size and local file size don’t match.’ is closed to new replies.