WordPress.org

Ready to get started?Download WordPress

Forums

BackWPup Free - WordPress Backup Plugin
[resolved] Backup Job Schedule Resets to 1969 (28 posts)

  1. polybearsfootball
    Member
    Posted 10 months ago #

    I have BackWPup setup with a few jobs with a destination of Dropbox. Once a job triggers, even if its a "Run Now", it resets the schedule to 1969. This happens even if the job is run and immediately canceled. Any ideas in what could cause this?

    http://wordpress.org/extend/plugins/backwpup/

  2. CheapWineFinder
    Member
    Posted 10 months ago #

    Same problem. I had to go into each job AND click the schedule tab, then save to reset it, but would love to get an answer on how to fix this.

    Still having issue where plugin deactivates on its own. Not sure if it's related.

  3. polybearsfootball
    Member
    Posted 10 months ago #

    Same fix for me. Select the Schefule Tab and save. But then as a test I manually started and cancelled a job and it reset. Strange.

  4. polybearsfootball
    Member
    Posted 10 months ago #

    I really hope someone answers this post soon. I have no backups unless I manually run them because every time they run they reset to December 31, 1969 at 5:00.

  5. polybearsfootball
    Member
    Posted 9 months ago #

    Could anyone suggest what might cause this? I've checked all I can think of with no solution. Googling it shows its not just me, since I found other related post. Please?

  6. kdavidson
    Member
    Posted 9 months ago #

    Same thing for me. All my daily backups stopped working on May 26 (but my weekly backups have continued just fine). I just today discovered the 1969 "next run" date on the dailys, so I just resaved the schedule tab and we'll see what happens. This behavior was identical on three different web sites running on different hosts. All were running WP v3.5.1 (until today, now v3.5.2) using BackWPup v3.0.12. I'm anxious to see what happens after tonight's daily run.

  7. polybearsfootball
    Member
    Posted 9 months ago #

    I have the same specs, WP 3.5.2, and BackWPup 3.0.12. I found the post below, that is a generic discussion of PHP dates reseting to December 31, 1969, but while I understand that issue, I am unaware of where in the plugin code that could be an issue.

    http://stackoverflow.com/questions/2224097/prevent-php-date-from-defaulting-to-12-31-1969

  8. coffeemick
    Member
    Posted 9 months ago #

    I have the same problem and wrote about it in another support thread: http://wordpress.org/support/topic/jobs-sometimes-reschedule-to-1-jan-1970?replies=6#post-4403145

    1.1.1970 is used if there's no valid date available. Having it on December 31, 1969 means some time zone calculation took place.

  9. polybearsfootball
    Member
    Posted 9 months ago #

    Hey CoffeMick,

    I've found a number of threads about this, and have seen the 19070 & 1969 dates various times. I realize there is a pro version that includes support, but this seems to be happening to enough people I wish the Dev would chime in. I looked through code to find any DATE calls he was doing and nothing jumped out at me. Might have to look deeper.

    Razz

  10. Manuel de la Fuente
    Member
    Posted 9 months ago #

    Same problem here. I tried to solve it using the start script provided by the plugin and running it with Cron. The script has this estructure:

    #!/bin/sh
    @$1php -c "/usr/selector/php.ini" -r "define( 'DOING_CRON', TRUE ); require '/blog/path/wp-load.php'; if( class_exists( 'BackWPup_Job' ) ) BackWPup_Job::start_cli( 1 );"

    But when I run it, get this error:

    /path/to/the/script/BackWPup_cmd_start_job_1.sh: line 2: @php: command not found

    Does anyone know how to fix it?

  11. coffeemick
    Member
    Posted 6 months ago #

    My 1 Jan 1970 problem was solved when updating to WordPress 3.6 release version. I was running 3.6 RCx before.

  12. polybearsfootball
    Member
    Posted 6 months ago #

    @CoffeeMick,

    No fix on my end yet. I'm on WP 3.6, and BackWPup version 3.0.13. I thought I had solved the issue after changing the compression type, but it still fails after 1 run. This issue seems so common, the Dev not chiming in wrong. I realize this is free, and there is a paid Pro version, but seriously, if you release a free version that has such issues at least address it. I might of paid if the Dev was responsive, as I often do to show support for good devs doing strong work. In fact I love paying for good products, but the "lite" versions are supposed to convince me to buy. It's not like this problem is a "feature" you only get in the pro version, it's the basic required operation. How the hell do I know the paid version actually works. The complete lack of interaction makes me not want to buy, but I hope the Dev reads this and decides to help. Un-likely.

    Razz

  13. ukando
    Member
    Posted 5 months ago #

    Same here guys, we have the problem with resetting the schedule to December 31, 1969.
    Any suggestions how to solve that?

  14. Daniel Hüsken
    Member
    Plugin Author

    Posted 5 months ago #

    Please can you test the beta on https://github.com/inpsyde/backwpup. I think i have fixed it there.

  15. ukando
    Member
    Posted 5 months ago #

    Once installed beta, got the following error:
    Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /absolute-path-in-host/wp-content/plugins/backwpup-master/inc/class-admin.php on line 314

  16. Keith Aldrich
    Member
    Posted 5 months ago #

    Happening to me too. My backups stopped back in August and I didn't notice. Unfortunately, something broke my database around 3.7 or 3.7.1 update time and that's when I realized I hadn't been getting backups.

    Restored my database..set everything up again and after only 2 backups 2 of my jobs reset to December 31 1969.

    I'll try the beta and let you know if it is fixed there...

  17. Keith Aldrich
    Member
    Posted 5 months ago #

    I'd like to confirm that upgrading to the 3.0.14 beta release put my jobs back on schedule. No other action required.

  18. Daniel Hüsken
    Member
    Plugin Author

    Posted 5 months ago #

    The jobs will reschedule on activation of the plugin. Please look some times if the stay scheduled. Thanks.

  19. ed_monger-rue
    Member
    Posted 4 months ago #

    Daniel: I just downloaded the beta code (3.0.14-beta3) and thus far it seems to be working!

    The jobs were reschedule upon activation. I'll let it run for a couple of days and see how things work.

    Thank you!

    Cheers,
    Ed

  20. Daniel Hüsken
    Member
    Plugin Author

    Posted 4 months ago #

    thanks for the responce

  21. lrech
    Member
    Posted 4 months ago #

    I'm using 3.1-rc-1 version and still getting the backup jobs dates being reseted to 1969-12-31.

  22. Daniel Hüsken
    Member
    Plugin Author

    Posted 4 months ago #

    use the latest rc or wait for the release tomorrow.

  23. lrech
    Member
    Posted 4 months ago #

    I'm sorry, Daniel, but 3.1-rc-1 isn't the latest rc? I did not understand.

    By the way, the release 3.1-rc-1 should not have the changes where made at 3.0.14-rc-1 and before?

    If I'm wrong, tell me where I can download version 3.0.14-rc-1, because in github the only version available is 3.1-rc-1:
    https://github.com/inpsyde/backwpup/releases

  24. lrech
    Member
    Posted 4 months ago #

    Someone knows where I can download version 3.0.14-rc-1?

  25. Daniel Hüsken
    Member
    Plugin Author

    Posted 4 months ago #

  26. lrech
    Member
    Posted 4 months ago #

    I think that you don't understand my previous messages, Daniel. I'm using version 3.1-rc-1 and I'm worried about because you said that the problem with backup scheduling was resolved in version 3.0.14-rc-1. But I'm having the problem using version 3.1-rc-1! How a problem that happens in the version 3.0.13 whas solved in a RC of 3.0.14 and reappears in a RC of version 3.1?

  27. Daniel Hüsken
    Member
    Plugin Author

    Posted 3 months ago #

    We have switched from Version 3.0.14 to Version 3.1 because there are so many changes and 3.8 (Backend design) compatibility in the release. The next update is not longer 3.0.14 it is 3.1. We are sorry for the circumstances,

  28. ionutz_joe2009
    Member
    Posted 3 months ago #

    ok... wp-cron.php is the problem(low trafic).

    seve this in wp-config.php

    define('DISAMBLE_WP_CRON',true);

    example:

    efine('AUTH_KEY', 'put your unique phrase here');
    define('SECURE_AUTH_KEY', 'put your unique phrase here');
    define('LOGGED_IN_KEY', 'put your unique phrase here');
    define('NONCE_KEY', 'put your unique phrase here');
    define('AUTH_SALT', 'put your unique phrase here');
    define('SECURE_AUTH_SALT', 'put your unique phrase here');
    define('LOGGED_IN_SALT', 'put your unique phrase here');
    define('NONCE_SALT', 'put your unique phrase here');
    define('DISAMBLE_WP_CRON',true);

    if neded sudo apt-get install php5-cli

    in terminal type : crontab -e

    type this in window(last line):

    */1 * * * * php /var/www/wp-cron.php > /dev/null 2>&1
    control+x then save (y)
    this line will update wp-cron.php every minute(run wp-cron.php)

    change /var/www with your path to wp-cron.php

    for more informations http://wiki.dreamhost.com/Crontab
    My site have 0 trafic and may date does not reset any more and backwpup work now with cron.
    sorry for my english!!!!

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.