• Resolved Sean

    (@sean-h)


    HI there,

    It seems others are also getting warnings, but for different reasons. In my case, this is all I can find in the logs:

    0000.069 (0) Checking if we have a zip executable available
    0000.074 (0) Testing: /usr/bin/zip
    0000.092 (0) Output: zip warning: binziptest/test.zip not found or empty
    0000.096 (0) Output: adding: binziptest/subdir1/ (in=0) (out=0) (stored 0%)
    0000.098 (0) Output: adding: binziptest/subdir1/subdir2/ (in=0) (out=0) (stored 0%)
    0000.099 (0) Output: adding: binziptest/subdir1/subdir2/test.html (in=131) (out=107) (deflated 18%)
    0000.101 (0) Output: total bytes=131, compressed=107 -> 18% savings
    0000.116 (0) Output: adding: binziptest/subdir1/subdir2/test2.html (in=138) (out=113) (deflated 18%)
    0000.123 (0) Output: total bytes=269, compressed=220 -> 18% savings
    0000.143 (0) Working binary zip found: /usr/bin/zip
    0000.148 (0) Zip engine: found/will use a binary zip: /usr/bin/zip
    0000.152 (0) Creation of backups of directories: beginning
    0000.163 (0) Beginning creation of dump of plugins (split every: 400 MB)
    0000.370 (0) Total entities for the zip file: 1516 directories, 8953 files (0 skipped as non-modified), 125.6 MB

    I should bring attention to the fact this only seems to happen on our larger of the 6 sites we have on the same shared server, when I say ‘large’ though, it is only a grand total of about 1GB. But like I say, the backup appears to complete successfully anyway. All 6 sites are running real-cron jobs.

    • This topic was modified 4 years, 11 months ago by Sean.
    • This topic was modified 4 years, 11 months ago by Sean.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Sean

    (@sean-h)

    Update: I set the split to 200MB, down from 400MB. I still get the same zip warnings in the log as pasted in my post above, but the backups now complete without (warnings).

    The backup apparently succeeded and is now complete (Apr 22 16:31:56)

    I know, if it’s not broken, don’t fix it, but I am still curious as to what’s going on.

    Plugin Contributor bcrodua

    (@bcrodua)

    Hi,

    For us to check, please could you send us a full copy of the backup log?
    Please use an online service such as Dropbox or Pastebin, and post the link here.

    Regards,
    Bryle

    Thread Starter Sean

    (@sean-h)

    Hi Bryle,

    I have further decreased the chunks down to 100MB after things got stuck, again.

    But all sites seem to be working fine now. I think this has something to do with shared hosting limitations, but, I think the above adjustment has fixed it.

    Also, it looks like this ‘problem’ I think I have is in fact Updraft looking for the default zip engine, not finding it, but instead it ends up using the one my host has enabled.

    So, here is my latest log, only I don’t think anything is broken, at this time:

    https://drive.google.com/file/d/1bQlIJArNCnbZm7QBHHmkyy-c0Eq7zJtP/view?usp=sharing

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Successful backup, but with warnings.’ is closed to new replies.