In the last episode (Jul 06), Dilipan Sebastiampillai said: > our server crashed yesterday with the following error : > > do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused > do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused > do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this > binary or one of the libraries it was linked against is corrupt, > improperly built, or misconfigured. This error can also be caused by > malfunctioning hardware. We will try our best to scrape up some info > that will hopefully help diagnose the problem, but since we have > already crashed, something is definitely wrong and this may fail. [..] > resolved stack gives : > > 0x80f7893 handle_segfault + 399 > 0xc5ed96 (?) > 0x82ab930 strnmov + 24 > 0x8158a17 innobase_mysql_print_thd + 471 > 0x82302c1 lock_print_info + 1573 > 0x819f373 srv_sprintf_innodb_monitor + 507 > 0x815d4e2 _Z18innodb_show_statusP3THD + 138 > 0x8105657 _Z21mysql_execute_commandv + 5999 > 0x810868d _Z11mysql_parseP3THDPcj + 329 > 0x8103321 _Z16dispatch_command19enum_server_commandP3THDPcj + 1069 > 0x8102eb8 _Z10do_commandP3THD + 100 > 0x810280d handle_one_connection + 841 > 0xc59e51 (?) > 0x50e06a (?) > > this is a Mysql 4.0.18 on a dedicated linux Red Hat Enterprise Linux ES > release 3 ( kernel 2.4.21-20 ) with 3 Gig RAM > > could you tell me what happened please?
It looks like the innodb "show status" command crashed trying to print its list of locks. You might want to upgrade to 4.0.27 (or even 4.1.* or 5.0.*). I don't see any bugfixes specifically related to your problem, but 4.0.18 is 2 years old. http://downloads.mysql.com/archives.php?p=mysql-4.0 -- Dan Nelson [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
