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
Nagios Log Server - migration to 2026
Re: Nagios Log Server - migration to 2026
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
- Posts: 398
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagios Log Server - migration to 2026
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?
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?
Please let us know if you have any other questions or concerns.
-Jason
-Jason
Re: Nagios Log Server - migration to 2026
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.
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.
- jmichaelson
- Posts: 398
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagios Log Server - migration to 2026
Thee underlying command for that is
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_limit = 1024M to /etc/php/8.3/cli/php.ini
Code: Select all
php /usr/local/nagioslogserver/scripts/migrate_data.php -s << ip address of your old NLS server>> -c -rIf you have a problem where PHP is exhausting its memory, add memory_limit = 1024M to /etc/php/8.3/cli/php.ini
Please let us know if you have any other questions or concerns.
-Jason
-Jason
Re: Nagios Log Server - migration to 2026
How long is the command supposed to run until it is finished? Been going for a while now... (maybe 30 mins?). Just seems to be a lot of this...
Code: Select all
Migrating index nagioslogserver_log hit type: MAINTENANCE id: AZk10yl6hNdxeYGrcYqN
index: nagioslogserver_log, type: MAINTENANCE, id: AZk10yl6hNdxeYGrcYqN, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk1zoiJhNdxeYGraf7I
index: nagioslogserver_log, type: JOBS, id: AZk1zoiJhNdxeYGraf7I, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk1z9LShNdxeYGrbBwK
index: nagioslogserver_log, type: JOBS, id: AZk1z9LShNdxeYGrbBwK, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk10IO6hNdxeYGrbU7A
index: nagioslogserver_log, type: JOBS, id: AZk10IO6hNdxeYGrbU7A, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk10mtfhNdxeYGrcFkr
index: nagioslogserver_log, type: JOBS, id: AZk10mtfhNdxeYGrcFkr, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk10wgxhNdxeYGrcVem
index: nagioslogserver_log, type: JOBS, id: AZk10wgxhNdxeYGrcVem, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk11N8phNdxeYGrdE-z
index: nagioslogserver_log, type: JOBS, id: AZk11N8phNdxeYGrdE-z, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk1ztd5hNdxeYGraoD3
index: nagioslogserver_log, type: ALERT, id: AZk1ztd5hNdxeYGraoD3, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk11ndVhNdxeYGrdsUZ
index: nagioslogserver_log, type: ALERT, id: AZk11ndVhNdxeYGrdsUZ, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2CeNlhNdxeYGrxFx2
index: nagioslogserver_log, type: JOBS, id: AZk2CeNlhNdxeYGrxFx2, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2C3y_hNdxeYGrxpTz
index: nagioslogserver_log, type: JOBS, id: AZk2C3y_hNdxeYGrxpTz, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2DBpIhNdxeYGrx2nO
index: nagioslogserver_log, type: JOBS, id: AZk2DBpIhNdxeYGrx2nO, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2ECadhNdxeYGrzVyn
index: nagioslogserver_log, type: JOBS, id: AZk2ECadhNdxeYGrzVyn, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2EHTmhNdxeYGrzcX-
index: nagioslogserver_log, type: JOBS, id: AZk2EHTmhNdxeYGrzcX-, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2ENNUhNdxeYGrzkIo
index: nagioslogserver_log, type: JOBS, id: AZk2ENNUhNdxeYGrzkIo, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2ESGjhNdxeYGrzq0s
index: nagioslogserver_log, type: JOBS, id: AZk2ESGjhNdxeYGrzq0s, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2Er5fhNdxeYGr0RVY
index: nagioslogserver_log, type: JOBS, id: AZk2Er5fhNdxeYGr0RVY, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2D4l3hNdxeYGrzHxk
index: nagioslogserver_log, type: ALERT, id: AZk2D4l3hNdxeYGrzHxk, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2FxT_hNdxeYGr16M5
index: nagioslogserver_log, type: JOBS, id: AZk2FxT_hNdxeYGr16M5, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2F7HBhNdxeYGr2HXg
index: nagioslogserver_log, type: JOBS, id: AZk2F7HBhNdxeYGr2HXg, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2GE7LhNdxeYGr2VVR
index: nagioslogserver_log, type: JOBS, id: AZk2GE7LhNdxeYGr2VVR, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2GedBhNdxeYGr26Pr
index: nagioslogserver_log, type: JOBS, id: AZk2GedBhNdxeYGr26Pr, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2GyEPhNdxeYGr3U-3
index: nagioslogserver_log, type: JOBS, id: AZk2GyEPhNdxeYGr3U-3, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2G2-fhNdxeYGr3c4y
index: nagioslogserver_log, type: JOBS, id: AZk2G2-fhNdxeYGr3c4y, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2E2zmhNdxeYGr0esw
index: nagioslogserver_log, type: ALERT, id: AZk2E2zmhNdxeYGr0esw, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2FVYLhNdxeYGr1RGd
index: nagioslogserver_log, type: ALERT, id: AZk2FVYLhNdxeYGr1RGd, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2F2NihNdxeYGr2Az9
index: nagioslogserver_log, type: ALERT, id: AZk2F2NihNdxeYGr2Az9, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2HAychNdxeYGr3sLm
index: nagioslogserver_log, type: JOBS, id: AZk2HAychNdxeYGr3sLm, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2HaUrhNdxeYGr4Ota
index: nagioslogserver_log, type: JOBS, id: AZk2HaUrhNdxeYGr4Ota, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2H0EUhNdxeYGr41Cb
index: nagioslogserver_log, type: JOBS, id: AZk2H0EUhNdxeYGr41Cb, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2H49lhNdxeYGr480f
index: nagioslogserver_log, type: JOBS, id: AZk2H49lhNdxeYGr480f, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2IMkUhNdxeYGr5Z1E
index: nagioslogserver_log, type: JOBS, id: AZk2IMkUhNdxeYGr5Z1E, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2I5sOhNdxeYGr6Xnn
index: nagioslogserver_log, type: JOBS, id: AZk2I5sOhNdxeYGr6Xnn, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2JEe7hNdxeYGr6oqr
index: nagioslogserver_log, type: JOBS, id: AZk2JEe7hNdxeYGr6oqr, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2JYGXhNdxeYGr7Jnr
index: nagioslogserver_log, type: JOBS, id: AZk2JYGXhNdxeYGr7Jnr, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2JJYVhNdxeYGr6yBU
index: nagioslogserver_log, type: ALERT, id: AZk2JJYVhNdxeYGr6yBU, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2LCRThNdxeYGr9eRk
index: nagioslogserver_log, type: JOBS, id: AZk2LCRThNdxeYGr9eRk, upsert: 1
Migrating index nagioslogserver_log hit type: ALERT id: AZk2LCSAhNdxeYGr9eRl
index: nagioslogserver_log, type: ALERT, id: AZk2LCSAhNdxeYGr9eRl, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2Jm0uhNdxeYGr7f3Y
index: nagioslogserver_log, type: JOBS, id: AZk2Jm0uhNdxeYGr7f3Y, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2JwnuhNdxeYGr7tzU
index: nagioslogserver_log, type: JOBS, id: AZk2JwnuhNdxeYGr7tzU, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2KoxDhNdxeYGr869a
index: nagioslogserver_log, type: JOBS, id: AZk2KoxDhNdxeYGr869a, upsert: 1
Migrating index nagioslogserver_log hit type: JOBS id: AZk2LMEshNdxeYGr9rsP
index: nagioslogserver_log, type: JOBS, id: AZeR-VWh6b5MlWqCTbcp, upsert: 1- jmichaelson
- Posts: 398
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagios Log Server - migration to 2026
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 0.0001 days which is approximately 8 and a half minutes. Then go to Admin->Audit Log and click trim audit log.
Please let us know if you have any other questions or concerns.
-Jason
-Jason
Re: Nagios Log Server - migration to 2026
I have set it to 30 days, and trimmed it to 30 days. Anything else I need to do, or should the operation finally finish automatically on the target server?
- jmichaelson
- Posts: 398
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagios Log Server - migration to 2026
As long as it keeps moving, it will eventually finish. If you get a PHP exception and it stops, please let us know!
Please let us know if you have any other questions or concerns.
-Jason
-Jason