Unresponsive services do not generate nodeLostService messages
Description
Environment
Operating System: All
Platform: All
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Fixed
Details
Assignee
OpenNMS Bug Mailing ListOpenNMS Bug Mailing ListReporter
Tarus BalogTarus BalogComponents
Fix versions
Affects versions
Priority
Major
Details
Details
Assignee

Reporter

Components
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Created March 4, 2005 at 1:25 PM
Updated January 27, 2017 at 4:31 PM
Resolved February 20, 2006 at 11:19 AM
We had a server get very busy last night (no pun intended) and the SMTP service would not send a HELO
within the timeout. The logs show the service as unresponsive:
2005-03-04 03:25:34,569 DEBUG [PollerScheduler-30 Pool-fiber1] PollableServiceConfig: Polling
172.20.0.177:SMTP using pkg example1
2005-03-04 03:25:34,569 DEBUG [PollerScheduler-30 Pool-fiber1] SmtpMonitor: poll: address =
172.20.0.177, port = 25, timeout = 3000, retry = 1
2005-03-04 03:25:34,587 DEBUG [PollerScheduler-30 Pool-fiber1] SmtpMonitor: SmtpMonitor:
connected to host: /172.20.0.177 on port: 25
2005-03-04 03:25:34,697 DEBUG [OpenNMS.Poller.DefaultPollContext]
EventIpcManagerDefaultImpl$ListenerThread: run: calling onEvent on
OpenNMS.Poller.DefaultPollContext for event uei.opennms.org/generic/traps/EnterpriseDefault
2005-03-04 03:25:37,588 DEBUG [PollerScheduler-30 Pool-fiber1] SmtpMonitor: SmtpMonitor: did not
connect to host within timeout: 3000 attempt: 0
2005-03-04 03:25:37,607 DEBUG [PollerScheduler-30 Pool-fiber1] SmtpMonitor: SmtpMonitor:
connected to host: /172.20.0.177 on port: 25
2005-03-04 03:25:40,607 DEBUG [PollerScheduler-30 Pool-fiber1] SmtpMonitor: SmtpMonitor: did not
connect to host within timeout: 3000 attempt: 1
2005-03-04 03:25:40,608 DEBUG [PollerScheduler-30 Pool-fiber1] PollableServiceConfig: Finish
polling 9:172.20.0.177:SMTP using pkg example1 result =Unresponsive
2005-03-04 03:25:40,608 DEBUG [PollerScheduler-30 Pool-fiber1] PollableNode$Lock: Releasing lock
for 9
This should have generated a nodeLostService event.
Note: The IP addresses have been changed to protect the innocent.