Open
Conversation
offset with a negative "-1 second" offset causes a critical status Offsets should be positive integers
Contributor
|
Hi @cedr-x, Here's what I suggest:
What do you think? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
offset with a negative "-1 second" output cause a critical status of the plugin. Offsets should be positive integers
Community contributors
Description
Sometimes, centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=time trigger critical status when the checked host is just a second behind the ref_time
Type of change
How this pull request can be tested ?
Check against an host which have it clock set near 1s behing ntp ref time
The unpatched check is tossed be criticals when it retrives exactly "-1" (second) as offset
This patched check, returning in that case "1" stay with status OK
tested with:
Checklist