Quick-add node leads to an error (after a longer system uptime)
Description
Environment
OpenNMS Configuration
OpenNMS Version: 17.1.0
Home Directory: /opt/opennms
RRD store by group enabled? False
RRD store by foreign source enabled? False
Reports directory: /opt/opennms/share/reports
Jetty HTTP host: Unspecified
Jetty HTTP port: 8980
Jetty HTTPS host: Unspecified
Jetty HTTPS port: Unspecified
SNMP trap port: 162
Syslog port: 10514
System Configuration
Server Time: Thu Mar 03 15:37:56 CET 2016
Client Time: Thu Mar 03 2016 15:37:56 GMT+0100 (CET)
Java Version: 1.8.0_45 Oracle Corporation
Java Virtual Machine: 25.45-b02 Oracle Corporation
Operating System: Linux 2.6.32-042stab113.11 (amd64)
Servlet Container: jetty/8.1.10.v20130312 (Servlet Spec 3.0)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Firefox/44.0
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Seth Leger June 6, 2016 at 11:43 AM
No additional information furnished, marking as incomplete.
Seth Leger March 29, 2016 at 10:25 AM
Can you explain more about the problem? Why can't you update any provisioning configuration for the first 30 minutes that the system is online? Is the system under excessive load?
Incomplete
Details
Assignee
UnassignedUnassignedReporter
guenther.schreinerguenther.schreinerLabels
Components
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
guenther.schreinerLabels
Components
Affects versions
Priority
MajorPagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Created March 3, 2016 at 9:41 AM
Updated June 6, 2016 at 11:43 AM
Resolved June 6, 2016 at 11:43 AM
The Quick-add throws an error for any new entry ... after a longer runtime than 30 minutes. In fact, during the about first 30 minutes after starting the OpenNMS there is no modification of provisioning possible at all.