Bug fix: Sensormond crashes on elapsed time limit warning log #434
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.
Changes call to
log_warning
that sensormond daemon uses to do it directly through the object rather than attempting to uselogger
which will crash the daemon as it is not a part of the object.Description
Changes call to
log_warning
that sensormond daemon uses to do it directly through the object rather than attempting to uselogger
which will crash the daemon as it is not a part of the object.Motivation and Context
In its current form, if the elapsed time log warning is ever attempted, the sensormond daemon will hit an error causing it to crash and restart, this will happen in an infinite loop.
How Has This Been Tested?
This change has been tested on Cisco 8201-32fh and 8111-32eh where we can see the sensormond process staying up and the logs being printed into the syslog correctly.
Before change:
After change:
Additional Information (Optional)