• bubulina

    (@bubulina)


    I have upgraded to v2.1.8 (WordPress 3.3.1) and since the upgrade my daily backup job does not run automatically anymore, as it was scheduled. If I run the job manually then then job will run up to the point to upload the backup to SugarSync, it will stay stuck until I cancel it…

Viewing 4 replies - 1 through 4 (of 4 total)
  • Daniel Hüsken

    (@danielhuesken)

    please resave the job.
    wait util the upload to sugarsync is done.

    Thread Starter bubulina

    (@bubulina)

    Hi Daniel,

    I resaved the job, and now the scheduled job started as it was supposed to. However, like with the manual job that I run yesterday, it is not managing to upload the backup to SugarSync anymore, here is part of the log:

    2012/02/20 03:03.35: Archive size is 219.94 MB
    2012/02/20 03:03.35: 1. try sending backup to SugarSync…
    2012/02/20 03:03.35: Authed to SugarSync with xxxx xxxxxxxxxxxxx
    2012/02/20 03:03.35: 4.34 GB free on SugarSync
    2012/02/20 03:03.36: Upload to SugarSync now started…
    2012/02/20 03:18.42: [ERROR] Job restarted, bcause inactivity!
    2012/02/20 03:18.42: 2. try sending backup to SugarSync…
    2012/02/20 03:18.42: Authed to SugarSync with xxxx xxxxxxxxxxxxx
    2012/02/20 03:18.42: 4.34 GB free on SugarSync
    2012/02/20 03:18.43: Upload to SugarSync now started…
    2012/02/20 03:27.25: [ERROR] SugarSync API: Http Error: 503
    2012/02/20 03:27.25: 3. try sending backup to SugarSync…
    2012/02/20 03:27.26: Authed to SugarSync with xxxx xxxxxxxxxxxxx
    2012/02/20 03:27.26: 4.34 GB free on SugarSync
    2012/02/20 03:27.26: Upload to SugarSync now started…
    2012/02/20 03:27.43: [ERROR] SugarSync API: Http Error: 503
    2012/02/20 03:27.43: [ERROR] Step arborted has too many trys!
    2012/02/20 03:27.43: One old log deleted
    2012/02/20 03:27.43: Job done in 1520 sec.

    14nc310t

    (@14nc310t)

    The same for me. After the upgrade, a job that backup the databese and the filsystem, just hang.

    This is the log of my scheduled backup:

    <html>
    <head>
    <meta name=”backwpup_version” content=”2.1.8″ />
    <meta name=”backwpup_logtime” content=”1329710538″ />
    <meta name=”backwpup_errors” content=”0″ />
    <meta name=”backwpup_warnings” content=”0″ />
    <meta name=”backwpup_jobid” content=”1″ />
    <meta name=”backwpup_jobname” content=”Backup full” />
    <meta name=”backwpup_jobtype” content=”DB+FILE+OPTIMIZE+CHECK” />
    <meta name=”backwpup_backupfilesize” content=”0″ />
    <meta name=”backwpup_jobruntime” content=”0″ />
    <style type=”text/css”>
    .timestamp {background-color:grey;}
    .warning {background-color:yellow;}
    .error {background-color:red;}
    #body {font-family:monospace;font-size:12px;white-space:nowrap;}
    </style>
    <title>BackWPup log for Backup full from 20 febbraio 2012 at 05:02</title>
    </head>
    <body id=”body”>

    14nc310t

    (@14nc310t)

    Resolved chmodding 755 the backwpup plugin directory after the upgrade!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: BackWPup] Jobs don't run after upgrade’ is closed to new replies.