Sometimes a node does not raise a corresponding error about the incorrect node configuration during its startup before node process is ended.

Description

It seems that when we start a node with an incorrect configuration, sometimes the node process ends before the corresponding error is printed to console and written to the log.

Please see the screenshot below which shows three attempts to start the node with wrong value of the "custom" field in the node configuration:

Attempt 1:
Expected result - The node raises error a detailed error about the incorrect node configuration:

1 2 [ERROR] 12:21:10+0300 [main] node.SharedNodeCmdLineOptions. - There were error(s) while attempting to load the node configuration: [ERROR] 12:21:10+0300 [main] node.SharedNodeCmdLineOptions. - /home/alexey.panfilov/corda/workdir/environments/DW3/NFTEPDW3Party011/node.conf: 32: List should have ended with ] or had a comma, instead had token: ':' (if you want ':' to be part of a string value, then double-quote it)

Attempt 2:
Unexpected result - The node raises only error about unsuccessful load of node configuration:

1 [ERROR] 12:21:18+0300 [main] node.SharedNodeCmdLineOptions. - There were error(s) while attempting to load the node configuration:

Attempt 3 - DEBUG logging level:
Unexpected result - There are no errors about the incorrect node configuration.

Logs attached.

 

Status

Assignee

Stefan Iliev

Reporter

Alexey Panfilov

Labels

None

Priority

Medium

Fix versions

Ported to...

None

Feature Team

Operational Experience

Severity

Medium

Affects versions

Corda 4.3 RC01
Configure