poller-configuration.xml modified when outages saved from GUI
Description
Every time I save an outage from the GUI, the address range of one of my poller packages is changed. The modified ranges are relevant to my network, but I don't see where they come from. They do not include the addresses of some of the equipment I need polled.
Seth Leger (community account) August 10, 2010 at 4:25 PM
This bug has been marked as a duplicate of ***
Ian Goodacre February 25, 2007 at 9:06 PM
Hi Tarus,
Thanks for the tip - that works for me.
I can confirm that it is necessary to shut down tomcat as well as OpenNMS. Previously I had only shut down OpenNMS and still I got the old configuration comming back when I changed an outage. I have just tested after shutting down both, and the address ranges weren't changed.
Regards, Ian
Ian Goodacre February 25, 2007 at 8:55 PM
I doesn't change the file every time, only when I schedule a polling outage.
Tarus Balog February 22, 2007 at 10:50 AM
Okay, this is a known issue. If you change your poller-configuration.xml file, be sure to restart both opennms and tomcat. Otherwise, tomcat will cache the old poller-configuration file and when it writes out the scheduled outage it will overwrite your changes.
Ian Goodacre February 22, 2007 at 12:56 AM
Actually, my version is 1.2.9-2, but that wasn't on the pick list for version.
Every time I save an outage from the GUI, the address range of one of my
poller packages is changed. The modified ranges are relevant to my network,
but I don't see where they come from. They do not include the addresses of
some of the equipment I need polled.