Skip to main content

What does the value of the "errorCode" field mean?

This article will answer the question: "What does the value of the errorCode field mean?". This article will also help you identify the problem in more detail.

Problem​

Errors in task execution may occur in every system. When working with Mercury DB 3.0 (HgDB) system services, data after correct execution is sent in the fields:

  • errorCode - error code.
  • errorMessage - error content, description / error description.

If an error in service execution occurred, both values ​​of these fields will not be empty (they will not have the value null). Each error is recorded in the server event log, system node! Often the error description may seem insufficient, so you should look at the value of the code field (errorCode).

Solution​

The errorCode field contains data that will allow us to delve into the problem. This data is written in the following format:

<error_acronym>#[node_name.]<error_id>

e.g. error code with the value: M0001#node3.4b9a3e59-7a9e-4852-8160-c8016a26720e tells us that:

  • error_acronym is M0001
  • node_name is node3 (optional value and occurs only in the case of a clustered, multi-node system configuration)
  • error_id is 4b9a3e59-7a9e-4852-8160-c8016a26720e

Steps to diagnose the problem:

  1. Search for the error acronym in the documentation, e.g. on this site - based on it you can learn about the most common problems related to the causes of this error.
  2. If you have the name of the node, log in (ssh console) to the server on which it is running, if you do not have the name of the node, it means that the server is installed on only one machine - log in to it (ssh console).
  3. Search the event log for a record with the value of the error identifier.
tip

The log is a file called mercury-ws-app.log, which is located (unless configured otherwise) in $MRC_HOME/logs, where the environment variable $MRC_HOME is the directory where the product was installed - an example file location: /opt/mercury-3.0/logs/mercury-ws-app.log.

  1. If you do not have log rotation enabled, this event should be logged in the file /opt/mercury-3.0/logs/mercury-ws-app.log
  2. If you have log rotation enabled, first find out in which file the entry is located. Using the command line, issue the command (e.g. for Linux):
cd /opt/mercury-3.0/logs
grep 4b9a3e59-7a9e-4852-8160-c8016a26720e *

Command output:

Command output

In the case presented above, the name of the file in which the entry occurs is shown in purple. Let's proceed to its review.

  1. In the event log file in which the error entry occurs, search for the error identifier value (for example 4b9a3e59-7a9e-4852-8160-c8016a26720e). To do this, issue the command (e.g. for Linux):
less /opt/mercury-3.0/logs/mercury-ws-app.log

press the / key and enter the identifier value: Command output

after the search for the error entry is complete, you will receive more detailed event data:

Command output Command output

In the presented case, we can see that the cause of the error is an incorrectly constructed query to the Lucene index:

Command output

If you already know everything about the event, you can prevent such situations. If you have any doubts, contact the system administrator.