MYSQL KEEPS CRASHING HELP!!!

Anon

Hi All,

I have a serious Mysql problem. I've got a Mysql + php3 website running for the pat one yr now.

Mysql had never given any problems but suddenly the mysql deamon has started showin erratic behaviour. The deamon starts itself (/rc.d/inintd/mysql) and stops working after a few hits 2 the site. Staring the deamon again does not help for long since after a few hits it crashes again!

The err file in /var/lib/myswl reads..

Number of processes running now: 0
mysqld restarted on Fri Jan 19 10:44:20 IST 2001
010119 10:44:20 Can't start server: Bind on TCP/IP port: Address already in use
010119 10:44:20 Do you already have another mysqld server running on port: 330$
010119 10:44:20 Aborting

mysqld ended on Fri Jan 19 10:44:20 IST 2001

I have checked and there is no other thread running on 3306. Also nothing in /etc/services is running on 3306 except....

mysql 3306/tcp # MySQL

mysql 3306/udp # MySQL

I cant get to solve this one guys pl throw sum help 🙂!!!

Manpreet.

[deleted]

It doesn't have to be MySQL running on that port, anything taht binds to that port will stop MySQL from binding to it.

And what kind of queries do you run to make it crash?

Anon

Might it be a corrupted dataset? It might be worth trying to dump out the tables one at a time and see if one of them makes the mysql daemon puke.

It's also possible a library that mysql uses has become corrupted. I'd try backing up the data on that box and building a replacement for it, as it could be hardware, software, or any number of problems causing this to happen.

[deleted]

A corrupted dataset should cause MySQL to throw an error, not crash.
Corrupted tables are quite easy to check by reading the MySQL manual about the isamchk function. That function will check your data for errors without dumping them out.

I wouldn't try backup up the data now, because now it is already corrupted.
If you would build a copy of the server, you'd build it off a backup that was done before the error started happening.

Note: save your existing backups for now, don't overwrite them. The cause of the problem may have been around for a while, you may have to restore an 'older' backup that you are about to overwrite with the new and corrupted data.

I don't think this is a hardware error (except for HD failure), becuase that would affect the whole system, not just MySQL after some activity.

I guess MySQL barfs out on a bad query (maybe one that either reads corrupted data or one that exceeds the limits of your setup) and doen't release the port.
That way a new MySQL process can't bind to the port.

Check the FAQ's and search search search the net. There's far more info out there than in here :-)

Anon

hey i'm having exactly the same problem ... have u found anything on this yet ? MySQL crashes or restarts unexpectedy during queries .. this results in lots of connection failures !! i've tried a million things .. nothing seems to work .. HELPPPP !!!

Anon

ya i found a solution~~~!!!

i converted to Oracle!!

hope this helps!!

smarlowe

If the problem is bad hardware, not mysql, then converting to Oracle or any other DBMS would simply result in a different kind of unreliability.

Test the hardware first. If running on Linux, write a script to compile the kernel a hundred times and see if you get any sig 11s while compiling.

Anon

I have the same problem. Please post any solution here!

Anon

I solved my problem.
Here it is:

Use "ps" unix command to find out what PID is the crashed mysqld.

Example:
%ps
PID TT STAT TIME COMMAND
1108 p2 Ss 0:00.13 -tcsh (tcsh)
11517 p2 R+ 0:00.00 ps
55777 p2- I 0:00.18 /usr/local/mysql/libexec/mysqld

In the above example the PID of MySQL daemon is 55777.

Now kill it!
Issue this command (change the PID 55777 to match yours):
%kill -9 55777

Now you can run mysqld again: the port is free!!!

Essell wrote:

[deleted]

That's just how to fix it once it has crashed, you need a way to stop it from crashing :-)

Anon

Use isamchk!

vincent wrote:

That's just how to fix it once it has crashed, you need a way to stop it from crashing :-)

[deleted]

Ehm... again, that's only once it has already failed.
The tables get corrupted when mysqld fails.
You need to find the reason why mysqld stops in the first place.

Anon

I understand.
My MySQL seems stable now (after I reinstalled it from scratch and recreated tables from SQL files I kept, using myPHPadmin 2.1.0).
I it drops again, I will investigate further (I hope that won't happen!)

Still I can't understand why mysqld failed the first time. No obvious reason so far.

Be sure that if I found what was wrong, I will post here.

Thank you for your time.

vincent wrote:

Ehm... again, that's only once it has already failed.
The tables get corrupted when mysqld fails.
You need to find the reason why mysqld stops in the first place.