ioBroker.js-controller
ioBroker.js-controller copied to clipboard
Write meaning of more exit codes in log and improve existing ones
Currently, when an adapter restarts or quits, the numeric error code is written in the log and sometimes a meaning is added. Without looking in the sources, one does not always know what that means. E.g.:
system.adapter.cloud.0 terminated with code 156 ()
Some examples:
Code 0
Current explanation: OK Should be: Planned shutdown or restart
Code 7
Current explanation: Adapter already running Should be: Another process for this instance is running in the background.
Code 156 (-100 in code)
Current explanation: none
Problematic ones (like code 7) should include a link to the documentation with tips how to solve it. Should be: Scheduled restart
How do we want to proceed here?
Anything else we should add for the exit codes or ok now?
@AlCalzone What do you think?
What are we logging now?
aaahhh ok, np I think there is not much changed ... so idea would be to add "exit code specific error infos texts"?