Cron script not running about bitnami-docker-moodle HOT 6 CLOSED

Hi,

Thanks for letting us know. We will try to reproduce the issue to see if the warning appears to us as well.

from bitnami-docker-moodle.

Hi,

In the first test I did, I just did this small operation inside the container.

sed -i 's|/dev/null|/tmp/test|g' /etc/cron.d/moodle

Then:

cat /tmp/test

Scheduled task complete: Incoming email pickup (tool_messageinbound\task\pickup_task)
Execute scheduled task: Cleanup event monitor events (tool_monitor\task\clean_events)
... started 10:26:02. Current memory use 25.3MB.
... used 0 dbqueries
... used 0.00020694732666016 seconds
Scheduled task complete: Cleanup event monitor events (tool_monitor\task\clean_events)
Cron script completed correctly
Cron completed at 10:26:02. Memory used 25.3MB.
Execution took 0.470763 seconds

Could you check if this is ocurring in your container as well? If so, then the problem is that the Moodle web-app is not detecting that the cron job is being executed.

from bitnami-docker-moodle.

Hi,

It would seem that the cron script is simply not running in my deployment. /tmp/test is never created after doing what you suggest.

from bitnami-docker-moodle.

I've changed the /etc/cron.d/moodle contents to:

*/1 * * * * echo "run" > /tmp/test2; bitnami sudo su daemon -s /bin/sh -c "/opt/bitnami/php/bin/php /opt/bitnami/moodle/admin/cli/cron.php > /tmp/test"

And even /tmp/test2 isn't created either. However, service cron status returns cron is running. I'm dumbfounded.

from bitnami-docker-moodle.

After some more tests, I am inclined to believe it was a permission issue due to the persistence volumes being bind-mounted rather than named volumes. Just restarting the container seems to have solved it.

To anyone that may find this issue in the future: don't try to bind-mount these volumes, and be very careful with file ownership if you do.

from bitnami-docker-moodle.

Hi,

Thanks for letting us know. Bind mounting folders is always problematic when working with docker. This is even worse in the case of non-root containers. If you find any other issues, do not hesitate to open a new ticket

from bitnami-docker-moodle.