The indexing engine Installation wizard does not support installing elastic on a machine that does not have Dataminer installed. We tried to setup elastic search on that machine using the provided elastic distribution and configure Dataminer to use that elastic instance by adding an entry into the DB.xml.
<DataBase active="true" search="true" type="Elasticsearch">
<DBServer>10.10.10.11</DBServer>
</DataBase>
Now the job manager log shows that it is initialized successfully and we can access the user interface. Also in search and indexing page, install indexing engine is not longer shown and migrate data to indexing engine is shown instead (we can see data in the elastic database already). However, when we access the job manager a pop up message as the following appears and no job domain is configured in the manager. i.e DefualtJobDomain
Installing DataMiner Indexing Engine says that we have to run an automation script to connect Dataminer to a remote Elastic instance, which we did not do as we do not know where to find the library implementing it.
Is it possible to have elastic on a machine that does not have DM agent installed? if so how to do this without the wizard and what is missing in what we have done?
Thanks
Hello,
I'm going to assume that everything went correctly, since your DMA is indicating that the Elastic is working. You could double check if you've installed the correct version of Elastic trough going to 10.10.10.11:9200 and checking if the version mentions a 6.x.x installation (most likely 6.8.x).
The equivalent of that automation script is actually manually adjusting the DB.Xml's in the DMS and then restarting.
We are currently working to making the installation procedure allow remote installations fully. (so the manual work should no longer be done, apart from installing the Elastic on the remote server).
To fully verify that your Elastic is behaving correctly, you could open the SLSearch Log file and find the line:"Connecting with http://10.10.10.11:9200/". After this indices should be created ("Creating index for: alarms"). If this appears in the SLSearch log file, we can assume that the connection was made succesfully and the issue is somewhere else.
Kind regards,
Thanks Thomas! The indexing engine is now installed and we can access the job manager without any problem. However, after running elastic for some hours, it starts to throw the following warning message regularly
[2020-12-11T14:45:56,943][WARN ][o.e.x.m.e.l.LocalExporter] [DMA] unexpected error while indexing monitoring document
org.elasticsearch.xpack.monitoring.exporter.ExportException: [.monitoring-es-6-2020.12.11] IndexNotFoundException[no such index]
at org.elasticsearch.xpack.monitoring.exporter.local.LocalBulk.lambda$throwExportException$2(LocalBulk.java:125) ~[?:?]
Have you seen such a warning before?
Also the status of the indices in Kibana are shown to be yellow for some reason. This could be due to the fact that our cluster consists of one node and therefore there is no other node to replicate the data.
Do you know how to fix this?
Kind Regards,
Kind regards,