Troubleshooting with NuoDB Command

This section documents the use of NuoDB Command (nuocmd) to retrieve diagnostic information and how to generate a support package file. When a NuoDB process terminates unexpectedly, the core file gets written to a core subdirectory in the NuoDB log directory. To generate a core file, see get diagnose-info and get core-file. Please send all the core files to NuoDB Support for analysis. For assistance, contact NuoDB Support.

Collecting Diagnostics

Using the NuoDB Command (nuocmd) command-line interface, the following commands are used to collect information:

For more information on NuoDB Command and other command line tools, see Command Line Tools.

To enable the auto-completion and verify the commands before the execution, type bash in the terminal command window and press the ⏎ or Enter key.

get diagnose-info

The nuocmd get diagnose-info collects admin logs, admin configuration, system binaries, and cores into a single support package (.zip) file.

Example
nuocmd get diagnose-info --output-dir /tmp/nuodiag --include-cores

get server-logs

The nuocmd get server-logs creates a zip file containing the Admin Service log files in the specified location.

Example
nuocmd get server-logs --output /tmp

get log-messages

The nuocmd get log-messages streams log messages for the specified process, database, or domain.

Example
nuocmd get log-messages --log-options msgs
The --log-options parameter is required. For a complete list of log parameters, see Description of Logging Categories.

get core-file

The nuocmd get core-file downloads the core file for a running database process.

Example
nuocmd get core-file --start-id 1 --output-dir /tmp/
To get the value for the --start-id parameter, run the nuocmd show domain command and then note the start ID value displayed for the SM or TE process for which you want to generate a core file. If this parameter is not specified, permission to write to the directory where you executed the command is required.

get database-connectivity

The nuocmd get database-connectivity provides connectivity information for the specified database in JSON format.

Example
nuocmd get database-connectivity --db-name test
{
  "0": {
    "1": {
      "lastAckDeltaInMilliSeconds": 746,
      "lastMsgDeltaInMilliSeconds": 755
    },
    "2": {
      "lastAckDeltaInMilliSeconds": 460,
      "lastMsgDeltaInMilliSeconds": 755
    },
    "3": {
      "lastAckDeltaInMilliSeconds": 860,
      "lastMsgDeltaInMilliSeconds": 755
    }
  },
  "1": {
    "0": {
    "lastAckDeltaInMilliSeconds": 802,
    "lastMsgDeltaInMilliSeconds": 794
    },
    "2": {
      "lastAckDeltaInMilliSeconds": 508,
      "lastMsgDeltaInMilliSeconds": 794
    },
    "3": {
      "lastAckDeltaInMilliSeconds": 907,
      "lastMsgDeltaInMilliSeconds": 794
    }
  },
...

show database-connectivity

The nuocmd show database-connectivity displays a connectivity graph of the specified database.

Example
nuocmd show database-connectivity --db-name test --with-node-ids
     1    2    3    4
1             27s
2             27s
3    ?    ?    ?    ?
4             32s

Legend:
X: node at this row does not consider node at this column a peer
?: node at this row could not be queried for connectivity information
!: node at this row does not have expected metadata for node at this column
[0-9]+[hms]: time since node at this row last heard from node at this column