by Perry Way.
Hi Ken, Thanks for responding.
I have a little time to dig in a little deeper. I went to where the exception is thrown in the code and outputted the object $this using print_r() and that's what is in the attachment of this response.
I had a look around in the moodledata/temp folder, I did not find any errant backup.mbz files. All I saw were *.log files with the name corresponding to folders that contain the data that later gets zipped up to .mbz.
Part of me wants to empty the folder entirely and try a manual backup interactively. These folders here are remaining from our system that creates new courses from template courses the beginning of each new term. I don't need these folders, right? It's not going to hurt the system if I delete them? Just wondering if that's the case. I could copy them to another folder and then return them later if it's a problem I guess. Maybe I will hack around.. and see, a bit later.
The exception is thrown when $this->status is not that backup::STATUS_SETTING_UI. And if you look at my file, the numeric value in the $this object is 700 which equates to backup::STATUS_AWAITING. Not sure if this adds any useful hint.
Ownership permissions are not a problem. It's been working just fine until this new version of Moodle. No alterations of any kind were made to the moodledata folder.
Timing out is not the issue. The exception happens immediately without any delay whatsoever. It happens so fast I wondered if anything executed at all, frankly. We've corrected those things a long ago and have a nicely tuned system, highly responsive even without Wincache which is totally and irretreivably busted. (Side Note: That Wincache does not work at all in PHP 7.0.x I've done everything under the sun and it spits out system errors faster than you can manage).
I like how you end everything with spirit of sharing. I've always had that attitude myself. Freedom of information! Let truth prevail!
Knowledge and wisdom. Two things Solomon requested. 😊
Perry