=> Whatever MySQL does, the system should not reboot. If
=> everything is cool, but MySQL is at fault, you will see
=> 99% CPU eathen up, hard disks going wild, segfaults and
=> other nasty things, but not a cold reboot. Looks like
=> a hardware problem of some kind. Maybe there is an evil
=> gnome in your server room that pull a prank on you once
=> in a while by hitting the reset button :) ?
That's just is tho... we figured this was probably anything but mySQL, but
the thing is this:
At 12:30 (noon and midnight) we have several PHP scripts from other
machines connect to the server and issue some queries. This is precisely
when the client will reboot (not the server tho), the moment this script is
run. We can tell, because the scripts writes output to a file, and the file
is only being opened and not written (failure of a flush when the reboot
occurs).
We figured it might be something else, but it only seems to happen at this
particular time (when our database is at it's most busiest because alot of
our servers are querying it for info). We did attempt to stagger the
machines so that they don't all connect at the same time, and that appeared
to work for a while, but then the problem returned (after about a month).
As if this weren't bad enough, just recently the server decided to crash
(although it never did before, only the clients).
Nonetheless, I'm going to try compiling mySQL myself instead of using a
binary and doing so w/the latest build and see if this problem repeats
itself at all. I was wondering if someone else had this particular problem
before I do this tho (it may not work).
TIA.
-----
Sumbry][ | Affinity Hosting | http://affinity.net | sumbry@stripped
"If I save time, when do I get it back?"
