mahara-contributors team mailing list archive

[Hugh Davenport <776955@xxxxxxxxxxxxxxxxxx>]

The cause for this was because one of the cronjobs was checking in the import directory of the maharadata directory.
If this didn't exist, it complained with ugly error.

The patch at https://reviews.mahara.org/112 fixes this by adding a check
for the import directory.

Another solution is that the import dir is made at install time.

Heinz, you can fix this for you by either waiting till it appears
upstream, or do the following.

make a directory maharadata/import, where maharadata is the directory specified in config.php
this directory must be owned by the user that runs the webserver (ie www-data, or apache)
Then you have to wait for 24 hours since this cronjob was started, then it will try again.
You can keep the entry in your crontab, but just check after 24 hours.

Cheers,

Hugh

** Changed in: mahara
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/776955

Title:
  /admin shows cronjob not running altho it is ok

Status in Mahara ePortfolio:
  In Progress

Bug description:
  Hi,

  I installed mahara 1.4 (Mahara version 1.4.0alpha2dev (2011042000) 
  the cronjob is running, but the site shows:
  Cron: Cron is not running.
  See the installation guide for instructions on how to set it up.