content_image/709073.jpg content_image/709072.jpg content_image/709066.jpg
<img src='content_image/709073.jpg'>

Enable verbose messages. 

## • --version 

<img src='content_image/709072.jpg'>

Display version information and exit. 

## 23.4.16 ndb_perror — Obtain NDB Error Message Information 

ndb_perror  shows 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 for perror --ndb , which is no longer supported. 

## Usage 

ndb_perror [ options ] error_code 

ndb_perror  does 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, invoke ndb_perror  with the --silent  option (short form -s ), as shown here: 

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

Like perror , ndb_perror  accepts 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 for ndb_perror  are described later in this section. 

ndb_perror  replaces perror --ndb , which is no longer supported by NDB Cluster. To make substitution easier in scripts and other applications that might depend on perror  for obtaining NDB error information, ndb_perror  supports its own “dummy” --ndb  option, which does nothing. 

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

<img src='content_image/709066.jpg'>

