TheTrinity
06-11-2006, 06:04 PM
I'm trying to resolve a problem with automatic backups in Moodle (PHP/MySQL).
I use cron to automate the maintenance functions in Moodle and everything works fine, except for a couple of courses which seem to fail because they take too long to execute. Here's how I execude the cron:
/usr/local/bin/php /home/myaccount/public_html/admin/cron.php
It works fine, except for the automatic backup of two large courses. Examination of the Moodle backup logs, shows that everything appears to be going fine, but the backup is terminated before completion. When the backups took 10-12 minutes, they worked fine. The last time-marker in the log shows that it's now taking more than 18 minutes. I'm guessing that the process is being terminated at about 20 minutes; but it looks like it will need another 10 minutes or so to finish.
Is there a way to extend the time for the process to run? And can I confirm whether or not the process (that particular cron instance) is being terminates by the server?
(My other theory is that it's taking too much disk space, but this seems unlikely since there's about 170MB free in that account.)
Any suggestions would be appreciated.
Paul.
I use cron to automate the maintenance functions in Moodle and everything works fine, except for a couple of courses which seem to fail because they take too long to execute. Here's how I execude the cron:
/usr/local/bin/php /home/myaccount/public_html/admin/cron.php
It works fine, except for the automatic backup of two large courses. Examination of the Moodle backup logs, shows that everything appears to be going fine, but the backup is terminated before completion. When the backups took 10-12 minutes, they worked fine. The last time-marker in the log shows that it's now taking more than 18 minutes. I'm guessing that the process is being terminated at about 20 minutes; but it looks like it will need another 10 minutes or so to finish.
Is there a way to extend the time for the process to run? And can I confirm whether or not the process (that particular cron instance) is being terminates by the server?
(My other theory is that it's taking too much disk space, but this seems unlikely since there's about 170MB free in that account.)
Any suggestions would be appreciated.
Paul.