Pular para o conteúdo principal

Signer - Checking the system logs (Linux)

When installed on Linux, Signer writes its logs to systemd journal, a centralized Linux log management solution. To view the logs, use the utility journalctl.

To check the Signer logs:

journalctl -u lacuna-signer

Use the -f flag to monitor the log continuously (like the tail -f command):

journalctl -u lacuna-signer -f

Use the --since parameter to view only the most recent logs:

journalctl -u lacuna-signer --since "1 min ago"

Error with a code on screen​

When an unexpected error happens, Signer shows this message to the user:

An unexpected error has occurred. Please contact technical support and enter the code 62BE3B.

The code has six hexadecimal characters and is random. Signer generates a new code for each error. At the same moment, it writes to the log an Error level line with the same code, followed by the full exception:

Unhandled exception -- code: 62BE3B

To find the error, search the log for the code. Replace 62BE3B with the code the user reported and adjust the period in --since:

journalctl -u lacuna-signer --since "1 day ago" | grep -A 40 62BE3B

Send Lacuna support:

  1. The code and the approximate date and time of the error.
  2. The log excerpt with the code line and the exception that follows it.
  3. The Signer version (the productVersion field of /api/system/info).
  4. What the user was doing when the error happened (screen, action and, if any, the document ID).
note

Expected errors, such as a data validation, show their own message and carry no such code.

See also​

View as Markdown