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 all MySQL Cluster programs, see Section 15.4.21, “Options Common to MySQL Cluster Programs”.
Table 15.13. ndb_error_reporter Command Line Options
Format | Description | Introduction | Deprecated | Removed |
---|---|---|---|---|
--fs | Include file system data in error report; can use a large amount of disk space |
Usage:
ndb_error_reporterpath/to/config-file
[username
] [--fs]
This utility is intended for use on a management node host,
and requires the path to the management host configuration
file (config.ini
). Optionally, you can
supply the name of a user that is able to access the cluster's
data nodes via SSH, in order 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_
,
where YYYYMMDDHHMMSS
.tar.bz2YYYYMMDDHHMMSS
is a datetime
string.
If the --fs
is used, then the data node file
systems are also copied to the management host and included in
the archive that is produced by this script. As 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 Sun Microsystems, Inc. unless you
are specifically requested to do so.
Command-Line Format | --fs |
|
Permitted Values | ||
Type | boolean |
|
Default | FALSE |
User Comments
Add your own comment.