Am Sat, 23 Oct 2021 12:01:34 -0700
schrieb Jim Henderson
Digging into this a little more, it looks like there may be something problematic in the database. Looking at what config diagnostics I can and searching for answers, there's a reported fix for vBulletin 5 that *might* work if it's not a database corruption issue - increasing the execution time and the memory limit in config.php. (The recommended values were 2880 and -1, respectively).
As I'm not a fan of "unlimited resources", but on the other hand found some memory left unused on the machine: max_execution_time = 240 memory_limit = 3072M I hope this helps you already.
(b) that we have a good backup of the database in case things go really off the rails.
The latest DB backup is: 465360152 Oct 25 09:35 webforums.sql.xz (triggered manually). Usually, the backup job runs at 05:00 UTC every day. Regards, Lars