Nagios Log Server - migration to 2026

[NMFSTeam]

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.

[jmichaelson]

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.

[DoubleDoubleA]

While we are generally reluctant to post/predict specific release dates, we expect 2026R1.3 to release very soon.

Aaron
Product Development Manager

[NMFSTeam]

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!

[NMFSTeam]

We downloaded the new release and have begun our migration. Question for you, it is moving the indices right now, and it seems to be stuck on one of them, it has been at 40% on this one index for the last two days. Not sure how to restart, get past, see what's going on, etc. Any help would be appreciated, thank you.

[jmichaelson]

It may not actually be stuck. If it was the current day's log index, it is possible, if not likely, that more logs came in after the migration started. The percentage is based on the number of logs in the source index when the migration started. If the number of logs isn't increasing, the reindex process has finished and its safe to restart the migration of that index.

Regardless of whether this is the case, you can return to the migration page and reinitiate migrating the index, checking the box to reprocess the selected indices. This will start the migration of that index as though it hadn't been migrated at all (and if it was the current day's index, migrate anything more recent while you're at it if you're so inclined).

By all means, however please let us know if there's any way we can improve this process. As of Nagios Log Server 2026R1.3, we believe that we're migrating everything that we can. There may be unique situations that we don't know about that we can migrate in future releases.

[NMFSTeam]

The index is from April 13, so no new data should be coming in. The migrated log entry count has not changed in at least a few hours. I'm not sure what to do at this point, check the box to reprocess, or don't?

[jmichaelson]

Check the box to reprocess for that index, and rerun the migration

[NMFSTeam]

I appreciate it. I tried re-running it last night, and checked on it today and it is sitting at 0%. I spoke with the application owner, and turns out he isn't too concerned with past data, so we may just skip it. I have re-started the migration and just selected that last 7 days worth of indices, we'll see what happens.

[jmichaelson]

What do you get if you run the commend:

Code: Select all

php  /usr/local/nagioslogserver/scripts/migrate_data.php -s << ip address of your old NLS server>> -l -i logstash-2026.04.13 -r

Replace the << ip address of your old NLS server> with the ip address of your source server.

There will be a lot of output. But let it do its thing and see if it's stalling someplace, or what ends up happening.