From my research, it seems to me that this error is saying that the OS hard coded limits keeps getting hit and that I should use the innoDB heavy .ini file. However, I do not know what the implications will be for my sites using MySQL. Below is the heavy innoDB configurations I am thinking of replacing it with, can anyone tell me what this will mean for my sites with existing databases? They are all InnoDB and even all their tables are InnoDB. Am I on the right track?

What is the error? That first line you quoted isn't an error message. So what is in the event logs? Also, when you say "server", do you mean the OS, as indicated by the title, or the MySQL service?
–
John GardeniersApr 19 '10 at 22:21

You are right, the first line I quoted was actually a "warning" from the event logs. As soon as that message gets logged, the server crashes and reboots. There are no errors besides this warning.
–
TruMan1Apr 19 '10 at 23:11

What about the Windows even logs? Nothing there at all?
–
John GardeniersApr 20 '10 at 1:14

3 Answers
3

I don't think MySQL should ever kill your operating system, even if it's misbehaving. What you describing is not normal for a healthy server. In the worst case, the MySQL instance should die, not the whole server.

You should investigate for possible hardware problems, such as insufficient cooling or bad RAM chips. So you should rule those out first.

If you agree that this might indeed be a hardware problem, here is what you could do:

improve cooling. Maybe open the server case and leave it running this way to prove the theory.

burn a memcheck live CD and do a quick RAM check. This requires a reboot, but I reckon your server is giving you daily opportunities, right? ;-)

It should improve response and performance for all sites using an innodb database. They will not stop working because of these changes. I do suggestion doing the tunning during off peak hours. The config list is a good start, but ultimately you will have to fine tune it to meet your needs best. I made use of the page of phpmyadmin to turn the server.

I'd change the innodb_buffer_pool_size = 2G to 1GB since you only have 3GB of ram and you need enough for the system to run

Did you end up using the "socket = /tmp/mysql.sock" setting? I do not know what that is, but it is not in my current settings.
–
TruMan1Apr 19 '10 at 22:11

The socket functions are pretty clearly documented, as well as all of the other settings you are thinking of changing. It's best to know as much as you can about the systems you are managing, so would really recommend putting in some study time before throwing a bunch of settings changes you don't understand onto a production server. Also, what Yves said above: the entire server OS rebooting is not normal behaviour, and I would look to things outside of MySQL for the cause. One thing he didn't mention is to check your OS's open file limit. If MySQL using them all up, the OS might go belly up.
–
ryandenkiAug 22 '11 at 1:54