Bug #30357 ndb_mgm report incorrect msg after stop NDB node when single user mode
Submitted: 10 Aug 2007 12:21 Modified: 10 Jan 2008 3:34
Reporter: justin he Email Updates:
Status: Patch approved Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: 5.1.20-ndb-6.3.2 bk

[10 Aug 2007 12:21] justin he
Description:
[justin.he@dev3-240 src]$ mgmclient/ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 172.16.70.240:1186
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2, Nodegroup: 0, Master)
id=3    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)

[mysqld(API)]   6 node(s)
id=4    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)
id=5    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)
id=6 (not connected, accepting connect from any host)
id=7 (not connected, accepting connect from any host)
id=8 (not connected, accepting connect from any host)
id=9 (not connected, accepting connect from any host)

ndb_mgm> enter single user mode 4;
Single user mode entered
Access is granted for API node 4 only.
ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2, single user mode, Nodegroup: 0, Master)
id=3    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2, single user mode, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)

[mysqld(API)]   6 node(s)
id=4    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)
id=5    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)
id=6 (not connected, accepting connect from any host)
id=7 (not connected, accepting connect from any host)
id=8 (not connected, accepting connect from any host)
id=9 (not connected, accepting connect from any host)

ndb_mgm> 2 stop;
Shutdown failed.
*  2002: Stop failed
*        Operation not allowed while nodes are starting or stopping.: Permanent error: Application error

ndb_mgm> 3 restart
Shutting down nodes with "-n, no start" option, to subsequently start the nodes.
Node 3: Node shutdown initiated
Node 3: Node shutdown completed, restarting, no start.
Node 3 is being restarted

ndb_mgm> Node 3: Forced node shutdown completed. Occured during startphase 1. Initiated by signal 6. Caused by error 2314:'Data node is not allowed to get added to the cluster while it is in single user mode(Restart error). Temporary error, restart node'.

ndb_mgm> show
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2, single user mode, Nodegroup: 0, Master)
id=3 (not connected, accepting connect from 172.16.70.240)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @172.16.70.240  (mysql-5.1.20 ndb-6.3.2)

[mysqld(API)]   6 node(s)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)
id=6 (not connected, accepting connect from any host)
id=7 (not connected, accepting connect from any host)
id=8 (not connected, accepting connect from any host)
id=9 (not connected, accepting connect from any host)
                               

How to repeat:
1. enter user mode
2. stop a NDB node, err msg isnot correct
3. restart a NDB node, report error
[10 Aug 2007 12:28] Bugs System
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/32352

ChangeSet@1.2562, 2007-08-10 20:12:35+08:00, Justin.He@dev3-240.dev.cn.tlan +1 -0
  Bug#30357, ndb_mgm report incorrect msg after stop/restart NDB node when single user mode
[17 Sep 2007 12:54] Bugs System
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/34343

ChangeSet@1.2552, 2007-09-17 06:54:37+00:00, justin.he@turbo.localdomain +1 -0
  Bug#30357, ndb_mgm report incorrect msg after stop NDB node when single user mode