Dear all,
I've installed MySQL 3.23.33 on my Slackware7 box, prior I used 3.22.x and started MySQL by root everything gonna be fine.
After I installed 3.23.33, I followed the installation instruction by creating a user called 'mysql' and use that username for start/stop MySQL, firstly It seemed smooth! but when it runs for couple hours. MySQL is die by itself 'n when I 'ps ax' show the process there is a line look like...
[mysqld <defunct>]
'n it's gonna be a zombie process.
So that, I follow the MySQL troubleshooting issues on MySQL.com and use 'strack trace'
to get the error in host.err looks like this..
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died
Attemping backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong
Cannot determine thread, ebp=0xbffff00c, backtrace may not be correct
stack range sanity check, ok, backtrace follows
0x40072dfe
0x40071949
0x40073717
0x4012e72d
0x4012bc30
0x8168d29
0x1
New value of ebp failed sanity check terminating backtrace
,so I executed resolve_stack_dump to find out what that numbers mean.. and I got the out put like this..
/usr/local/mysql/bin/resolve_stack_dump -s ./mysqld.sym -n mysql.stack
0x40072dfe end + 937996090
0x40071949 end + 937990789
0x40073717 end + 937998419
0x4012e72d end + 938764393
0x4012bc30 _end + 938753388
0x8168d29 rfc931 + 525
0x1 (?)
Please help me to figure out, what is happening?
Thank you for your patient to read my long message!
Prachid T.
