MySQL Bugs: #23203: ndb_mgmd seg fauts on all dump 1000

Bug #23203	ndb_mgmd seg fauts on all dump 1000
Submitted:	12 Oct 2006 9:06	Modified:	2 Nov 2006 10:04
Reporter:	Bernd Ocklin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.0.26 max	OS:	Linux (Suse 10.1)
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
If the data nodes are connected to the management server but not yet started the ndb_mgmd will seg fault if the command all dump 1000 is issued to the management console.

How to repeat:
1. start ndb_mgmd
2. start nodes with ndbd -n
3. start ndb_mgm
4. issue command ndb_mgm> all dump 1000

Suggested fix:
Catch the command if the data nodes are not started and don't execute it.

Changed category to a more appropriate one.

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/commits/13648

ChangeSet@1.2259, 2006-10-13 12:09:41+02:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#23203
    1) Handle not started nodes in dump 1000 (check for division by 0)
    2) Make sure to init variables in constructor

pushed to 5.0-ndb

pushed into 5.1-ndb

pushed into 5.0.29

pushed into 5.1.13

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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix for 5.0.29 & 5.1.13.

*Fix for 5.0 documented in 5.0.30 Release Notes.*

*Fix for 5.0 documented in 5.0.30 Release Notes.*