Bug #62233 Data node crash DBTUP (Line: 2035) 0x00000002
Submitted: 23 Aug 2011 7:17 Modified: 25 Aug 2011 6:38
Reporter: mysql cluster Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:7.1.15 OS:Linux (debian 5.0.8 x64)
Assigned to: Assigned Account CPU Architecture:Any

[23 Aug 2011 7:17] mysql cluster 
Description:
In a 2 SQL node and 2 data node environment I have random crashes of data nodes, usually one fails every 24-48 hours, but sometimes both crash at the same time with a complete loss of service, always with the same error:

2011-08-23 07:35:58 [ndbd] ALERT    -- Node 4: Forced node shutdown completed. Caused by error 2341: 'Internal program error (failed ndbrequire)(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.

Time: Tuesday 23 August 2011 - 07:35:57
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: dbtup/DbtupTrigger.cpp
Error object: DBTUP (Line: 2035) 0x00000002
Program: /usr/local//mysql/bin//ndbmtd
Pid: 14760 thr: 5
Version: mysql-5.1.56 ndb-7.1.15
Trace: /data/mysqlcluster//ndb_4_trace.log.4 /data/mysqlcluster//ndb_4_trace.log.4_t1 /data/mysqlcluster/

How to repeat:
Crashes are random, I don't know any way to force the crash.
[23 Aug 2011 7:19] mysql cluster 
trace

Attachment: ndb_4_trace.log.4.zip (application/zip, text), 321.11 KiB.
[23 Aug 2011 7:38] Jonas Oreland 
Hi,

This is a duplicate of Bug#62116
If you compile your self, there is a patch attached to that bug,
and if not, you have to wait for a new 7.1.15a that we are working on producing right now.

/Jonas
[25 Aug 2011 6:38] mysql cluster 
Hi Jonas,

Since updated both cluster data nodes started correctly and are working fine.

Tnak you very much.