MySQL Bugs: #24547: Error after shutdown of stopped nodes

Bug #24547	Error after shutdown of stopped nodes
Submitted:	23 Nov 2006 15:04	Modified:	10 Aug 2007 13:42
Reporter:	Geert Vanderkelen	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
I found this problem while verifying bug 24105. After running the shell script for that bug I did a shutdown of the cluster while the nodes were in 'not started' state. This resulted in a temporary error on the node that was used in the shell script with the -n option.

How to repeat:
Run the shell script attached to this bug. It's the same as bug 24105.

 shell> ./bug_24105.sh

Then do:
 shell> ndb_mgm -e "SHUTDOWN"

And start again the ndb_mgm with the 4 nodes (config also attached). The node that was used with -n option will fail with this message (trace uploaded):

Time: Thursday 23 November 2006 - 15:44:59
Status: Temporary error, restart node
Message: Internal program error (failed ndbassert) (Internal error, programming error or missing error message, please report a bug)
Error: 2343
Error data: dblqh/DblqhMain.cpp
Error object: DBLQH (Line: 3577) 0x0000000a
Program: ./libexec/ndbd
Pid: 25786
Trace: /var/mysql/51bk/ndb_3_trace.log.16
Version: Version 5.1.14 (beta)
***EOM***

Configuration

Attachment: 51bk-quattro-config.ini (application/octet-stream, text), 708 bytes.

Shell script for repeating

Attachment: bug_24105.sh (application/x-shellscript, text), 606 bytes.

Tracefile going with the error message

Attachment: ndb_3_trace.log.16.gz (application/x-gzip, text), 49.68 KiB.

Verified using 5.1bk on Linux.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Just a note to confirm I can't repeat anymore in latest build from bitkeeper, and also not with 5.1.20.