Luca Maranzano
2011-11-28 16:01:37 UTC
Luca Maranzano [http://community.zenoss.org/people/liuk] created the discussion
"Lots of "Unable to read processes on device xxxx; Timeout on device" after upgrading from 2.5.1 to 3.2.1"
To view the discussion, visit: http://community.zenoss.org/message/62863#62863
--------------------------------------------------------------
After upgrading from Zenoss Core 2.5.1 to 3.2.1 on Ubuntu 8.04 64 bit we are experiencing several of these errors:
*Unable to read processes on device xxxxxx.mydomain.it; Timeout on device*
The monitored devices are tipically Linux or Solaris server monitored from Zenoss via SNMP.
Before the upgrade this issue was not present at all, so something has surely changed on the Zenoss side.
If I try to manually run from the zenoss server a command like this when the error occurs:
snmpwalk -v1 -c MYCOMMUNITY x.x.x.x system
I always get an almost instant response from the remote, so it is hard to say that the problem is on the remote side.
How can I trace down / debug this issue? I've hundreds of devices monitored and I'm getting crazy :-)
TIA.
Regards,
Luca
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62863#62863]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Lots of "Unable to read processes on device xxxx; Timeout on device" after upgrading from 2.5.1 to 3.2.1"
To view the discussion, visit: http://community.zenoss.org/message/62863#62863
--------------------------------------------------------------
After upgrading from Zenoss Core 2.5.1 to 3.2.1 on Ubuntu 8.04 64 bit we are experiencing several of these errors:
*Unable to read processes on device xxxxxx.mydomain.it; Timeout on device*
The monitored devices are tipically Linux or Solaris server monitored from Zenoss via SNMP.
Before the upgrade this issue was not present at all, so something has surely changed on the Zenoss side.
If I try to manually run from the zenoss server a command like this when the error occurs:
snmpwalk -v1 -c MYCOMMUNITY x.x.x.x system
I always get an almost instant response from the remote, so it is hard to say that the problem is on the remote side.
How can I trace down / debug this issue? I've hundreds of devices monitored and I'm getting crazy :-)
TIA.
Regards,
Luca
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62863#62863]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]