Agent logs and diagnostics
When troubleshooting Elastic Disaster Recovery agent issues, start by checking the service status and reviewing recent log entries. This page provides commands for checking agent health and gathering diagnostic information for support cases.
Check agent status and logs
Use the following commands to verify that the replication agent is running and to review recent log output.
Common log patterns
Look for the following patterns in agent logs to identify the root cause of issues.
-
FATAL or ERROR entries — Indicate agent failures that require immediate attention.
-
Connection refused — Indicates a network connectivity issue. Verify that the source server can reach the AWS replication endpoints.
-
Certificate errors — Indicates TLS or certificate trust issues. Verify that the source server trusts the AWS root certificates.
-
Timeout — Indicates a firewall blocking traffic or an unreachable endpoint. Check security group rules and network ACLs.
Gather diagnostic information for support
Use the following tools to collect system details before opening a support case.
Include the following information in your support case:
-
Agent log files (
agent.log.0) -
Diagnostic tool output
-
Operating system version
-
Agent version