mahara-contributors team mailing list archive

[Kevin Dibble <1818082@xxxxxxxxxxxxxxxxxx>]

Hi Fiona,

The Release and archive of a portfolio it's tied to the Cron job.
Does your server team have the crop job running every 15 mins - or have they delayed it.

This is stated at:
https://wiki.mahara.org/index.php/System_Administrator%27s_Guide/Cron_Job

I note that this issue started since your upgrade. 
If the path or server changed - then the special job on the server called "CRON" needs to be updated as well.

Often during an upgrade - the cron gets overlooked.

Typically on Mahara (All versions i have used) any work due to be
released, gets released in seconds when cron runs.

To check this: submit work to a group - then release it, then manually
run CRON at:  https://[yourwebsite]/lib/cron.php?urlsecret=[your url
secret from the config.php file]

If the work gets released immediately - then see your server team about
the cron job... If not... then post back here and let me know.

** Changed in: mahara
     Assignee: (unassigned) => Kevin Dibble (digitalskill)

-- 
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/1818082

Title:
  Long delays after release of ePortfolio for archiving

Status in Mahara:
  New

Bug description:
  Since upgrading from 18.04 we have noticed a long delay for the group
  archiving process following the release of an ePortfolio from a group
  back to a student. It used to take 30mins for a 1 page eportfolio
  featuring 10 PDFs and 4 word documents to archive to LEAP2A. It is now
  taking more than 1 hour since we upgraded to 18.10.

  Interestingly we have found that the archiving is hanging for the
  first two submissions, but then if you submit a third ePortfolio and
  then release it that can hasten the first two into completing the
  archiving process. Upon checking the archived LEAP2A files they are
  fine.

  This is going to be a bit of a headache for us as students often
  accidentally submit before they are supposed to and 1 hour or more is
  a very long delay before they can resume work on their ePortfolio. As
  a result we are going to have to turn off archiving during submissions
  and then turn it on again in each group prior to ePortfolio release.

  Steps to complete:
  1. Student submits ePortfolio to a group which has archiving turned on.
  2. Academic releases ePortfolio back to student from the group.
  3. There is a long waiting period. Currently over 1 hour.

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