Re: best practice WRT use of "provision.pl requisition import ..."

Found the issue per a post from Jesse White dated 2017-03-29:

	"If you are not using Minions, the Node should not be associated with a Location, or should be set to the use "Default" location."

Indeed I was populating the Location field for the first time and wasn't aware of this dependency.

Happiness.

-Paul


-----Original Message-----
From: Hernandez, Paul 
Sent: Wednesday, February 21, 2018 11:53 AM
To: 'General OpenNMS Discussion' <[email protected]>
Subject: RE: [opennms-discuss] best practice WRT use of "provision.pl requisition import ..."

Excellent. Thank you Ron as that matched my best guess.

The nodes are being defined in the requisition for a 5 node (linus hosts) testcase. The only three detectors I have defined for the req for the moment are ICMP, SSH, and SNMP for this testcase.
When I drill down into a node I see the interface properly defined but oddly no service definitions for those detectors.

In provisiond.log:

Exchange
---------------------------------------------------------------------------------------------------------------------------------------
Exchange[###REPLACE_ME###   Id                  ID-cas-onms-dev-vm-34842-1519240743336-0-140###REPLACE_ME###    ExchangePattern     InOut###REPLACE_ME###   Headers             {breadcrumbId=ID-cas-onms-dev-vm-34842-1519240743336-0-128, CamelJmsRequestTimeout=20000, CamelRedelivered=false, CamelRedeliveryCounter=0, JMSCorrelationID=Camel-ID-cas-onms-dev-vm-34842-1519240743336-0-130, JmsQueueName=OpenNMS.NA-SJE-Fremont.RPC.Detect}###REPLACE_ME###    BodyType            String###REPLACE_ME###  Body                [Body is not logged]]

Stacktrace
---------------------------------------------------------------------------------------------------------------------------------------
org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-cas-onms-dev-vm-34842-1519240743336-0-130 not received on destination: temp-queue://ID:cas-onms-dev-vm-38008-1519240738595-3:8:1. Exchange[Message: [Body is not logged]] .
.
.

and in web.log:

2018-02-21 11:24:28,412 WARN  [qtp1203221407-309] o.e.j.s.h.ErrorHandler: EXCEPTION
org.apache.jasper.JasperException: An exception occurred processing JSP page /errors/elementnotfound.jsp at line 46

43:         enfe = (ElementNotFoundException)exception;
44:     }
45:     else if( exception instanceof ServletException ) {
46:         enfe = (ElementNotFoundException)((ServletException)exception).getRootCause();
47:     }
48:     else {
49:         throw new ServletException( "This error page does not handle this exception type.", exception );


Stacktrace:
    at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:584) ~[apache-jsp-8.5.5.jar:2.3] .
.
.


Have looked for threads on this but wasn't able to find a resolution.  Have tried the:
dropdb -U postgres opennms
/opt/opennms/bin/install -dis

but above errors persist.

Thanks in advance,
Paul








-----Original Message-----
From: Roskens, Ronald [mailto:[email protected]]
Sent: Wednesday, February 21, 2018 10:18 AM
To: General OpenNMS Discussion <[email protected]>
Subject: Re: [opennms-discuss] best practice WRT use of "provision.pl requisition import ..."

At the end of the script, call "provision.pl requisition import $requisition" for each requisition you just created.

This will cause OpenNMS to import that requistion's data, and kick off a scan of those hosts to add any detected services to them.

For this initial call of the script, the deployed requisitions are empty inside OpenNMS, so the only rescanExisting flag that would affect the overall run would be dbonly.  Then it would just update the database to synchronize the nodes, interfaces, and services. It wouldn't kick off a scan phase using either the default or requisition foreign source detectors & policies.

Ron 

----------------------------------------------------------------------
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

------------------------------------------------------------------------------
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