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:

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

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

Logs attached.

 

Assignee

Stefan Iliev

Reporter

Alexey Panfilov

Labels

None

Sprint

None

Epic Link

None

Priority

Medium

Engineering Teams

None

Fix versions

Affects versions

Ported to...

None

Story Points / Dev Days

None

Build cut

None

Feature Team

Operational Experience
Configure