Bug #28236 full cluster crash during restart crashed node
Submitted: 4 May 2007 12:02 Modified: 28 Feb 2008 11:23
Reporter: Kris Buytaert (Candidate Quality Contributor) Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:5.1.16 OS:Linux (Centos 4.2)
Assigned to: CPU Architecture:Any
Tags: qc

[4 May 2007 12:02] Kris Buytaert
While trying to recover from Bug #28235, (restarting ndbd on the crashed node)
Both nodes crash

Time: Thursday 3 May 2007 - 16:52:13
Status: Temporary error, restart node
Message: System error, node killed during node restart by other node (Internal e
rror, programming error or missing error message, please report a bug)
Error: 2303
Error data: Node 4 killed this node because GCP stop was detected
Error object: NDBCNTR (Line: 234) 0x0000000e
Program: ndbd
Pid: 22135
Trace: /var/lib/mysql/mysql-cluster//ndb_4_trace.log.3
Version: Version 5.1.16 (beta)


Time: Thursday 3 May 2007 - 17:07:24
Status: Temporary error, restart node
Message: Another node failed during system restart, please investigate error(s) 
on other node(s) (Restart error)
Error: 2308
Error data: Node 4 disconnected
Error object: QMGR (Line: 2648) 0x0000000a
Program: ndbd
Pid: 12184
Trace: /var/lib/mysql/mysql-cluster//ndb_3_trace.log.5
Version: Version 5.1.16 (beta)

Note that ntp wasn't running on these node and altough the timestamps are far a part they were at the same mement.

How to repeat:
Not reproduced yet
[4 May 2007 12:02] Kris Buytaert
Full lgo

Attachment: ndb_error_report_20070504100751.tar.bz2 (application/x-bzip2, text), 150.95 KiB.

[4 May 2007 12:03] Kris Buytaert
main clusterlog

Attachment: ndb_1_cluster.log.gz (application/x-gzip, text), 46.65 KiB.

[28 Jan 2008 11:23] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.1.22, and inform about the results.
[29 Feb 2008 0: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".