mahara-contributors team mailing list archive

[Kristina Hoeppner <1557160@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Reported on bug #1549947:

All of our courses (groups) are configured to archive submissions before
release, so while the export_process_queue CRON task was processing
about 150 collections (600 pages), PHP encountered a max_run_time error,
and stopped the task partway through, so some were archived, but none
were released.

The export_process_queue task locks itself when it starts and cannot be
run again until it has finished, but if it crashes it does not unlock.

So for about 36 hours after this task crashed, anything that was flagged
for release just said "Pending release after archiving" and nothing
happened. I had to go into the config table in the database and deleted
the lock, and clear out the export queue.

So this potential error will need to be handled in some way, otherwise
it will probably happen a lot more often if an entire class can be
flagged for archiving & release all at once. 150 collections was only
1/4 of the class.

** Affects: mahara
     Importance: High
         Status: Triaged

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1557160

Title:
  PHP error when releasing and archiving submissions

Status in Mahara:
  Triaged

Bug description:
  Reported on bug #1549947:

  All of our courses (groups) are configured to archive submissions
  before release, so while the export_process_queue CRON task was
  processing about 150 collections (600 pages), PHP encountered a
  max_run_time error, and stopped the task partway through, so some were
  archived, but none were released.

  The export_process_queue task locks itself when it starts and cannot
  be run again until it has finished, but if it crashes it does not
  unlock.

  So for about 36 hours after this task crashed, anything that was
  flagged for release just said "Pending release after archiving" and
  nothing happened. I had to go into the config table in the database
  and deleted the lock, and clear out the export queue.

  So this potential error will need to be handled in some way, otherwise
  it will probably happen a lot more often if an entire class can be
  flagged for archiving & release all at once. 150 collections was only
  1/4 of the class.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1557160/+subscriptions