Duplicate
Details
Assignee
UnassignedUnassignedReporter
Cyrille BolluCyrille BolluLabels
Components
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Cyrille Bollu
Cyrille BolluLabels
Components
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created November 4, 2015 at 3:54 AM
Updated November 6, 2015 at 4:26 PM
Resolved November 6, 2015 at 4:25 PM
Hi,
I've stumbled upong the following error when trying to provision new nodes with OpenNMS-17 on my dev box:
2015-11-04 09:44:34,734 INFO [scanExecutor-1] o.o.n.p.s.NewSuspectScan: Attempting to scan new suspect address 10.4.1.143 for foreign source null
2015-11-04 09:44:34,839 WARN [scanExecutor-1] o.h.u.JDBCExceptionReporter: SQL Error: 0, SQLState: 23502
2015-11-04 09:44:34,839 ERROR [scanExecutor-1] o.h.u.JDBCExceptionReporter: ERROR: null value in column "monitoringarea" violates not-null constraint
Is there any valid reason why monitoringarea shall be not-null? And, how should I work around this (I haven't found any requisition policy allowing me to set this value)?
Best regards,