On Thursday, 1 October 2009 07:47:04 thorsten.erdmann at daimler.com wrote:
Hi
I have just noticed that devmon stops working if a device it should test is not reachable. We had an UPS test running via devmon an one of the UPS is uninstalled but not deleted in Hobbit/devmon. When I start devmon it does exactly one scan which reported tons of errors in the devmon log and then nothing happens any more. The Hobbit devmon tests of all devices get purple after some time.
One of our UPS's was the last to be moved to a new network, and this caused no problems.
Can you provide more detail: 1)What version of devmon are you running? 2)Is hobbit still testing this device? 3)Was there a conn test for this device? Is it still there? What colour is it currently 4)Can you provide the useful parts of the log?
How can I setup devmon to ignore such errors and not stop working.
Usually devmon should not poll the device if the conn test is red, and even if it does, it should at worst time out for the maximum of (SNMPTIMEOUT * SNMPTRIES) and MAXPOLLTIME. While it is timing out the fork that is polling this device, the other forks should continue polling ....
Regards, Buchan