Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Professional Edition
-
None
Description
When a poller performs the ping and the snmp ping at the start of a poll, it will assume the device is UP if the results are ok.
But if the device stops responding after that point, then this happens:
I had a chat on IRC about this:
<Gunni> adama: why does this happen?
<Gunni> can your poller not notice the request timed out, vs the value being set to ''?
<landy> that happen when device down after check their status, mean ping and snmp ping return ok, but after stop responding
<landy> try increase snmp timeout
<Gunni> yeah i expected that landy, but can't the script notice that and ... abandon the poll or some instead of clearing all fields?
<landy> check status before each module - derp idea
Attachments
Activity
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: In Review [ 10101 ] | New: In Progress [ 3 ] |
Comment | [ not relevant ] |
Comment |
[ Please make and attach additional information about the device: * full snmp dump from device: {noformat} snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk {noformat} _If device not support SNMP version 2c, replace -v2c with -v1._ * If you have problems with discovery or poller processes, please do and attach these debugs: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files {color:#505F79}_Note, this comment is added automatically._{color} ] |
Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |
Not sure if it's help in all cases, but if all params resets in system module (sysDescr, etc) next polls will stopped.
Fixed in r11100.