Poller not running

Description

RH9 and Blackdown-1.4.2-01
Caps and discovery are ok, but pollers are not doing anything. Checked the uncat
logs and confirmed with tcpdump.

I moved all the changes I saw in new configs into my setup.

nextOutageId="SELECT nextval('outageNxtId')" in poller-configuration.xml
and
delete-propagation-enabled = "true" in capsd-configuration.xml

Didn't see any mention of these in the CHANGELOG, or in PollerNotes.txt.
Anywhere else I should be looking?

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Ted Kaczmarek January 19, 2005 at 6:15 PM

Looks good again

Former user January 19, 2005 at 12:07 PM

Does this mean the poller is now polling? I just added some better logging so
it is easier to tell what the poller is doing? I am going to Resolve this and
you can open a new bug if the poller is now working. If the poller is not
working then reopen this bug.

Thanks alot for you testing Ted,
Matt

Ted Kaczmarek January 17, 2005 at 5:52 PM

Should I open new one, or you want snmp details in here. Says SNMP not polled in
browser, but snmp stats are being collected.
ipinterface table
issnmpprimary = P
ismanaged = M
snmpinterface entries look fine as well

if you want a new one, just close this and I will open a new one.

Ted Kaczmarek January 17, 2005 at 5:43 PM

With today checkout, and after fixing local clock and dropping test db pollers
working. See a quirk with snmp on a node still, but need to confirm configs.

Ted Kaczmarek January 14, 2005 at 9:34 PM

CVS from today behaving the same, did a fresh build right after the
"BUILD COMPLETE - build.85" notification.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created January 8, 2005 at 7:46 PM
Updated November 5, 2010 at 2:02 PM
Resolved September 9, 2010 at 1:24 PM