Bug #58994 problem with mysql cluster data nodes(not starting)
Submitted: 17 Dec 2010 10:36 Modified: 20 Jan 2011 15:36
Reporter: abhay singh Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version: OS:Linux (Debian lenny)
Assigned to: CPU Architecture:Any
Tags: bugs.mysql, cluster, MySQL, MySQL Cluster, mysql_cluster

[17 Dec 2010 10:36] abhay singh
Description:
I have mysql cluster setup with 2 hosts + 1 load balancer.
Data nodes on one of the host is not starting.
I tried to start it again and again but it starts for sometime then shuts down automatically. This data node was active previously and was working fine.

Data nodes on other hosts works fine.We are already live in production. 
How this issue can be resolved ?

Log show following error:

Time: Thursday 16 December 2010 - 13:00:33
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/DbtupRoutines.cpp
Error object: DBTUP (Line: 728) 0x00000002
Program: mysqlc/bin/ndbd
Pid: 2322
Version: mysql-5.1.51 ndb-7.1.9
Trace: ./ndb_2_trace.log.8
***EOM***

How to repeat:
Make 2 clusters on 2 different hosts with data nodes on each of them.

Start management first on each.
Then data nodes on each.
data node on 1 host shut down automatically.
[17 Dec 2010 10:40] abhay singh
trace log file when data nodes get shut down

Attachment: trace.bug.zip (application/zip, text), 52.28 KiB.

[17 Dec 2010 13:21] abhay singh
Added tags
[20 Dec 2010 14:16] Jonas Oreland
Hi,

Can you
1) upload full logs using ndb_error_reporter ?
2) Provide table definition of table with ndb-internal id = 96
   (this can be found using ndb_show_tables)

/Jonas
[21 Jan 2011 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".