No data being collected when nodes added via Provisioning Requisitions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
46 messages Options
123
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
i am testing the functionality of Provisioning Requisitions and i have created 4 unique Requisitions.  Each requisition has at least one node defined and in the database.  When I look at the nodes themselves there isn't any data being collected.

Under the Availability section I am not seeing any of the services that should have been picked up in a discovery scan.  Under the requisition I have not removed or made any changes to the Detectors or Policies.  These should be run by default in a discovery scan..??  

Any help to point me in the right direction to get this issue resolved would be great.

Thank you.

-Patrick


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

David Hustace

> On Mar 22, 2017, at 2:36 PM, Patrick Topping <[hidden email]> wrote:
>
> Any help to point me in the right direction to get this issue resolved would be great.

I’m guessing that you are referring to SNMP data so and since there isn’t an SNMP service discovered I’m assuming that you having configured the SNMP settings to support those provisioned nodes.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
David,

I am referring to all services for a node when provisioned in a requisition.  I am not seeing services like SSH or HTTP/HTTPS for devices that support these services.  I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.  

Thank you.

-Patrick


On Wed, Mar 22, 2017 at 11:51 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 2:36 PM, Patrick Topping <[hidden email]> wrote:
>
> Any help to point me in the right direction to get this issue resolved would be great.

I’m guessing that you are referring to SNMP data so and since there isn’t an SNMP service discovered I’m assuming that you having configured the SNMP settings to support those provisioned nodes.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

David Hustace

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.  

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

John Blake

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Christy Cooper
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
In reply to this post by John Blake
I checked /opt/opennms/etc/imports and thought the issue might be because I have a space in the Requisition name so I aded EQAT2 and got the exact same error.

2017-03-23 16:32:20,186 ERROR [importExecutor-5] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQAT2.xml.1490286722126]

Looking at what is in /opt/opennms/etc/imports I do not have any files with anything appended past .xml.

root@opennms
[/opt/opennms/etc/imports]# ls -l
total 36
-rw-rw-r--. 1 root root  378 Mar 23 16:32 EQAT2.xml
-rw-rw-r--. 1 root root  380 Mar 23 04:19 EQ CH2.xml
-rw-rw-r--. 1 root root  378 Mar 23 14:40 EQ DA6.xml
-rw-rw-r--. 1 root root  387 Mar 23 04:22 EQ DC2.xml
-rw-rw-r--. 1 root root  384 Mar 23 04:18 EQ LA1.xml
-rw-rw-r--. 1 root root  386 Mar 23 04:20 EQ NY8.xml
-rw-rw-r--. 1 root root  379 Mar 23 14:19 EQ SE2.xml
-rw-rw-r--. 1 root root  381 Mar 23 04:21 EQ SV5.xml
drwxrwxr-x. 2 root root 4096 Mar 23 16:32 pending
root@opennms
[/opt/opennms/etc/imports]# cd pending/
root@opennms
[/opt/opennms/etc/imports/pending]# ls -l
total 0

I am not sure where I am screwing this up.....

-Patrick


On Thu, Mar 23, 2017 at 8:01 AM, John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

John Blake

Are these the steps you are following?
https://wiki.opennms.org/wiki/Requisition_Editor

From the name of the file, it might be that you are not hitting the "done" button.
Those last numbers of the file name appear to be epoch timestamps.

John

-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 12:38PM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I checked /opt/opennms/etc/imports and thought the issue might be because I have a space in the Requisition name so I aded EQAT2 and got the exact same error.

2017-03-23 16:32:20,186 ERROR [importExecutor-5] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQAT2.xml.1490286722126]

Looking at what is in /opt/opennms/etc/imports I do not have any files with anything appended past .xml.

root@opennms
[/opt/opennms/etc/imports]# ls -l
total 36
-rw-rw-r--. 1 root root  378 Mar 23 16:32 EQAT2.xml
-rw-rw-r--. 1 root root  380 Mar 23 04:19 EQ CH2.xml
-rw-rw-r--. 1 root root  378 Mar 23 14:40 EQ DA6.xml
-rw-rw-r--. 1 root root  387 Mar 23 04:22 EQ DC2.xml
-rw-rw-r--. 1 root root  384 Mar 23 04:18 EQ LA1.xml
-rw-rw-r--. 1 root root  386 Mar 23 04:20 EQ NY8.xml
-rw-rw-r--. 1 root root  379 Mar 23 14:19 EQ SE2.xml
-rw-rw-r--. 1 root root  381 Mar 23 04:21 EQ SV5.xml
drwxrwxr-x. 2 root root 4096 Mar 23 16:32 pending
root@opennms
[/opt/opennms/etc/imports]# cd pending/
root@opennms
[/opt/opennms/etc/imports/pending]# ls -l
total 0

I am not sure where I am screwing this up.....

-Patrick


On Thu, Mar 23, 2017 at 8:01 AM, John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
In reply to this post by Christy Cooper
I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

John Blake
 Off topic real quick but I personally think you should get a reward for watching Tarus's video that often.
Gotta be a record or something.

heh


-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
I am grasping at anything here.....  If this takes this much effort to get up and running I may need to ditch OpenNMS



On Thu, Mar 23, 2017 at 12:04 PM, John Blake <[hidden email]> wrote:
 Off topic real quick but I personally think you should get a reward for watching Tarus's video that often.
Gotta be a record or something.

heh


-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM

Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

John Blake
In reply to this post by Patrick Topping

 So you create a Requ,
 then add a node,
 then add an ip to that node.
 Do you add any services to it?
Can you add just ICMP so we can just have a basic setup?

John

-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
John,

I added a single node with ICMP and I am getting the exact same error in provisiond.log.

2017-03-23 19:39:16,238 ERROR [importExecutor-3] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490297949662]
java.io.FileNotFoundException: there is no file called 'EQ LA1.xml.1490297949662' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.GeneratedMethodAccessor705.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 19:39:37,719 WARN  [importExecutor-5] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.0.1 at location EQ LA1. Using IP address as hostname.


Is this an issue with the latest version of OpenNMS..?? 

-Patrick


On Thu, Mar 23, 2017 at 12:28 PM, John Blake <[hidden email]> wrote:

 So you create a Requ,
 then add a node,
 then add an ip to that node.
 Do you add any services to it?
Can you add just ICMP so we can just have a basic setup?

John

-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM

Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

John Blake

Maybe I'm reading it wrong but its stating it cant save the cache of the file in the "imports/pending" and put a copy of it in "imports".
Are the permissions on those directories ok?



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 03:42PM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

John,

I added a single node with ICMP and I am getting the exact same error in provisiond.log.

2017-03-23 19:39:16,238 ERROR [importExecutor-3] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490297949662]
java.io.FileNotFoundException: there is no file called 'EQ LA1.xml.1490297949662' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.GeneratedMethodAccessor705.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 19:39:37,719 WARN  [importExecutor-5] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.0.1 at location EQ LA1. Using IP address as hostname.


Is this an issue with the latest version of OpenNMS..?? 

-Patrick


On Thu, Mar 23, 2017 at 12:28 PM, John Blake <[hidden email]> wrote:

 So you create a Requ,
 then add a node,
 then add an ip to that node.
 Do you add any services to it?
Can you add just ICMP so we can just have a basic setup?

John

-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM

Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Roskens, Ronald-2
In reply to this post by Patrick Topping

I wonder if there is something watching the imports directory for new files and it tries to import them in. So when it saves the copy of the file from pending with the .{time}, the scanner sees the file and tries to initiate the import of it?


Ron

 

From: Patrick Topping [mailto:[hidden email]]
Sent: Thursday, March 23, 2017 2:41 PM
To: General OpenNMS Discussion
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

 

John,

 

I added a single node with ICMP and I am getting the exact same error in provisiond.log.

 

2017-03-23 19:39:16,238 ERROR [importExecutor-3] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490297949662]

java.io.FileNotFoundException: there is no file called 'EQ LA1.xml.1490297949662' in directory /opt/opennms/etc/imports

            at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]

            at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]

            at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]

            at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]

            at sun.reflect.GeneratedMethodAccessor705.invoke(Unknown Source) ~[?:?]

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]

            at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]

            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]

            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]

            at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]

            at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]

            at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]

            at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]

            at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]

            at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]

            at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]

            at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]

            at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]

            at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]

            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]

            at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]

            at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]

2017-03-23 19:39:37,719 WARN  [importExecutor-5] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.0.1 at location EQ LA1. Using IP address as hostname.

 

 

Is this an issue with the latest version of OpenNMS..?? 

 

-Patrick

 

 

On Thu, Mar 23, 2017 at 12:28 PM, John Blake <[hidden email]> wrote:


 So you create a Requ,
 then add a node,
 then add an ip to that node.
 Do you add any services to it?
Can you add just ICMP so we can just have a basic setup?

John

-----Patrick Topping <[hidden email]> wrote: -----

To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM


Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

 

·         Add Requisition

·         Add a Node

o    Add Node Label

o    Add IP Address

o    Click Save

o    Click Return

·         Click Return from Requisition EQ LA1 screen

·         Synchronize Requisition EQ LA1 ( Using YES )

·         Give it a few and confirm the node is in the database

I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

 

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

 

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

 

Thank you.

 

-Patrick

 

 

On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:

Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:


" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----

To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

 

David,

 

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

 

-Patrick

 

///////////////////////////////////////////////////////////////////////////////////////////////////////////

 

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]

java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports

at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]

at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]

at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]

at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]

at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]

at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]

at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]

at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]

at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]

at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]

at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]

at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]

at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]

at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]

at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]

at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]

at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]

2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.

2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)

2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is [hidden email] source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]

2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = [hidden email] source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]

2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = [hidden email]

 

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:


> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.



David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

 


This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Patrick Topping
In reply to this post by John Blake
They are the default permissions that the system / application was installed with.  They are listed below:

root@opennms
[/opt/opennms]# ls -ld etc
drwxrwxr-x. 21 root root 12288 Mar 23 00:05 etc

root@opennms
[/opt/opennms/etc]# ls -ld imports/
drwxr-xr-x. 3 root root 4096 Mar 23 19:39 imports/

root@opennms
[/opt/opennms/etc/imports]# ls -l
total 8
-rw-rw-r--. 1 root root  452 Mar 23 19:39 EQ LA1.xml
drwxrwxr-x. 2 root root 4096 Mar 23 19:39 pending

I checked /etc/passwd and I don't see an opennms user.  Does everything run as root..??

Thank you.

-Patrick



On Thu, Mar 23, 2017 at 1:08 PM, John Blake <[hidden email]> wrote:

Maybe I'm reading it wrong but its stating it cant save the cache of the file in the "imports/pending" and put a copy of it in "imports".
Are the permissions on those directories ok?



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 03:42PM

Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

John,

I added a single node with ICMP and I am getting the exact same error in provisiond.log.

2017-03-23 19:39:16,238 ERROR [importExecutor-3] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490297949662]
java.io.FileNotFoundException: there is no file called 'EQ LA1.xml.1490297949662' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.GeneratedMethodAccessor705.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 19:39:37,719 WARN  [importExecutor-5] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.0.1 at location EQ LA1. Using IP address as hostname.


Is this an issue with the latest version of OpenNMS..?? 

-Patrick


On Thu, Mar 23, 2017 at 12:28 PM, John Blake <[hidden email]> wrote:

 So you create a Requ,
 then add a node,
 then add an ip to that node.
 Do you add any services to it?
Can you add just ICMP so we can just have a basic setup?

John

-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 02:45PM

Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions

I apologize for something that seems to be very simple....  I have attached the steps that I am doing throughout the adding of a Requisition as well as adding of a node and I do not see any step that is being missed.  I have watched Tarus' YouTube video a dozen times to see if there is a step I am missing and I do not see one ( https://www.youtube.com/watch?v=atK-zYYEzd0&t=375s )

  • Add Requisition
  • Add a Node
    • Add Node Label
    • Add IP Address
    • Click Save
    • Click Return
  • Click Return from Requisition EQ LA1 screen
  • Synchronize Requisition EQ LA1 ( Using YES )
  • Give it a few and confirm the node is in the database
I checked /opt/opennms/etc/imports/pending before synchronizing and file "EQ LA1.xml.1490294066281" is not there so I get the following error:

2017-03-23 18:35:32,660 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ LA1.xml.1490294066281]

Is this a bug in the version of OpenNMS that I am running..??  Should I downgrade..??  Is there a patch..??  

Thank you.

-Patrick


On Thu, Mar 23, 2017 at 8:19 AM, Christy Cooper <[hidden email]> wrote:
Looks like the provisioning req isn't being written for some reason. Have you looked to make sure it's being generated in the imports directory? And the pending? Maybe you're not syncing it because it's not been written. 

On Thu, Mar 23, 2017 at 9:10 AM John Blake <[hidden email]> wrote:

" there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports"



-----Patrick Topping <[hidden email]> wrote: -----
To: General OpenNMS Discussion <[hidden email]>
From: Patrick Topping <[hidden email]>
Date: 03/23/2017 10:40AM
Subject: Re: [opennms-discuss] No data being collected when nodes added via Provisioning Requisitions


David,

This is a new install of OpenNMS and the DB only has the few nodes that I have been trying to add via Provisioning.  Below is the log output from a node I tried to add this morning.  I do see some an aborted message in the log but I am not sure this is related to the lack of services / data that I am seeing.

-Patrick

///////////////////////////////////////////////////////////////////////////////////////////////////////////

2017-03-23 14:19:00,236 ERROR [importExecutor-7] o.o.n.p.p.FasterFilesystemForeignSourceRepository: importResourceRequisition: can't save cached requisition associated with file [/opt/opennms/etc/imports/pending/EQ SE2.xml.1490278733428]
java.io.FileNotFoundException: there is no file called 'EQ SE2.xml.1490278733428' in directory /opt/opennms/etc/imports
at org.opennms.netmgt.provision.persist.DirectoryWatcher.getContents(DirectoryWatcher.java:257) ~[opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FasterFilesystemForeignSourceRepository.importResourceRequisition(FasterFilesystemForeignSourceRepository.java:92) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.persist.FusedForeignSourceRepository.importResourceRequisition(FusedForeignSourceRepository.java:97) [opennms-provision-persistence-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.DefaultProvisionService.loadRequisition(DefaultProvisionService.java:1058) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) [org.apache.servicemix.bundles.spring-aop-4.0.7.RELEASE_1.jar:?]
at com.sun.proxy.$Proxy169.loadRequisition(Unknown Source) [?:?]
at org.opennms.netmgt.provision.service.CoreImportActivities.loadSpecFile(CoreImportActivities.java:74) [opennms-provisiond-19.0.1.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.doInvoke(Phase.java:196) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod.access$100(Phase.java:160) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.netmgt.provision.service.lifecycle.Phase$PhaseMethod$1.run(Phase.java:178) [opennms-provisiond-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.run(SyncTask.java:88) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask.access$000(SyncTask.java:41) [org.opennms.core.tasks-19.0.1.jar:?]
at org.opennms.core.tasks.SyncTask$1.run(SyncTask.java:100) [org.opennms.core.tasks-19.0.1.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) [?:1.8.0_45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_45]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
2017-03-23 14:19:22,671 WARN  [importExecutor-4] o.o.n.p.s.DefaultHostnameResolver: Reverse lookup failed for /37.244.5.1 at location EQ SE2. Using IP address as hostname.
2017-03-23 14:20:04,727 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: node added event (1490278804727)
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: scheduleForNode is org.opennms.netmgt.provision.service.NodeScanSchedule@791cd818[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,initial delay=PT0S,scan interval=PT86400S]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: nodeScan = org.opennms.netmgt.provision.service.NodeScan@1842ad46[foreign source=EQ SE2,foreign id=1490278694805,node id=7,location=EQ SE2,aborted=false,provision service=org.opennms.netmgt.provision.service.DefaultProvisionService@6900e6b5]
2017-03-23 14:20:04,937 WARN  [Provisiond:EventListener-Thread] o.o.n.p.s.Provisioner: addToScheduleQueue future = java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3f7b5acc

On Thu, Mar 23, 2017 at 2:40 AM, david <[hidden email]> wrote:

> On Mar 22, 2017, at 4:04 PM, Patrick Topping <[hidden email]> wrote:
>
> I have configured the snmp RO string in snmp-config.xml and I thought that this would be used when doing discovery of a newly provisioned node.

The easiest way to diagnose this, in my opinion, would be to start with a clean DB and logs and configure DB logging for Provisiond then provision a single node.  I would examine the logs to see if the detectors are bering run and if they are what may be causing them to fail to discover the services you believe should have been found.


David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

P-A Panon
I was just looking to add a new post that, having just upgraded to from Horizon 18 to Horizon 19, I suddenly can't seem to modify the Provisioning Requisitions or the associated Foreign Sources. I get a Page not found error. When I saw this thread and thought it could be related.

Our installation is on CentOS with rpms from the rpm repository. Trying to create a new Requisition, I couldn't seem to do more than enter the name. Could this be a packaging problem where files necessary for those functions got missed or didn't get the proper SELinux context settings? The GUI layout seems to have changed significantly, so perhaps something was missed on associated back-end functions.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

David Hustace
In reply to this post by Patrick Topping

> On Mar 23, 2017, at 3:13 PM, Patrick Topping <[hidden email]> wrote:
>
> I am grasping at anything here.....  If this takes this much effort to get up and running I may need to ditch OpenNMS

Start clean, again.  If you don’t have any nodes in the system it just makes it easier for us to help.  


Shutdown.
Remove the OpenNMS logs
$ sudo rm -rf /var/logs/opennms/*.log*

Clean the DB:
$ dropdb --username=opennms opennms
$ sudo /opt/opennms/bin/install -dis

Edit etc/log4j2.xml and put Provisiond in DEBUG logging mode.

Provision one of the nodes.  If you don’t get what you’re looking for, send us the provisiond.log file.



David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No data being collected when nodes added via Provisioning Requisitions

Christy Cooper
The only other thing I could think of was maybe you can't write because full disk or mount point mounted RO. It's usually not this difficult to bring up. 

--c

On Fri, Mar 24, 2017 at 4:53 AM david <[hidden email]> wrote:

> On Mar 23, 2017, at 3:13 PM, Patrick Topping <[hidden email]> wrote:
>
> I am grasping at anything here.....  If this takes this much effort to get up and running I may need to ditch OpenNMS

Start clean, again.  If you don’t have any nodes in the system it just makes it easier for us to help.


Shutdown.
Remove the OpenNMS logs
$ sudo rm -rf /var/logs/opennms/*.log*

Clean the DB:
$ dropdb --username=opennms opennms
$ sudo /opt/opennms/bin/install -dis

Edit etc/log4j2.xml and put Provisiond in DEBUG logging mode.

Provision one of the nodes.  If you don’t get what you’re looking for, send us the provisiond.log file.



David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
123
Loading...