That was an intentional restart of the DB Server. I was monitoring the system because of the recent slowdown and decided that I had enough information logged that I could try to free up the jam.
The restart has seemed to settle things down, but I'm keeping an eye on it, and going to be examining the logs for the cause. I'm also going to be contacting our host to see what they think of it.
Sorry about that.
-Ibrahim
The restart has seemed to settle things down, but I'm keeping an eye on it, and going to be examining the logs for the cause. I'm also going to be contacting our host to see what they think of it.
Sorry about that.
-Ibrahim