ndb_perrorshows information about an NDB error, given its error code. This includes the error message, the type of error, and whether the error is permanent or temporary. This is intended as a drop-in replacement forperror--ndb, which is no longer supported.

Usage

ndb_perror [options]error_code

ndb_perrordoes not need to access a running NDB Cluster, or any nodes (including SQL nodes). To view information about a given NDB error, invoke the program, using the error code as an argument, like this:

shell> ndb_perror 323 NDB error code 323: Invalid nodegroup id, nodegroup already existing: Permanent error: Application error

To display only the error message, invokendb_perrorwith the--silentoption (short form-s), as shown here:

shell> ndb_perror -s 323 Invalid nodegroup id, nodegroup already existing: Permanent error: Application error

Likeperror,ndb_perroraccepts multiple error codes:

shell> ndb_perror 321 1001 NDB error code 321: Invalid nodegroup id: Permanent error: Application error NDB error code 1001: Illegal connect string

Additional program options forndb_perrorare described later in this section.

ndb_perrorreplacesperror--ndb, which is no longer supported by NDB Cluster. To make substitution easier in scripts and other applications that might depend onperrorfor obtaining NDB error information,ndb_perrorsupports its own“dummy”--ndboption, which does nothing.

The following table includes all options that are specific to the NDB Cluster programndb_perror. Additional descriptions follow the table.

Additional Options