Bug #5435 "all stop" command crashes MySQL server
Submitted: 6 Sep 2004 17:53 Modified: 10 Sep 2004 17:14
Reporter: Victoria Reznichenko Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1 OS:Linux (Linux)
Assigned to: Tomas Ulin CPU Architecture:Any

[6 Sep 2004 17:53] Victoria Reznichenko
"all stop" ndb_mgm command crashes MySQL server.

# ./bin/ndb_mgm localhost 2200
-- NDB Cluster -- Management Client --
Connecting to Management Server: localhost:2200
NDB> all stop
Executing STOP on all nodes.
Shutdown failed.
*  1006: Illegal reply from server


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 131081 (LWP 9744)]
0x00000002 in ?? ()
(gdb) Quit
(gdb) bt
#0  0x00000002 in ?? ()
#1  0x087581f0 in ?? ()
#2  0x00000002 in ?? ()
#3  0x08742808 in ?? ()
#4  0x08370393 in TransporterFacade::ReportNodeAlive (this=0x87581f0, tNodeId=0) at TransporterFacade.cpp:678
#5  0x08370aaa in TransporterFacade::reportDisconnected (this=0x87420f8, aNodeId=2)
    at TransporterFacade.cpp:944
#6  0x0836f72b in reportDisconnect (callbackObj=0x87420f8, nodeId=2, error=0) at TransporterFacade.cpp:115
#7  0x083743a5 in TransporterRegistry::report_disconnect (this=0x8742808, node_id=2, errnum=0)
    at TransporterRegistry.cpp:1076
#8  0x08382c55 in TCP_Transporter::doReceive (this=0x8743eb0) at Transporter.hpp:133
#9  0x0837413e in TransporterRegistry::performReceive (this=0x8742808) at TransporterRegistry.cpp:833
#10 0x0836ffce in TransporterFacade::threadMainReceive (this=0x87420f8) at TransporterFacade.cpp:526
#11 0x0836ff47 in runReceiveResponse_C (me=0x87420f8) at TransporterFacade.cpp:510
#12 0x4017414b in pthread_start_thread () from /lib/libpthread.so.0
#13 0x401741df in pthread_start_thread_event () from /lib/libpthread.so.0
#14 0x402df50a in clone () from /lib/libc.so.6

How to repeat:
Set up MySQL Cluster as described at:

Start mysqld_safe.
Start ndb_mgm.
Execute: all stop
[10 Sep 2004 17:14] Tomas Ulin
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at