at midnight (which was 3:00 in the morning, florida time), i got a message saying that the database was blowing up again. they said it was 183 GIGABYTES…
because of the fact that i was asleep (thankfully), i didn’t actually read the message until 7:00 my time (10:00 florida time). i immediately logged into my web server, and discovered that the MySQL disk usage was lower than i have ever seen it before, which is to say 253 MEGABYTES
what this tells me is that there’s something else going on besides this whole “enfold-theme-not-caching-correctly” horseshit.
which is bad.
it also tells me that, whatever it is, we haven’t actually found it… we may have found another problem, but not the one for which we’re looking… yet…
which is bad, but not as bad as it could be.
it also tells me that, whatever it is that is going wrong, the cronjob that we put in place to solve the problem, works, REGARDLESS of the actual problem.
which is good.
but, when it comes right down to it, it is not good for me to be so stressed out about something over which i have very little control.
which is bad.
something has to be done. this is ridiculous.