Troubleshoot Live Migration (Pull)
Before the live migration (pull) process begins, Atlas performs a validation check to ensure that all the necessary form fields and parameters are functional and correct. If any parameters are invalid, Atlas returns an error and live migration does not proceed.
This section describes common live migration (pull) validation errors and provides suggestions for what to check if you encounter them.
Common Live Migration (Pull) Validation Errors
Could not reach specified source
Could not resolve hostname
No IP address was found for the given hostname. Confirm that the given hostname is correct and publicly accessible.
Invalid SSL options provided
If you are using SSL:
If you aren't using SSL:
The username or password is not correct
User not authorized to execute command
To run the live migration (pull) process, the MongoDB user must have sufficient system privileges. To learn more, see Source Cluster Security.
Disk storage info unavailable
To run the live migration (pull) process, the MongoDB user must have permissions on the source cluster's MongoBD instance. To learn more, see Source Cluster Security.
Source disk usage is too large for destination
Different Atlas service tiers have different amounts of disk space available. Ensure that your Atlas cluster has enough disk space for all the data on your source cluster. To learn more about cluster sizings, see Create a New Cluster.
Source appears to be a standalone
Your source deployment must be a MongoDB replica set. If your source deployment is currently a standalone node, convert it to a single-node replica set before running live migration (pull).
Unable to process the provided CA file
Confirm that your CA file is complete and correctly pasted into the live migration (pull) modal window.
Common Post-Validation Errors
Could not retrieve the latest oplog entry from the source: not found
Could not determine if --host is a replica set: error connecting to db server: no reachable servers
Error applying oplog entries during initial sync: renameCollection command encountered during initial sync. Please restart
Renaming a collection on the source cluster during live migration (pull) may trigger this error.
Unsupported index error
Certain types and configurations of indexes which were allowable in earlier versions of MongoDB are no longer supported in more recent versions. Check the release notes for the MongoDB version on your destination cluster for possible conflicts. If necessary, drop any indexes which cause errors and rebuild them after the live migration process is complete.
Error while tailing the oplog on the source: Checkpoint not available in oplog
Live migration (pull) uses the source oplog to sync operations which occur on the source cluster during the pull live migration procedure. If the source cluster oplog size is too small, it might not be able to record all the operations that occur on the source cluster during the sync, and live migration (pull) falls too far behind to catch up.
If you see this error: