Bug #7303 ndb_mgm: Trying to set CLUSTERLOG for a specific node id core dumps
Submitted: 14 Dec 2004 23:34 Modified: 15 Dec 2004 12:38
Reporter: Todd Carter Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:4.1.7 OS:Solaris (Solaris 2.8)
Assigned to: Tomas Ulin CPU Architecture:Any

[14 Dec 2004 23:34] Todd Carter
Description:
When I try to set the indivdual nodeid CLUSTERLOG level I get a core dump of ndb_mgm when I don't specify the <category>=<level>.

How to repeat:
/usr/local/mysql/bin/ndb_mgm
-- NDB Cluster -- Management Client --
Connecting to Management Server: localhost:2200
NDB> show
Cluster Configuration
---------------------
[ndbd(NDB)]     1 node(s)
id=2    @127.0.0.1  (Version: 3.5.3, single user mode, Nodegroup: 0, Master)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @127.0.0.1  (Version: 3.5.3)

[mysqld(API)]   3 node(s)
id=3    @127.0.0.1  (Version: 3.5.3)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)

NDB> 3 CLUSTERLOG ALERT=DEBUG
Executing CLUSTERLOG on node 3.
Unknown category: "ALERT"

NDB> 3 CLUSTERLOG DEBUG=ALERT
Executing CLUSTERLOG on node 3.
Executing CLUSTERLOG on node 3 OK!

NDB> 3 CLUSTERLOG
Executing CLUSTERLOG on node 3.
Segmentation Fault (core dumped)

Suggested fix:
Correct Error Handling in ndb_mgm for null values on the given command - It does understand unvalid responses - just not null ones :)
[15 Dec 2004 12:38] Tomas Ulin
fixed in 4.1.8