We are trying to migrate from Nagios Log Server 2024R1.3.6 to the latest release 2026R1.2.1. On the old server, we have changed the setting to allow Elasticsearch to listen on all interfaces, and we have added a firewall rule in the operating system to allow this traffic over port 9200/tcp. However, when we run ss -antp | grep LISTEN, we only see 9200 listening on 127.0.0.1. We have tried rebooting the entire system, and the results are the same. I do see port 9300 appears to be listening on all interfaces, but I'm not sure what that is for.
We have tried connecting from the new server running 2026R1.2.1, and it does not work. We tried both via the "Migrate data" feature, and from the command line using netcat (nc). Any assistance you can provide would be greatly appreciated. Thank you.
Nagios Log Server - migration to 2026
- jmichaelson
- Posts: 389
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagios Log Server - migration to 2026
Hi NMFSTeam
Occasionally, we've seen that happen. I'm not entirely sure why, but if you set ti back to localhost and save it, then change to all interfaces and save it, that frequently resolves the problem.
If that doesn't work, go ahead and edit /usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml
Find the network.host line and replace it with network.host: 0.0.0.0
Then make sure the http.host line is commented out by putting a # in front if it
Then restart eleasticsearch, and you should have it set up to migrate data.
That said, since I'm not damiliar with your specific environment, you may want to consider waiting for the 2026R1.3 release of Nagios Log Server. It has massive improvements in migration rom 2024R1, particularly in the areas of dashboards and reports, which 1.2.1 doesn't migrate. Given the possible complexity of your queries, it may not be perfect, but we'd love to hear back with any problems you may have after you migrade the dashboards and reports.
Occasionally, we've seen that happen. I'm not entirely sure why, but if you set ti back to localhost and save it, then change to all interfaces and save it, that frequently resolves the problem.
If that doesn't work, go ahead and edit /usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml
Find the network.host line and replace it with network.host: 0.0.0.0
Then make sure the http.host line is commented out by putting a # in front if it
Then restart eleasticsearch, and you should have it set up to migrate data.
That said, since I'm not damiliar with your specific environment, you may want to consider waiting for the 2026R1.3 release of Nagios Log Server. It has massive improvements in migration rom 2024R1, particularly in the areas of dashboards and reports, which 1.2.1 doesn't migrate. Given the possible complexity of your queries, it may not be perfect, but we'd love to hear back with any problems you may have after you migrade the dashboards and reports.
Please let us know if you have any other questions or concerns.
-Jason
-Jason
-
DoubleDoubleA
- Posts: 305
- Joined: Thu Feb 09, 2017 5:07 pm
Re: Nagios Log Server - migration to 2026
While we are generally reluctant to post/predict specific release dates, we expect 2026R1.3 to release very soon.
Aaron
Product Development Manager
Aaron
Product Development Manager
Re: Nagios Log Server - migration to 2026
Thank you for this information. Sounds like the new release is coming out very soon, so we'll wait a few days and see what happens. Thank you again!