Does anybody have a quickfix for removing a file cron lock? Our cron has not run since Tues because it is unable to get the cron lock.
All of the files in moodledata/lock are empty. The directory permission is set to 777.
We are about to remount the NFS as there were network changes on Tuesday. Anything else we can try?
Another alternative would be switch to using the DB locking mechanism. The DB is the default locking location so unless you've already actively changed, you may just be looking in the wrong place.
Note: Locking over NFS is generally inadvisable.
I agree - locking files over NFS should not be used. My understanding is that it's either not supported or it will have a condition race - depending on the version of NFS one is using.
How do you actually switch locking mechanism? See the Moodle demo for example - login as admin and go to https://demo.moodle.net/cache/admin.php . There is only one option available under "Summary of cache lock instances" - and that is file locking.
In config.php
Isn't that only the case if the DB is Postgres? It defaults to file locking for other databases.
If you use postgresql, then your locks will be in the DB.
If you use any other DB, then in the filesystem - under <moodledata>/lock. In this case, you can delete everything under <moodledata>/lock and run cron. If new (empty) files and directories are not created, then your PHP process run from cron can not write there, for some reason. Restarting NFS may help.
Tomek
All of the files in moodledata/lock are empty. The directory permission is set to 777.
We are about to remount the NFS as there were network changes on Tuesday. Anything else we can try?
