Nagios Support Forum

Thanks! I liked the idea of a copy rather than a migration so stopped elasticsearch, created a tarball of /usr/local/nagioslogserver/elasticsearch/data, copied the data over to /nagioslog_data/elasticsearch/data, modified the DATA_DIR in /etc/sysconfig/elasticsearch, then started elasticsearch. Base...

I'm thinking that I should
(1)shut down elasticsearch
(2)migrate the data from /usr/local/nagioslogserver/elasticsearch/data to /nagioslog_data/elasticsearch/data
(3)edit the /etc/sysconfig/elasticsearch
(4)restart elasticsearch

could fix the data location issue?

There is data in the location you specified on the new node: # ls -l /usr/local/nagioslogserver/elasticsearch/data/4261ea49-46b2-43f8-b7b5-4378a217f92c/nodes/0 total 4 drwxr-xr-x 55 nagios nagios 4096 Jun 4 11:02 indices -rw-r--r-- 1 nagios nagios 0 Jun 4 11:02 node.lock drwxr-xr-x 2 nagios nagios 2...

I was having problems connecting a new LS to my existing 3 node cluster, getting a connection timeout error every time I tried to join. I went through the forums and tried everything, but continued to get 504 errors. Out of desperation, I restarted elasticsearch on the new node. When I went to http:...

As an FYI, I added an additional 4 GB to all log servers, bumping the memory up to 12 GB from 8 GB. This looks likes it may have resolved my issue

I've attached the information.

The Nagios Log server is a 4 server cluster with ~1900 linux servers pointing to them. When this problem occurs, the log searches are no longer functional. the four servers have 2 cpus each and 8GB of memory. They do not appear to be bottle-necked by these resources. They are all VMs (VMWare). Resta...