MySQL 5.7 Reference Manual Including MySQL NDB Cluster 7.5 and NDB Cluster 7.6

20.4.13 ndb_error_reporter — NDB Error-Reporting Utility

ndb_error_reporter creates an archive from data node and management node log files that can be used to help diagnose bugs or other problems with a cluster. It is highly recommended that you make use of this utility when filing reports of bugs in NDB Cluster.

The following table includes command options specific to the NDB Cluster program ndb_error_reporter. Additional descriptions follow the table. For options common to most NDB Cluster programs (including ndb_error_reporter), see Section 20.4.32, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.

Table 20.32 Command-line options for the ndb_error_reporter program

Format Description Added, Deprecated, or Removed

--connection-timeout=timeout

Number of seconds to wait when connecting to nodes before timing out

(Supported in all MySQL 5.7 based releases)

--dry-scp

Disable scp with remote hosts; used only for testing

(Supported in all MySQL 5.7 based releases)

--fs

Include file system data in error report; can use a large amount of disk space

(Supported in all MySQL 5.7 based releases)

--skip-nodegroup=nodegroup_id

Skip all nodes in the node group having this ID

(Supported in all MySQL 5.7 based releases)


Usage

ndb_error_reporter path/to/config-file [username] [options]

This utility is intended for use on a management node host, and requires the path to the management host configuration file (usually named config.ini). Optionally, you can supply the name of a user that is able to access the cluster's data nodes using SSH, to copy the data node log files. ndb_error_reporter then includes all of these files in archive that is created in the same directory in which it is run. The archive is named ndb_error_report_YYYYMMDDhhmmss.tar.bz2, where YYYYMMDDhhmmss is a datetime string.

ndb_error_reporter also accepts the options listed here: