[docker-snmp]: Modify log level of snmpd #9734
Merged
Conversation
This file contains 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
critical or debug messages. this is done mainly to suppress the error message 'truncating integer value > 32 bits'. This error message gets printed when the sysUpTime or hrSystemUptime OIDs are queried and these counters exceed the 32 bit value. Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
qiluo-msft
approved these changes
Jan 11, 2022
SuvarnaMeenakshi
added
Request for 201811 Branch 
Request for 201904 Branch 🏂
Request for 201911 Branch
Request for 202006 Branch
Request for 202012 Branch
Request for 202106 Branch
Request for 202111 Branch
qiluo-msft
pushed a commit
that referenced
this pull request
Jan 14, 2022
#### Why I did it resolves #8779 snmpd writes the below error message in syslog : snmp#snmpd[27]: truncating integer value > 32 bits This message is written in syslog when the hrSystemUptime(1.3.6.1.2.1.25.1.1.0 / system uptime) or sysUpTime(1.3.6.1.2.1.1.3 network management portion or snmpd uptime) is queried when either of these counters overflow beyond 32 bit value. This happens the device uptime or snmpd uptime is more than 497 days. #### How I did it Reference: https://access.redhat.com/solutions/367093 and https://linux.die.net/man/1/snmpcmd To avoid seeing this message if the counter grows, the snmpd error log level is changed to display LOG_EMERG, LOG_ALERT, LOG_CRIT, and LOG_DEBUG. Without this change, LOG_ERR and LOG_WARNING would also be logged in syslog. #### How to verify it On a device which is up for more than 497 days, modify supervisord.conf with the change and restart snmp. Query 1.3.6.1.2.1.1.3 and verify that log message is not seen.
judyjoseph
pushed a commit
that referenced
this pull request
Jan 17, 2022
#### Why I did it resolves #8779 snmpd writes the below error message in syslog : snmp#snmpd[27]: truncating integer value > 32 bits This message is written in syslog when the hrSystemUptime(1.3.6.1.2.1.25.1.1.0 / system uptime) or sysUpTime(1.3.6.1.2.1.1.3 network management portion or snmpd uptime) is queried when either of these counters overflow beyond 32 bit value. This happens the device uptime or snmpd uptime is more than 497 days. #### How I did it Reference: https://access.redhat.com/solutions/367093 and https://linux.die.net/man/1/snmpcmd To avoid seeing this message if the counter grows, the snmpd error log level is changed to display LOG_EMERG, LOG_ALERT, LOG_CRIT, and LOG_DEBUG. Without this change, LOG_ERR and LOG_WARNING would also be logged in syslog. #### How to verify it On a device which is up for more than 497 days, modify supervisord.conf with the change and restart snmp. Query 1.3.6.1.2.1.1.3 and verify that log message is not seen.
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.
Signed-off-by: Suvarna Meenakshi sumeenak@microsoft.com
Why I did it
resolves #8779
snmpd writes the below error message in syslog :
snmp#snmpd[27]: truncating integer value > 32 bits
This message is written in syslog when the hrSystemUptime(1.3.6.1.2.1.25.1.1.0 / system uptime) or sysUpTime(1.3.6.1.2.1.1.3 network management portion or snmpd uptime) is queried when either of these counters overflow beyond 32 bit value. This happens the device uptime or snmpd uptime is more than 497 days.
How I did it
Reference: https://access.redhat.com/solutions/367093 and https://linux.die.net/man/1/snmpcmd
To avoid seeing this message if the counter grows, the snmpd error log level is changed to display LOG_EMERG, LOG_ALERT, LOG_CRIT, and LOG_DEBUG.
Without this change, LOG_ERR and LOG_WARNING would also be logged in syslog.
How to verify it
On a device which is up for more than 497 days, modify supervisord.conf with the change and restart snmp.
Query 1.3.6.1.2.1.1.3 and verify that log message is not seen.
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)