PDF (A4) - 43.4Mb
Man Pages (TGZ) - 297.2Kb
Man Pages (Zip) - 402.4Kb
Info (Gzip) - 4.3Mb
Info (Zip) - 4.3Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
Security in MySQL
Starting and Stopping MySQL
MySQL and Linux/Unix
MySQL and Windows
MySQL and macOS
MySQL and Solaris
Building MySQL from Source
MySQL Restrictions and Limitations
MySQL Partitioning
MySQL Tutorial
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL NDB Cluster 8.0
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.
Options that can be used withndb_error_reporter are shown in the following table. Additional descriptions follow the table.
Table 25.34 Command-line options used with the program ndb_error_reporter
| Format | Description | Added, Deprecated, or Removed |
|---|---|---|
| Number of seconds to wait when connecting to nodes before timing out | (Supported in all NDB releases based on MySQL 8.0) | |
| Disable scp with remote hosts; used in testing only | (Supported in all NDB releases based on MySQL 8.0) | |
| Include file system data in error report; can use a large amount of disk space | (Supported in all NDB releases based on MySQL 8.0) | |
| Display help text and exit | (Supported in all NDB releases based on MySQL 8.0) | |
| Skip all nodes in the node group having this ID | (Supported in all NDB releases based on MySQL 8.0) |
Usage
ndb_error_reporterpath/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 namedconfig.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 namedndb_error_report_, whereYYYYMMDDhhmmss.tar.bz2YYYYMMDDhhmmss is a datetime string.
ndb_error_reporter also accepts the options listed here:
Command-Line Format --connection-timeout=#Type Integer Default Value 0Wait this many seconds when trying to connect to nodes before timing out.
Command-Line Format --dry-scpRunndb_error_reporter without using scp from remote hosts. Used for testing only.
Command-Line Format --helpDisplay help text and exit.
Command-Line Format --fsCopy 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 donot send archives created using this option to Oracle unless you are specifically requested to do so.
Command-Line Format --connection-timeout=#Type Integer Default Value 0Skip all nodes belong to the node group having the supplied node group ID.
PDF (A4) - 43.4Mb
Man Pages (TGZ) - 297.2Kb
Man Pages (Zip) - 402.4Kb
Info (Gzip) - 4.3Mb
Info (Zip) - 4.3Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
Security in MySQL
Starting and Stopping MySQL
MySQL and Linux/Unix
MySQL and Windows
MySQL and macOS
MySQL and Solaris
Building MySQL from Source
MySQL Restrictions and Limitations
MySQL Partitioning
MySQL Tutorial
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL NDB Cluster 8.0