Bug #42962 | Failed system restart due to dbdict | ||
---|---|---|---|
Submitted: | 18 Feb 2009 9:47 | Modified: | 11 Aug 2009 8:14 |
Reporter: | Johan Andersson | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Solaris |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | dbdict, system restart |
[18 Feb 2009 9:47]
Johan Andersson
[18 Feb 2009 9:48]
Johan Andersson
trace file from crash in dbdict
Attachment: ndb_2_trace.log.10.gz (application/x-gzip, text), 57.05 KiB.
[20 Feb 2009 10:07]
Jonas Oreland
maybe related to bug#40089
[6 Mar 2009 8:47]
Henrik Ingo
Johan: Was this also resolved by doing --initial restart, or did just a new normal restart work?
[6 Mar 2009 8:58]
Henrik Ingo
Oh, and another question: Was there anything special that happened before this, ie cluster was just cleanly restarted to reload config.ini, or was there a problem why it was restarted?
[6 Mar 2009 9:35]
Johan Andersson
IRC, a initial system restart was required :(
[24 Mar 2009 16:28]
Chris Owen
It appears I have ran into this bug as well after my data node crashed. I am unable to recover the node even with a initial start. Time: Tuesday 24 March 2009 - 15:44:37 Status: Temporary error, restart node Message: Internal program error (failed ndbrequire) (Internal error, programming Error: 2341 Error data: dbdict/Dbdict.cpp Error object: DBDICT (Line: 3171) 0x0000000e Program: /opt/mysql/mysql-cluster/bin/ndbd Pid: 5442 Trace: /opt/mysql/mysql-cluster/data/ndb_2_trace.log.1 Version: mysql-5.1.30 ndb-6.3.20-GA ***EOM***
[24 Mar 2009 16:29]
Chris Owen
here is the error bundle
Attachment: ndb_error_report_20090324155758.tar.bz2 (, text), 281.34 KiB.
[11 Aug 2009 8:14]
Jonas Oreland
johan's bug is a duplicate of bug#46552 chris: yours is something else, please open a new bug, and include schema closing this as duplicate