No, I meant VPS:
Forgive me, Father A., for I hadn't seen a VPS until today. I'm familiar with emulators and virtual Operating Systems, but not Virtual Servers. Clearly, a VPS doesn't give this application full access to CPU, RAM and Disk as it lives basically in a chunk of disk space somewhere on a bigger server. If the database starts approaching the disk limits, it will act funny and crash; That's been my experience in the past with tape backup databases when they grow large and crash without warning in a middle of backup job.
The mysqld log seems to go back to then. The httpd log only dates from today.
That's odd - the VPS probably restarts the httpd daemon every day, clearing the log files to conserve on disk space unless the log files are moved elsewhere?
Cleveland has seen the error he posted above, but we also have experienced errors which cause the httpd process to abruptly stop and it has to be restarted. Are the two things related? Maybe. Too early to say.
httpd hangs. I've never seen httpd restarted daily on a LINUX server. Most LINUX servers I dealt with stayed up for months.
Thank you for the reference and I will have a look.
You're welcome. The link helped many people resolve upgrade problems due to changing one word in a SQL script file.