Fix: ConnectionRefusedError on startup when no broker is running #247
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Notus-scanner exits now with a log message instead of an exception
SC-650
Why:
In case no MQTT broker was running, the notus-scanner would end with a
ConnectionRefuseError
as a exception. Now a log message is printed insteadHow:
Start notus-scanner without having a MQTT broker running
Checklist: