Nagios Support Forum

As long as it keeps moving, it will eventually finish. If you get a PHP exception and it stops, please let us know!

That looks like it's pulling everything from your old audit log. depending on how large it is, that could take a long time. You may want to consider truncating it. To do that go into Admin->Snapshots & Maintenance and set delete audit lg entries older than .... days. It accepts decimals down to ...

Thee underlying command for that is php /usr/local/nagioslogserver/scripts/migrate_data.php -s << ip address of your old NLS server>> -c -r This one may produce a log of output to weed through to find the cause of what's going on. If you have a problem where PHP is exhausting its memory, add memory_...

Certainly. Don't check any of the data indexes for migration, and check the "Migrate Log Server configuration." box at the bottom of the migration page. As for your 2026/04/13 index, out of curiosity, how big is the index? Even though you *shouldn't* have tom you may have to increase the m...

You can grab and resize the table panel by using the resize tools at the bottom left and right corners of the table (and any other panel you need to resize from the default sizes). Then save your dashboard, of course.

What do you get if you run the commend: 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 i...

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

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 pr...

I think the easiest thing to do there would be to configure lighttpd to send logs in the apache common log format, clone the existing apache filter and edit it for whatever changes you make for the process name in rsyslog, and then tweak the rsyslog config to point to the lighttpd logs with an appro...

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/elast...