MySQL Bugs: #63697: NDB Node shuts down with "failed ndbrequire"

Bug #63697	NDB Node shuts down with "failed ndbrequire"
Submitted:	9 Dec 2011 15:32	Modified:	29 Feb 2012 18:09
Reporter:	Mike van Lammeren	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1.47 ndb-7.1.8	OS:	Linux (Ubuntu 10.04)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	failed ndbrequire, node shut down

Description:
One ndb node shut down, then 14 minutes later, the other shut down. Prior to this, the cluster had been up for around 18 months. Messages from error logs:

Time: Thursday 8 December 2011 - 16:33:47
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: lgman.cpp
Error object: LGMAN (Line: 1444) 0x00000002
Program: /usr/local/mysql//mysql/bin//ndbmtd
Pid: 1856 thr: 1
Version: mysql-5.1.47 ndb-7.1.8
Trace: /data/mysqlcluster//ndb_4_trace.log.4 /data/mysqlcluster//ndb_4_trace.log.4_t1 /data/mysqlcluster//ndb_4_

Time: Thursday 8 December 2011 - 16:47:12
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a$
Error: 2341
Error data: pgman.cpp
Error object: PGMAN (Line: 537) 0x00000002
Program: /usr/local/mysql//mysql/bin//ndbmtd
Pid: 1964 thr: 2
Version: mysql-5.1.47 ndb-7.1.8
Trace: /data/mysqlcluster//ndb_3_trace.log.6 /data/mysqlcluster//ndb_3_trace.log.6_t1 /data/mysqlcluster//ndb_3_t

How to repeat:
I have no idea how to repeat this bug. This is the first time I've seen MySQL Cluster go down.

The ndb_error file is 2.6 MB, which is too large for the website limit of 500 K, and although there are instructions about uploading the ndb_error file to ftp.mysql.com, that appears to be no longer a valid address.

the lgman problem is fixed...100% sure...(don't remember which version though)
the pgman problem...i think is fixed, not 100% sure

upgrading to latest 7.1 will atleast fix one of the two...probably both

setting status to need feedback

/Jonas

Thank you Jonas, for your reply. We will most likely upgrade to the latest 7.1.

I will keep the ndb_error_report file in case anyone ever wants to see it.

Thanks again!

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".