Visvanath, lockfiles make me think of Redis or php session lock files on the file system, but I assume this isn't what you've configured? Did you check the session settings in your config.php file? Lock files in the moodledata directory I've never heard of before, but this directory can become very large in size and number of files.
Alain Raap
Posts made by Alain Raap
Hi Severin,
Yes, both servers have the same configuration for CPU/RAM/Disk type and have the same optimizations.
I expected that Moodle 4.0 would be much faster on Redhat 8 for these kind of heavy tasks.
Yes, both servers have the same configuration for CPU/RAM/Disk type and have the same optimizations.
I expected that Moodle 4.0 would be much faster on Redhat 8 for these kind of heavy tasks.
Yesterday I tested a backup of another large course, this backup finished correctly. Only the time of the backup went from 1:10 hours (production) to 7:30 hours (Moodle 4.0). Anyone who has had the same experiences with Moodle 4.0 automated backups? Caching (Redis) is enabled on both environments, the difference is RHEL7 / PHP 7.2 (production) and RHEL8 / PHP 7.4 (Moodle 4.0).
I found out that the record of the large course in the backup_controllers table is missing. It looks like that this large course gets in conflict with the automated backup cron script that runs the same backup script and in the same time slot. Probably the automated backup cleans up the backup_controllers table at the end?
I am testing our automated backup process for Moodle 4.0 on a Redhat 8 environment (Apache 2.4/PHP 7.4/Mariadb 10.3), and our largest course that normally runs 9 hours outside our Moodle cron fails to complete. I'm getting this error now:
== Performing backup... ==
!!! error/backup_controller_dbops_nonexisting !!!
The other courses end normally after the automated course backup has finished.