Import NLS index to new NLS server

[akaspar]

Scenario: Due to HTTPD issues we faced past weeks related to upgrading to PHP7.4 and SourceGuardian init problems, out NLS httpd suddenly decided not to come up anymore (manual fix was done before NLS last update rollout v.2.1.6). Long story short, I configured at NLS to store logs not locally but at a NAS device; everything working find there. After rebuilding Nagios LS (but not before installing PHP and all the preps), the new NLS has its own Cluster ID/Instance ID, which of course does not match the old one stored at the NAS device. Since important logs are stored at the old Instance ID path /mnt/nagioslog/ emmeed4f-f326-xxxxx-bb0c-7aeb0000000/node/0 < -- example, I need import all those indices/index (logstash) to the new NFS path (same NAS device, same NFS path, different instance ID), so I can query those at the new NLS instance.

Question: As I have now a new Instance ID, is there a proper way (documented by Nagios) to make such imports?
Does the “Import from File” with shipper.py do what I need to accomplish? – If yes, need some help on how to execute if possible.

[cdienger]

We don't have any official documents on this and I haven't tested it yet, but I would try this first:

Code: Select all

cp -R --preserve /mnt/nagioslog/emmeed4f-f326-xxxxx-bb0c-7aeb0000000/node/0 /mnt/nagioslog/new-cluster-id/node/0/

[akaspar]

Your solution did not quite fit since I would copy all content in /0, which isnt what I want. But.... moving all logstash files did the trick, since elasticsearch will pick them up from the system path declared for data.

Thanks....

post can be closed.

[scottwilkerson]

Your solution did not quite fit since I would copy all content in /0, which isnt what I want. But.... moving all logstash files did the trick, since elasticsearch will pick them up from the system path declared for data.

Thanks....

post can be closed.

Closing thread