Issues
- snmp asset provisioning adapter throws exceptions when unable to reach SNMPNMS-15830
- Snmp timeout exceptions appear in provisiond logNMS-15630
- Spelling correction in DEBUG discovery.log entriesNMS-14757Resolved issue: NMS-14757Rob Ellis
- Password in collectd.log fileNMS-13183Resolved issue: NMS-13183Christian Pape
- Enhance Jaeger OpenTracing Logging with tag for thread nameNMS-12195Resolved issue: NMS-12195Sean Torres
- In Threshd, added some debug statements + slight code refactoringNMS-9025
- Queued daemon seems to ignore loglevelNMS-7510Resolved issue: NMS-7510
- Allow ILR to output durations in millisecondsNMS-5755Resolved issue: NMS-5755Jeff Gehlbach
- Add notification ID to NotificationTask.toString()NMS-5377Resolved issue: NMS-5377Jeff Gehlbach
- output.log receiving printfs starting with "Hibernate:" and containing HQL statementsNMS-4906Resolved issue: NMS-4906Matt Brozowski
- JRobinRrdStrategy: JRobin: Unrecognized graph argument:NMS-4757Resolved issue: NMS-4757Benjamin Reed
- Importer doesn't log to correct log4j categoryNMS-4545Resolved issue: NMS-4545Matt Brozowski
- Log a login/logout/session event when a user logs into the webUINMS-1655
13 of 13
snmp asset provisioning adapter throws exceptions when unable to reach SNMP
Description
Acceptance / Success Criteria
None
Attachments
1
Details
Details
Assignee
Unassigned
UnassignedReporter
Marcel Fuhrmann
Marcel Fuhrmann
HB Grooming Date
Aug 01, 2023
HB Backlog Status
Backlog
Components
Affects versions
Priority
MediumPagerDuty
PagerDuty
Created July 6, 2023 at 10:48 AM
Updated August 1, 2023 at 3:16 PM
Activity
Show:
The node / interface 149.97.181.73. does not have SNMP service. The node had in the past SNMP, that is why we can see in the screenshot an sysObjectID etc. . But it was turned off.
Now it looks like the snmp asset provisioning adapter does not like this fact. I don’t know why it still thinks that it has to check the node. Maybe because it has the sysObjectID? I found a lot of exceptions about not reaching the IP address.
This might be special scenario, but this does not matter IMO. We should catch this state and print out useful log entries.