Bug #44082 ndb_error_reporter does not include cluster log when LogDestination is used.
Submitted: 3 Apr 2009 18:39 Modified: 23 Sep 2013 6:46
Reporter: Matthew Montgomery Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: mysql-5.1-telco-6.3.20

[3 Apr 2009 18:39] Matthew Montgomery 
Description:
The ndb_error_reporter program can miss collecting logs from some cluster nodes when the LogDestination option is used.

This results in having to make a second request for the missing logs. 

How to repeat:
Set LogDestination=FILE:filename=my-cluster.log  in config.ini and run ndb_error_reporter. 

Suggested fix:
Perhaps ndb_error_reporter could use 'ndb_config' to locate the logs that it may be missing.
[3 Apr 2009 18:40] MySQL Verification Team 
possibly related to Bug #43026
[23 Sep 2013 13:22] Jon Stephens 
Fixed by BUG#57417.
[23 Sep 2013 14:10] Jon Stephens 
Documented fix in the NDB 6.3.52 changelog as follows:

      A number of fixes for ndb_error_reporter have been backported 
      from MySQL Cluster NDB 7.0 and later to this NDB 6.3 release, 
      listed here:
      
      Bug #11764570, Bug #57417: If 'LogDestination=FILE' is included 
      without a file name, use 'ndb_*nodeid*_cluster.log' as the default.
      Bug #16765651: Add * to scp command to include all log files
      Bug #16602002: Add the --connection-timeout, --skip-nodegroup and 
      --dry-scp options. Note: Since NDB 6.3 does not support the  
      Nodegroup configuration parameter, node groups cannot be queried 
      using ndb_config; use 'ndb_mgm -e show' to get the node groups
      for the --skip-nodegroup option.
      Bug #11756666, Bug #48606: Add missing --help option.

Closed.