Nagios Log Server - migration to 2026

[NMFSTeam]

Migrating index logstash-2026.04.13 from 2026-04-13T00:03:00.000Z to 2026-04-13T00:06:00.000Z

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/nagioslogserver/scripts/migrate_data.php on line 744

[NMFSTeam]

Is it possible to only migrate the server settings (users, LDAP settings, snapshot settings, listening ports, etc.) from the old to the new, without migrating any of the indices?

[jmichaelson]

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 memory limit in php.ini from the default 128M just to get over that hurdle.

Which Linux distribution are you running?

[NMFSTeam]

I re-deployed a VM so we started fresh, and I tried to only check the box to migrate log server settings, but it doesn't seem to do anything. I tried to restart the server after giving it some time, to no avail.

The index from 4/13 is 27.9GB in size. We have others that are 29GB, 30.1GB, etc. Not sure why that one would cause an issue. As state above, since I have re-deployed a fresh VM, this is a non-issue. The application stakeholder isn't too concerned about historic data, just anxious to start using Nagios Log Server again (our current implementation is quite slow).

We are running on Ubuntu 24.04 LTS.