MySQL Bugs: #15215: mysqld fails at start-up because of illegal reply from mgmd

Bug #15215	mysqld fails at start-up because of illegal reply from mgmd
Submitted:	24 Nov 2005 6:16	Modified:	1 Feb 2006 3:26
Reporter:	Stewart Smith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.0.15, 5.1	OS:
Assigned to:	Stewart Smith	CPU Architecture:	Any

Description:
mysqld connects to a mgm server, then the mgm server goes away before a node id can be allocated.

mysqld-err.trace:

Error in mgm protocol parser. cmd: >get nodeid< status: 2 curr: -1073748832
Error in mgm protocol parser. cmd: >get nodeid< status: 2 curr: -1073748832
Error in mgm protocol parser. cmd: >get nodeid< status: 2 curr: -1073748832
Error in mgm protocol parser. cmd: >get nodeid< status: 2 curr: -1073748832
Configuration error: Illegal reply from server :
051112 15:04:08 [ERROR] Can't init databases
051112 15:04:08 [ERROR] Aborting

How to repeat:
in ndb_mgm_alloc_nodeid, before mgm_call, add a printout and a sleep. When running mysqld, unplug the node from the network when this printout is reached.

This is very hard to hit intentionally without modifying the source.

Suggested fix:
display a better error message and/or retry the mgm server connection.

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:

  http://lists.mysql.com/internals/32640

pushed to 5.0.17

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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented fix in 5.0.17 changelog.

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:

  http://lists.mysql.com/internals/33359