-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 19.0.0, 19.0.1, 19.1.0, 20.0.0
-
Fix Version/s: 20.1.0, Meridian-2017.1.0
-
Component/s: Provisioning / Discovery / Importer
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:CentOS Linux release 7.3.1611 (Core)
Linux 3.10.0-514.6.1.el7.x86_64
3 GB RAM
2 CPUs
50 GB HDD
OpenNMS 19.0.0
-
Sprint:Horizon - September 6th, Horizon - September 13th
I added nodes about the "Manually Add an Interface" and it create a newSuspect event. After more than 20 minutes none of this Nodes were added.
Because It was a installation for testing I stopped opennms, kicked the database and reproduce the bug.
After this I used the discovery to add the node (as specific) and it was added in a few seconds.
I greped the log files after the newSuspect event found that the first event was handled normal (as I can see) and it get to provisiond, but after this provisiond do nothing.
A look at the Events in the UI, they didn’t show any differences, so I had a look at the database. The event from the discovery had ‘eventparms’ (RTT=0.45(string,text);location=Default(string,text)) the event from "Manually Add an Interface" didn’t have it. Could that the cause of this problem?
PS: I wonder that the default logging value in log4j2.xml is DEBUG.
- Is caused by
-
-
- Resolved
-
