26 June 2011, 23:02

Hi,

I upgraded my mahara from 1.2 to 1.4 succesffully, for some reason, my cron job stopped sending messages. Here is my cron job log:

• [DBG] b9 (lib/cron.php:45) ---------- cron running Mon, 27 Jun 2011 15:54:01 +1200 ----------
• [DBG] b9 (lib/cron.php:146) Running core cron rebuild_artefact_parent_cache_dirty
• [DBG] b9 (lib/cron.php:502) Skipping long-running cron job core_activity_process_queue (Mon, 27 Jun 2011 10:33:52 +1200).
• [DBG] b9 (lib/cron.php:502) Skipping long-running cron job core_cron_check_for_updates (Mon, 27 Jun 2011 10:36:01 +1200).
• [DBG] b9 (lib/cron.php:168) ---------- cron finished Mon, 27 Jun 2011 15:54:01 +1200 ----------

I have also manually created a import directory under mahara data directory according to a bug report - https://bugs.launchpad.net/mahara/+bug/776955... cron job still not working for me.

-Lei

28 June 2011, 16:20

It's all sorted...manually create import directory in data directory and wait for long-running cron job to finish, mine takes overnight to finish.

29 June 2011, 3:42

Hi Lei,

Some cron jobs do take a long time to run and, from 1.4, the CRON system now skips over those jobs which are currently running. This is new in 1.4 so you won't have seen these messages before.

That said, the cron_check_for_updates job shouldn't take that long to run!

You've said in your other messages that it's all working now anyway, but it's perfectly acceptable for some jobs to take a very long time on a busy site.

If you know that a cron is *not* running and that it's lock file is stale, you can remove it. It's stored in the config table of the database.

Andrew

29 June 2011, 15:42

Thanks, Andrew. In fact, it's not a busy site at all. Only reason I can think of is cron job was not running for a long time prior to our upgrade to 1.4.

It's good to know lock file parameter in the config table, i'll check it if that happens again.

Lei