Bug #12045 ndb_mgmd PID fails to be found during "shutdown" if there is mutiple ndb_mgmd
Submitted: 20 Jul 2005 0:20 Modified: 20 Jan 2006 14:51
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:4.1-> OS:Linux (Linux)
Assigned to: Stewart Smith CPU Architecture:Any

[20 Jul 2005 0:20] Jonathan Miller
When you have more then 1 ndb_mgmd process in a cluster, the ndb_mgm -e "shutdown" fails to shutdown any of the processes except the ndbd processes.

one ndb_mgmd process:
ndb08:/space/run> ndb_mgm $ndbc -e "shutdown"
Connected to Management Server at: ndb08:14000
6 NDB Cluster storage node(s) have shutdown.
NDB Cluster management server shutdown.

Three ndb_mgmd processes:
@ndb08:/space/run> ndb_mgm $ndbc -e "shutdown"
Connected to Management Server at: ndb08:14000
6 NDB Cluster storage node(s) have shutdown.
Unable to locate management server, shutdown manually with <id> STOP

How to repeat:
setup 3 servers in a cluster with each having a ndb_mgmd process.
Issue a cluster "shutdown" request.

Suggested fix:
All ndb_mgmd processes in the cluster should shutdown following a shutdown request.
[16 Jan 2006 13:20] Stewart Smith
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


This should be the same fix as for BUG#12124.

Although I'm reluctant to port this back to 4.1 as it relies on the behaviour introduced in 5.0 of (in ndb_mgmd) connecting back to our own ndb_mgmd to use the mgmapi to report the port numbers we've set up to use for Transporters.
[19 Jan 2006 10:33] Stewart Smith
fix for BUG#12124 has been pushed to 5.0.19
[20 Jan 2006 14:51] Jon Stephens
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

Additional info:

Documented in 5.0.19 changelog. Closed.