Events Service Data Restore Fails with a 500 Error
During the data migration of Events Service, the Elasticsearch restore fails with a 500 error.
-
Check the
{HOME}/migration-tool/SERVICE-MIGRATION-STATUS.txtfile to verify the Events Service data migration status.CODEMigration Status - Updated: 2025-12-09 13:24:55 ==================================================== EUM | Status: running SYNTH | Status: running CONTROLLER | Status: saturated EVENTS | Status: failed ==================================================== -
If the Events Service data migration status is
failed, in some logs, you may observe the following pattern:PYTHONconfig_manager - restore_worker - ERROR - Elasticsearch-migration-restore-worker: Restore submit failed: ApiError(500, 'repository_exception', '[appdynamics-analytics-backup] Could not determine repository generation from root blobs', /mnt/nfs_events/index-N: Operation not permitted)Example log:PYTHONconfig_manager - restore_worker - ERROR - Elasticsearch-migration-restore-worker: Restore submit failed: ApiError(500, 'repository_exception', '[appdynamics-analytics-backup] Could not determine repository generation from root blobs', /mnt/nfs_events/index-4: Operation not permitted)
This 500 error occurs while restoring the Elasticsearch indices because of some transient errors like network or storage errors.
Increase the the retry and failure thresholds in the migration tool's configuration file.