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:
Expected result - The node raises error a detailed error about the incorrect node configuration:
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.