cron job aborted by provider causes collateral damage

cron job aborted by provider causes collateral damage

by Pieter van der Hijden -
Number of replies: 1

My provider aborted the cron jobs of three Moodle sites. They took too much resources and ran for ever. This happened at night when the backups had to be produced. To avoid this in the future I minimised my backup needs and switched off the statistics.

It seems that the intervention above causes some collateral damage:

  • I do not see any files in my moodledata. To be more precise: via FTP I can see them, via the Moodle files-page I can see them, however, when linking to them, Moodle displays an empty rectangle.
  • Further, I cannot open admin/index.php and manually starting cron.php does not work either. What could be the cause?

I run 1.9... I cannot even see the the version number.

Help is welcome!

Best Regards,
Pieter van der Hijden

Average of ratings: -