Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 35.4Mb
PDF (A4) - 35.6Mb
PDF (RPM) - 33.8Mb
EPUB - 8.5Mb
HTML Download (TGZ) - 8.3Mb
HTML Download (Zip) - 8.4Mb
HTML Download (RPM) - 7.2Mb
Eclipse Doc Plugin (TGZ) - 9.2Mb
Eclipse Doc Plugin (Zip) - 11.3Mb
Man Pages (TGZ) - 198.4Kb
Man Pages (Zip) - 302.4Kb
Info (Gzip) - 3.2Mb
Info (Zip) - 3.2Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  /  ...  /  ndb_error_reporter — NDB Error-Reporting Utility

19.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 MySQL Cluster.

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

Table 19.91 This table describes command-line options for the ndb_error_reporter program

Format Description Added or Removed


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

All MySQL 5.7 based releases


Disable scp with remote hosts; used only for testing.

All MySQL 5.7 based releases


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

All MySQL 5.7 based releases


Skip all nodes in the node group having this ID.

All MySQL 5.7 based releases


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:

  • --connection-timeout=timeout

    Command-Line Format--connection-timeout=timeout
    Permitted ValuesTypeinteger

    Wait this many seconds when trying to connect to nodes before timing out.

  • --dry-scp

    Command-Line Format--dry-scp
    Permitted ValuesTypeboolean

    Run ndb_error_reporter without using scp from remote hosts. Used for testing only.

  • --fs

    Command-Line Format--fs
    Permitted ValuesTypeboolean

    Copy the data node file systems to the management host and include them in the archive.

    Because data node file systems can be extremely large, even after being compressed, we ask that you please do not send archives created using this option to Oracle unless you are specifically requested to do so.

  • --skip-nodegroup=nodegroup_id

    Command-Line Format--connection-timeout=timeout
    Permitted ValuesTypeinteger

    Skip all nodes belong to the node group having the supplied node group ID.

User Comments
Sign Up Login You must be logged in to post a comment.