MySQL Bugs: #10950: Occational 'Error in mgm protocol parser' error on mysqld startup

Bug #10950	Occational 'Error in mgm protocol parser' error on mysqld startup
Submitted:	30 May 2005 2:35	Modified:	24 Aug 2005 18:20
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.11	OS:	Linux (linux)
Assigned to:	Stewart Smith	CPU Architecture:	Any

Description:
Occationally, during startup of mysqld, the following message is received.

Error in mgm protocol parser. cmd: 'get config' status=1, curr=(null)
Configuration error:

How to repeat:
only occurs sometimes on mysqld startup

Suggested fix:
don't have a problem getting configuration

we see this occationally from 4.1 and onwards

I have a hunch that this is because we're catching the mgm port still open from a previous run (e.g. the mgm server is shutting down) and we manage to connect, but not get any commands through (hence error in protocol).

In this case, we should retry the connection and it should work okay.

(btw, this is a hunch, not a solution, yet :)

A duplicate of this bug:
MySQL Bugs: #11404: mysqld process does not reconnect to cluster if MGM process moves

On mgm protocol error, we should check if we are still connected to the mgm server.

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/26556

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/28390

This does not affect 4.1 as the error message isn't there.

Pushed to 5.0.12

Documented in 5.0.12 changelog:

<listitem><para>Wrong error message displayed when cluster management server closes port when mysqld is connecting. (Bug #10950)</para></listitem>