- Published on
Troubleshooting Nagios Log Server Migration Issues
- Last Updated October 27, 2026
If your Nagios Log Server migration isn’t completing as expected, this guide will help you find the cause using migration logs, command-line tools, and example output.
Due to architectural changes introduced in Nagios Log Server 2024R2, an in-place upgrade from 2024R1.x is not supported. Instead, deploy a new Nagios Log Server 2026R2 Cluster and migrate data using the included migration utility.
During this migration, you may run into issues you can resolve on your own before contacting Nagios Support. This article covers how to review migration logs, run the migration manually, and identify common errors.
For migration instructions, see the Migrating to Nagios Log Server 2026 document.
Verify Versions
Before troubleshooting, confirm that you have used supported versions for the source and destination clusters:
- Source Cluster: Nagios Log Server 2024R1.3.8
- Destination Cluster: At least Nagios Log Server 2026R2
Common Migration Issues
Many issues can be resolved based on the log output, without the need to contact Nagios Support. For example, if you see that the logs show connectivity issues, it could be related to network connectivity problems.
Here is a list of common migration issues:
- Network connectivity problems
- Authentication failures
- OpenSearch indexing errors
- Data mapping conflicts
- Permission issues
- Dashboard or settings migration failures
Review Migration Logs
On the target instance, you can grep the logs to find all the messages generated by the migration, to isolate issues:
RHEL-Based Systems
cat /var/log/messages | grep "Nagios Log Server Migration"Debian-Based Systems
cat /var/log/syslog | grep "Nagios Log Server Migration"Run the Migration From the Command Line
Another option is to run the migration from the command line which gives you more flexibility and control, and shows actual errors on the console. You can isolate a specific index, migrate only the log data, or restart the previous migration. Run the following migration script from the command line on the target instance:
php /usr/local/nagioslogserver/scripts/migrate_data.php -s <source_ip>Example:
php /usr/local/nagioslogserver/scripts/migrate_data.php -s 192.168.55.101 -i logstash-2026.07.30 -rThis command will migrate the index named logstash-2026.07.30 and restart the previous migration using 192.168.55.101 as the source instance.
Common Parameters:
-s <source_ip>The IP address of the source cluster. This is required.-i <index_name>Migrates the specified index.-lMigrates log data.-rRestarts previous migration.
Reading Migration Outputs
The following examples show what to look for in the log files or on the console, if performed manually.
Failed Migration Example
{
"failures": [
{
"cause": {
"type": "mapper_parsing_exception",
"reason": "object mapping conflict"
},
"status": 400
}
]
}A mapper_parsing_exception indicates a data mapping conflict during migration. If you see this, please open a Support Case.
Successful Migration Example
{
"created": 1,
"version_conflicts": 0,
"failures": []
}An empty failures array indicates the migration completed without errors.
Before Opening a Support Case
If you still need help, collect the following and upload them to your Support Case:
- Source and destination Log Server versions
- Migration log output
- Any output from the migration script
- Screenshots of reported errors
- Full diagnostic profiles of both instances
Conclusion
Migrating to the latest Nagios Log Server version is a significant step. If you worked through these troubleshooting steps and still see errors, open a Support Case and include the items listed above so our team can review your migration as quickly as possible.
