1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Scheduled Tasks / Cronjobs Not Running Since Upgrade to PHP 5.3

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by DavidRA, Nov 24, 2011.

  1. DavidRA

    DavidRA New Pleskian

    12
    60%
    Joined:
    Nov 24, 2011
    Messages:
    4
    Likes Received:
    0
    Hi

    Plesk Version: Parallels Plesk Panel v9.5.4_build95101209.05 os_CentOS 5
    OS: Linux 2.6.34.6-xxxx-std-ipv6-32

    Since upgrading PHP to 5.3 (5.3.8-1 to be exact), our Scheduled Tasks / Cronjobs have not been running. I noticed this because our backup tasks have not run since the upgrade. I have checked the log at /var/log/cron and there are entries every 15 minutes for the backup task which is supposed to only run once at 03:00 every day and backup the server settings and content.

    The entries look like this:

    Nov 24 13:57:01 ks359302 crond[30754]: (root) CMD (/usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)

    So, the task is being logged, but is not being processed. I have run the following test:

    cd
    crontab -l > crontab.orig
    echo "* * * * * /usr/bin/date >> $HOME/cron_work.log" > crontab.file
    crontab crontab.file
    touch cron_work.log
    tail -f cron_work.log

    Again, the job is logged in /var/log/cron, but the cron_work.log file is empty. I have searched the forums for advice, but have mainly found advice for similar problems in Plesk 10. If anyone knows of cronjob issues when upgrading Plesk 9 to PHP 5.3, I would greatly appreciate the advice.
     
    Last edited: Nov 24, 2011
  2. DavidRA

    DavidRA New Pleskian

    12
    60%
    Joined:
    Nov 24, 2011
    Messages:
    4
    Likes Received:
    0
    We are also receiving email from the Cron Daemon stating:

     
  3. mbeijen

    mbeijen Guest

    0
     
    I have the same issue, anybody a solution for this problem?

    backupmng: Unable to fetch backup tasks from database: BIGINT UNSIGNED value is out of range in '(-(weekday(`psa`.`BackupsScheduled`.`last`)) + `psa`.`BackupsScheduled`.`backup_day`)'
     
    Last edited by a moderator: Dec 5, 2011
  4. mikcanavan

    mikcanavan Basic Pleskian

    23
    23%
    Joined:
    Dec 20, 2006
    Messages:
    25
    Likes Received:
    0
    Same issue here - running Plesk 9.5.4 and seems that since upgrading to PHP 5.3 I have the same issues described above.

    Anyone at Parallels shed any light?
     
  5. DavidRA

    DavidRA New Pleskian

    12
    60%
    Joined:
    Nov 24, 2011
    Messages:
    4
    Likes Received:
    0
    Have ended up upgrading to Plesk 10 via the Update button in the control panel. Plesk upgraded fine and the scheduled backups now work fine. Not really a fix, but a way out without reinstall then recovery of settings / site from backup.
     
  6. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Seems you have updated MySQL server too. Because error like
    caused by incompatibility between backupmng and MySQL 5.5. To prevent unsigned int overflow following MySQL query helped correct this issue:
    Try it. I hope it will help.
     
  7. mikcanavan

    mikcanavan Basic Pleskian

    23
    23%
    Joined:
    Dec 20, 2006
    Messages:
    25
    Likes Received:
    0
  8. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Thank you for sharing useful solutions from our forum :)
     
  9. egillette

    egillette Guest

    0
     
    Worked for me as well!

    Thanks!

    I was wondering why the backups were failing to run, and then I checked the cron log, and saw that message, which brought me here.

    Worked like a charm for me! =0)
     
Loading...