Bug #31280 error 2308 Node 2: Forced node shutdown completed. Occured during startphase 5.
Submitted: 28 Sep 2007 14:40 Modified: 14 Apr 2008 14:58
Reporter: joe smith Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.20 beta OS:Linux
Assigned to: CPU Architecture:Any
Tags: and restarting, ndbd node, shutting down

[28 Sep 2007 14:40] joe smith
Description:
I am running mysql 5.1.20.

I had two ndbd nodes, 2 sql nodes and 1 mgmd node.  I started mgmd
node and 2 ndbd nodes.  But sql nodes not yet been started.  I then
restarted ndbd node 1 (which was a master ndbd node).  Note, I haven't
changed any config.ini files.  Just restarting the master ndbd node,
which is node 1.  This causes ndbd node 2 to become master.  When the
ndbd node 1 machine restarted (ndbd starts up during linux bootup), I
get this error message mgm console:

ndb_mgm> Node 2: Forced node shutdown completed. Occured during
startphase 5. Caused by error 2308: 'Another node failed during system
restart, please investigate error(s) on other node(s)(Restart error).
Temporary error, restart node'.

I didn't shutdown the cluster, i.e, shutdown ndbd node 2, mgmd node.

How to repeat:
Start the mgmd.  
Start ndbd node 1.
Start ndbd node 2.

Shutdown ndbd node 1.
Restart ndbd node 1.
[5 Oct 2007 9:56] k ck
i also have this problem.
My OS is redhat enterprise 4.
Who can help to solve this problem?
kingofck@yahoo.com.hk
[31 Jan 2008 5:13] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.1.22. In case of the same problem, please, upload all the logs and trace files.
[1 Mar 2008 0:01] Bugs System
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".
[14 Mar 2008 14:58] Susanne Ebrecht
Joe,

we still need the feedback if all would be fine after you update to newer version and do what Valeriy pleaded you here. Our newest version is 5.1.23.
[14 Apr 2008 23:00] Bugs System
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".