report_coursesize\task\report_async tasks generates Error reading database

[foxlapinou]

I have this plugin installed since some months/year. Now on Moodle 4.0 and 4.1.

On my site, it was planned each minute (on hour 7). I have each day several occurrences generating a database read error (terminating the cron). And after several tasks failed, one is OK. I've changed it to 6h30 and 6h50, but id does'nt change anything : i still have 3 (or 4) executions generating database read error before having it ok.

The error is (in text log of cron and tasks, because there is nothing in tasks reports in Moodle's UI when database error) :
Scheduled task failed: Poids des cours (report_coursesize\task\report_async),Erreur de lecture de la base de données
!!! Erreur de lecture de la base de données !!!

What i don't understand either is why it's executed several times, when i've defined it only to 6h30 and 6h50...

If you have ideas, and better, a solution, that would be helpful.

[danmarsden]

when a task fails Moodle will try to schedule that to run again using a faildelay process - what database type are you using? - are you running into #39 ? - What moodle version are you running? - can you try upgrading to the latest version of the code from github to see if that helps too?

[foxlapinou]

Hi Dan,
Thanks for your answer, and explanation about faildelay process ; it's certainly that. Yes, i wasn't clear enough about versions used. For the moment, it's latest stable for 4.0 and 4.1, so Moodle 4.0.10 and 4.1.5. And i use MariaDB (10.3.32 and 10.6.15). And latest version of plugin code in the plugins DB (and there doesnt seem to be something more recent on Github for that).
If you're talking about Moodle code, for sure i'll update to 4.0.11 and 4.1.6 when it's out in 2/3 weeks.
But in fact, i have this problem since several weeks/months.

[foxlapinou]

Would you have other suggestions, or things i could look for, to have more precise information?
I don't know if it's always on the files of the same course (maybe with lot of files), or if the queries in the plugin can be optimised to avoid this problem?