Re: Unstoppable automated backups in 3.5

Hi Ken,

Thanks for the tips. max_allowed_packet is already set to 16M. Will try bumping it up higher. I've run MySQLTuner in the past but it's been awhile so we'll give it another shot.

Lots of log files in moodledata/temp/backup/ that are > 0 bytes. As you said, they don't really give me much info (see below).

Also a fair number of hashed directories in there, with backup.mbz and the standard selection of .xml files that backups are composed of.

[Sat 26 Sep 2020 13:39:43 PDT] [info] instantiating backup controller e0570c3e9c69c1a57999cf843b7018a3
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting controller status to 100
[Sat 26 Sep 2020 13:39:43 PDT] [debug] loading controller plan
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting controller status to 300
[Sat 26 Sep 2020 13:39:43 PDT] [debug] applying plan defaults
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting controller status to 400
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting file inclusion to 1
[Sat 26 Sep 2020 13:39:43 PDT] [info] checking plan security
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting controller status to 700
[Sat 26 Sep 2020 13:39:43 PDT] [debug] saving controller to db
[Sat 26 Sep 2020 13:39:43 PDT] [debug] calculating controller checksum 02f716732c1c02c6456f0b5b3a5a82bc
[Sat 26 Sep 2020 13:39:43 PDT] [debug] loading controller from db
[Sat 26 Sep 2020 13:39:43 PDT] [debug] setting controller status to 800

I'll start with a re-run of Tuner and a bump of the max_allowed_packet, and will see where that gets me. Thanks for the tip re: the scripts in admin/cli/.

For the short term, I've set up a cron job to run tmpreaper (super-handy!) against the moodledata/temp/backups directory and prune anything out that's older than 3 hours, while not breaking backups-in-progress - that should keep the directory size under control while I sort this out.

Regards,
-- Mike K