mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

To test:

Set up a site and tun on 'Export to queue' option under Admin -> config
site -> User settings

Then as a user do an leap2a export via Portfolio -> Export

This should add the export to the queue

Then go to Admin -> Users -> Export queue

to see it in the queue - it should be there until next cron run for it
(about 5mins) make sure the cron runs and exports the item.

To replicate the problem you need to mimic the 'queue' export crashing -
when it crashes it doesn't clean up the cron lock - you can do this by
adding the following line to the database:

INSERT INTO config VALUES('_cron_lock_core_export_process_queue', '1');

Now do another leap2a export via Portfolio -> Export

This should stay in your export queue and when you press 're-queue' it
should not actually get it processed.


Then checkout patch and hit the 're-queue' button again, this should clear the lock, and eventually the cron should export it from queue.

-- 
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:
  In Progress

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