Re: [External] Re: Alarm-Change-Notifier error forwarding alarms to Elasticsearch

I understand that, but we’re primarily a Windows shop and it would be a tough sell to switch to Linux.

I’ve run into a few idiosyncrasies running on Windows, but in general it runs fine.

I did install it on CentOS 7 and was able to get event and alarm forwarding working.  I was hoping to compare configs and see if I could find something that would help get the Windows config right, but no such luck.

Dave



From: Dino Yancey [mailto:[email protected]]
Sent: Thursday, May 03, 2018 11:47 AM
To: General OpenNMS Discussion <[email protected]>
Subject: [External] Re: [opennms-discuss] Alarm-Change-Notifier error forwarding alarms to Elasticsearch


This email is from an external source. Please exercise caution in opening attachments or links.
My recommendation would be not to run OpenNMS on Windows.  It's not well tested, and issues like this are common.

On Thu, May 3, 2018 at 7:31 AM, Ostock,David J. <[email protected]<mailto:[email protected]>> wrote:
I’ve reached an impasse trying to get event and alarm forwarding from OpenNMS to Elasticsearch working on Windows.

I’ve been able to successfully forward raw events, although there is a problem with the logmsg field in the index (shown below):

2018-04-27T13:32:58,143 ERROR opennms-es-rest.main-module:21.1.0(244) [Thread-109] org.opennms.plugins.elasticsearch.rest.ElasticSearchInitialiser: Error sending template 'eventsindextemplate' to Elasticsearch received result: {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [logmsg]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [_default_]: No handler for type [string] declared on field [logmsg]","caused_by":{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [logmsg]"}},"status":400}
   response code:400
   error message: {"root_cause":[{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [logmsg]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [_default_]: No handler for type [string] declared on field [logmsg]","caused_by":{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [logmsg]"}}

The bigger problem with the alarm-change-notifier is a showstopper.  It can’t find opennms-datasources.xml in .\etc.  The file does exist, so I’m guessing the path it’s looking for the file is wrong somewhere.

2018-05-02T15:53:59,309 ERROR org.apache.aries.blueprint.core:1.8.3(16) [features-1-thread-1] org.apache.aries.blueprint.container.BlueprintContainerImpl: Unable to start blueprint container for bundle alarm-change-notifier.main-module/21.1.0
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to initialize bean pgDataSourceFactory
Caused by: java.lang.RuntimeException: cannot load database values from .cfg or opennms-datasources.xml
                at org.opennms.plugins.dbnotifier.DbNotifierDataSourceFactory.init(DbNotifierDataSourceFactory.java:231) ~[?:?]
Caused by: java.io.FileNotFoundException: .\etc\opennms-datasources.xml (The system cannot find the path specified)
                at java.io.FileInputStream.open0(Native Method) ~[?:?]

I tried reinstalling and also sifted through the source code to try and figure out where it was looking for the file, but was unsuccessful.
From the error in the log, it looks like you can override database values using a .cfg file like the other plugins.  I searched the docs and source code for the .cfg filename but couldn’t find it.  Out of desperation I guessed at it, trying org.opennms.plugin.alarm.change.notifier.cfg and org.opennms.plugin.alarm-change-notifier.cfg, but no joy ☹

Anyone have any suggestions on next steps?  I’d really like to get this working.

Thanks,
Dave


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