Bug #69072 | Internal program error (failed ndbrequire) error:2341 | ||
---|---|---|---|
Submitted: | 25 Apr 2013 18:01 | Modified: | 2 Jun 2013 6:29 |
Reporter: | Ben Im | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 7.3.1 | OS: | Linux (ubuntu 12.0.4) |
Assigned to: | CPU Architecture: | Any |
[25 Apr 2013 18:01]
Ben Im
[30 Apr 2013 10:03]
Gustaf Thorslund
Hi Ben, Could you please attach the output from ndb_error_reporter without the --fs option? See: http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-programs-ndb-error-reporter.html It is often useful to start looking at the cluster log and also look at the other node in the same node group as the failing node. Then there are trace/error files too included by ndb_error_reporter. Since they report will be compressed it will minimise the size of file to attach. /Gustaf
[30 Apr 2013 15:54]
Ben Im
FTP'ed ndb_error_report_20130430084844.tar.bz2 in support/incoming directory. Let me know how it looks.
[2 May 2013 6:29]
Gustaf Thorslund
Hi Ben, I'm sorry to say, but it looks kind of empty. This is what I see on the server: ndb_error_report_20130430084844.tar.bz2 1 KB 2013-04-30 15:51:00 Downloading and looking inside I only see: $ tar tjf ndb_error_report_20130430084844.tar.bz2 ndb_error_report_20130430084844/ Did you get any errors when running ndb_error_reporter? Can you ssh into the different hosts from the data nodes from the management node? Does the user you invoke ndb_error_reporter with have read access to the logs? /Gustaf
[3 Jun 2013 1: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".