Signer - Checking the system logs on Docker
The Docker image for Signer sends its logs to the standard output, which in turn gets registered by Docker as service logs. To check the signer service logs:
docker service logs signer_signer
To follow the log continuously, use the -f flag:
docker service logs signer_signer -f
On the commands shown on this article, the leftmost signer is the name of the stack, while the rightmost part is the name
of the service (in the case above, the signer service). If you deployed your stack with another name, say dropsigner, you
would need to replace the leftmost signer on the commands shown here with the name of your stack (e.g. dropsigner_signer).
You can also check the SQL Server logs:
docker service logs signer_sql
And also the Nginx logs:
docker service logs signer_nginx
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 service log for the code. Replace 62BE3B with the code the user reported and adjust
the period in --since:
docker service logs signer_signer --since 24h 2>&1 | grep -A 40 62BE3B
Send Lacuna support:
- The code and the approximate date and time of the error.
- The log excerpt with the code line and the exception that follows it.
- The Signer version (the
productVersionfield of/api/system/info). - What the user was doing when the error happened (screen, action and, if any, the document ID).
Expected errors, such as a data validation, show their own message and carry no such code.