Luca Maranzano
2011-11-22 15:45:22 UTC
Luca Maranzano [http://community.zenoss.org/people/liuk] created the discussion
"Upgrade from 3.1 to 3.2.1 and zenprocess misbehaving"
To view the discussion, visit: http://community.zenoss.org/message/62774#62774
--------------------------------------------------------------
After upgrading from 3.1 to 3.2.1 we have to report a strange erratic behaviour of zenprocess.
To monitor some Oracle Databases, we have defined a Process with this regular expression pattern: ^ora_pmon_.*
And now on some apparently random servers, zenprocess is not able to detect that some process are up and running.
If we check with snmpwalk the process is present.
This behaviour is totally erratic, on some device all instances are correctly detected, on few devices instances are seen as DOWN, I cannot figure out a schema about this.
Is this a known issue of 3.2.1? Please note that this configuration has worked flawlessly for months on 2.5.1 and 3.1.0.
Let me know if you need more info.
Thank you.
Regards,
Luca
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62774#62774]
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]
"Upgrade from 3.1 to 3.2.1 and zenprocess misbehaving"
To view the discussion, visit: http://community.zenoss.org/message/62774#62774
--------------------------------------------------------------
After upgrading from 3.1 to 3.2.1 we have to report a strange erratic behaviour of zenprocess.
To monitor some Oracle Databases, we have defined a Process with this regular expression pattern: ^ora_pmon_.*
And now on some apparently random servers, zenprocess is not able to detect that some process are up and running.
If we check with snmpwalk the process is present.
This behaviour is totally erratic, on some device all instances are correctly detected, on few devices instances are seen as DOWN, I cannot figure out a schema about this.
Is this a known issue of 3.2.1? Please note that this configuration has worked flawlessly for months on 2.5.1 and 3.1.0.
Let me know if you need more info.
Thank you.
Regards,
Luca
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62774#62774]
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]