Cacti: Cacti 1.2.16: Spine poller "INFO: SNMP Device timeout" in debug in Medium log level

[iskandarbasman]

Describe the bug

Enabling medium level logs indicates excessive "INFO: SNMP Device timeout" logs.
Suspect the logs to be false positives.
Below screenshot shows that even localhost is generate these timeout logs to rule out network issue.
Graphing is normal.

To Reproduce

1. Enabled logging level in cacti to medium.
2. Go to cacti log and filter for keyword 'timeout'
3. Many "INFO: SNMP Device timeout" will be generated.

Expected behavior

Not expecting to see all these timeout logs especially for localhost polling.
Suspect these logs to be false positives.

Screenshots

As shown above.

[netniV]

That is not likely a bug but the reporting of something that is actually happening.

[iskandarbasman]

How should I verify this ?
Why does it only appear the MEDIUM log levels and not LOW ?
Graphing looks okay from what I can see.

That is not likely a bug but the reporting of something that is actually happening.

[bmfmancini]

It's because the medium reporting is more verbose

But also those are not errors they are informational stating the timeout
setting for localhost it doesn't actually say a timeout has occurred

On Sun., Feb. 21, 2021, 20:06 iskandarbasman, [e-mail]
wrote:

How should I verify this ?
Why does it only appear the MEDIUM log levels and not LOW ?
Graphing looks okay from what I can see.

That is not likely a bug but the reporting of something that is actually
happening.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Cacti/cacti/issues/4137#issuecomment-782974446, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGEXTEOKI3UC3OKODEOVITTAGU3FANCNFSM4X3O2PRQ
.

[TheWitness]

I've got an update coming.

[TheWitness]

Well, we like to keep logging at low unless you are doing diagnostics. Since this is really not a bug. I'm going to close this one. When I first commented, I did not note that this was for successive polling cycles.

[iskandarbasman]

How can I tell whether this these snmp timeouts at the MEDIUM level is valid.
How is this different from the snmp timeout at the LOW logging level ?

Well, we like to keep logging at low unless you are doing diagnostics. Since this is really not a bug. I'm going to close this one. When I first commented, I did not note that this was for successive polling cycles.

[bmfmancini]

They are not timeouts

They are simply telling you what the timeout is set to

On Mon., Feb. 22, 2021, 19:27 iskandarbasman, [e-mail]
wrote:

How can I tell whether this these snmp timeouts at the MEDIUM level is
valid.
How is this different from the snmp timeout at the LOW logging level ?

Well, we like to keep logging at low unless you are doing diagnostics.
Since this is really not a bug. I'm going to close this one. When I first
commented, I did not note that this was for successive polling cycles.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Cacti/cacti/issues/4137#issuecomment-783777501, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGEXTCTH3EUG7WD44GMAH3TALY6XANCNFSM4X3O2PRQ
.

[iskandarbasman]

Argghh... So that means. DOH!
So that means I need to filter these logs when troubleshooting. I SEE...

They are not timeouts They are simply telling you what the timeout is set to
…
On Mon., Feb. 22, 2021, 19:27 iskandarbasman, @.*> wrote: How can I tell whether this these snmp timeouts at the MEDIUM level is valid. How is this different from the snmp timeout at the LOW logging level ? Well, we like to keep logging at low unless you are doing diagnostics. Since this is really not a bug. I'm going to close this one. When I first commented, I did not note that this was for successive polling cycles. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4137 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGEXTCTH3EUG7WD44GMAH3TALY6XANCNFSM4X3O2PRQ .