silverlightwp

Hi,

no problem, starting to think it is some odd combination of factors within my setup.

So last night the regular scheduled monthly backup to SugarSync ran automatically and was successful. Then this morning I try running it manually and it fails again.

I then tried deleting authentication and re-authenticating as you asked, then ran it again. This time it came up with a different error ( ERROR: SugarSync API: cUrl Error: SSL_write() returned SYSCALL, errno = 32) on the first attempt but then appears to have succeeded on the second attempt. Here’s the log:

[INFO] BackWPup 3.3.7; A project of Inpsyde GmbH
[INFO] WordPress 4.7.4 on http://www.****
[INFO] Log Level: Normal
[INFO] BackWPup job: 2017_backup_Sugarsync_exclusions
[INFO] Logfile is: backwpup_log_8f4284_2017-05-01_10-39-10.html
[INFO] Backup file is: backwpup_8f4284_2017-05-01_10-39-10.zip
[01-May-2017 10:39:11] 1. Try to backup database …
[01-May-2017 10:39:11] Connected to database **** on localhost:/tmp/mysql5.sock
[01-May-2017 10:39:46] Added database dump “****” with 90.85 MB to backup file list
[01-May-2017 10:39:46] Database backup done!
[01-May-2017 10:39:47] 1. Trying to make a list of folders to back up …
[01-May-2017 10:39:53] Added “wp-config.php” to backup file list
[01-May-2017 10:39:53] 809 folders to backup.
[01-May-2017 10:39:54] 1. Trying to generate a file with installed plugin names …
[01-May-2017 10:39:54] Added plugin list file “****.pluginlist.2017-05-01.txt” with 3.05 KB to backup file list.
[01-May-2017 10:39:54] 1. Trying to generate a manifest file …
[01-May-2017 10:39:54] Added manifest.json file with 7.35 KB to backup file list.
[01-May-2017 10:39:54] 1. Trying to create backup archive …
[01-May-2017 10:39:54] Compressing files as ZipArchive. Please be patient, this may take a moment.
[01-May-2017 10:53:48] Backup archive created.
[01-May-2017 10:53:48] Archive size is 713.14 MB.
[01-May-2017 10:53:48] 12318 Files with 864.49 MB in Archive.
[01-May-2017 10:53:49] 1. Try to send backup to SugarSync …
[01-May-2017 10:53:51] Authenticated to SugarSync with nickname ****
[01-May-2017 10:53:51] 212.54 GB available at SugarSync
[01-May-2017 10:53:52] Starting upload to SugarSync …
[01-May-2017 10:59:08] ERROR: SugarSync API: cUrl Error: SSL_write() returned SYSCALL, errno = 32
[01-May-2017 10:59:09] 2. Try to send backup to SugarSync …
[01-May-2017 10:59:10] Authenticated to SugarSync with nickname ****
[01-May-2017 10:59:10] 212.54 GB available at SugarSync
[01-May-2017 10:59:11] Starting upload to SugarSync …
[01-May-2017 11:21:00] Backup transferred to https://****/backwpup_8f4284_2017-05-01_10-39-10.zip
[01-May-2017 11:21:02] 2 files deleted on SugarSync folder
[01-May-2017 11:21:02] One old log deleted
[01-May-2017 11:21:02] ERROR: Job has ended with errors in 2512 seconds. You must resolve the errors for correct execution.

I just checked my Sugarsync account and the file is there and complete. Interestingly, so is the file from my earlier attempt to manually backup (before redoing authentication) which supposedly failed, but looks like it went through anyway…..weird?!

Update on my issue with SugarSync/BackWPup…I contacted Sugarsync support, they said that “you are using a plugin that is no longer valid with SugarSync which is why you are having the issue. Unfortunately there is nothing we can do in regards to the plugin.” So basically they don’t think it’s going to work and nothing to be done about it.

I’ve switched to using DropBox as my BackWPup destination and that is working fine.

Interestingly, a few days after receiving that reply from Sugarsync, my monthly automatic backup to Sugarsync ran (hadn’t deleted it yet), and it was successful for the first time in several months…go figure!!