eva2000
Tue 31st Oct '00, 6:11am
As some of you know i have had alot of problems with MySQL server going down, dying etc and freezing up the server. My host look into and am not sure how i should proceed now.. ? This is what they said
I'm very sorry to hear of your ongoing trouble with MySQL. Unfortunately however, MySQL is not a product we directly support. I have taken a look into this problem and have a few suggestions for you, but am not performing any action at this time since any service
we perfrom would be chargable at $75.00 per half hour.
First off, in looking at your MySQL .err log, I found where the problem was occurring. It seems that something on the system, either a user, a script, or a query, told MySQL to restart. When it attempted to bind port 3306, where it runs, my best guess is that one or more of the child processes had not stopped and therefore prevented the main process from grabbing the port again as it was already bound.
The biggest question I have at this point is, why was mysql restarted? Is this something you have setup, something that was done by hand possibly? If this is something that is scripted or done by hand, is there another method that can be used to produce the desired results?
Unfortunately, there is no way to find out under the current setup what caused the restart. If the source of the restart is unknown to you, I would suggest turning on logging for MySQL so that we have a better chance of finding the source. This would only need to be turned on long enough to catch a few instances of this problem, then it could be turned off again, the log files could get very large if left on for too long a period of time.
You might also check in the MySQL documentation at http://www.mysql.com if you haven't already done so. They might have some pointers or possible solutions for the problem.
As I said, any further troubleshooting on this matter, if in fact it is a MySQL issue and not something having to do with the OS, it will be billable, so please let us know your consent or denial to be charged in any future correspondence. now what should i do ? turn on logging ?
I'm very sorry to hear of your ongoing trouble with MySQL. Unfortunately however, MySQL is not a product we directly support. I have taken a look into this problem and have a few suggestions for you, but am not performing any action at this time since any service
we perfrom would be chargable at $75.00 per half hour.
First off, in looking at your MySQL .err log, I found where the problem was occurring. It seems that something on the system, either a user, a script, or a query, told MySQL to restart. When it attempted to bind port 3306, where it runs, my best guess is that one or more of the child processes had not stopped and therefore prevented the main process from grabbing the port again as it was already bound.
The biggest question I have at this point is, why was mysql restarted? Is this something you have setup, something that was done by hand possibly? If this is something that is scripted or done by hand, is there another method that can be used to produce the desired results?
Unfortunately, there is no way to find out under the current setup what caused the restart. If the source of the restart is unknown to you, I would suggest turning on logging for MySQL so that we have a better chance of finding the source. This would only need to be turned on long enough to catch a few instances of this problem, then it could be turned off again, the log files could get very large if left on for too long a period of time.
You might also check in the MySQL documentation at http://www.mysql.com if you haven't already done so. They might have some pointers or possible solutions for the problem.
As I said, any further troubleshooting on this matter, if in fact it is a MySQL issue and not something having to do with the OS, it will be billable, so please let us know your consent or denial to be charged in any future correspondence. now what should i do ? turn on logging ?