AWS drs documentation change
Summary
Restructured troubleshooting guide from detailed error explanations to a link-based table of contents pointing to dedicated documentation pages for agent installation issues.
Security assessment
The changes reorganize existing content without introducing new security information. While some removed sections mentioned security features (SELinux, Secure Boot, BitLocker), these were existing explanations, not new security documentation. The restructuring doesn't address any specific vulnerability or weakness.
Diff
diff --git a/drs/latest/userguide/troubleshooting-agent-issues.md b/drs/latest/userguide/troubleshooting-agent-issues.md index fba001d21..c575bddce 100644 --- a//drs/latest/userguide/troubleshooting-agent-issues.md +++ b//drs/latest/userguide/troubleshooting-agent-issues.md @@ -7,12 +7 @@ -Agent log locations and statusError: Installation FailedThis app can't run on your PC error – WindowsIs having a mounted '/tmp' directory a requirement for the Agent?Installation Failed – Old AgentInstallation Failed on Linux ServerInstallation Failed on Windows MachineWindows – Installation Failed - Request SignatureError – driver was compiled for a different kernel not loadingError: insmod permission denied or operation not permittedError: Failed to set system user permissionsError: failed to map segment from shared objectMultipath configuration issuesWindows: Cannot open self or archiveWindows: TLS connection error when downloading installerWindows: The directory is not emptyError – certificate verify failedError: Account not initializedError: Failed to validate AWS credentialsError: Missing agent installation policyError: Agent IAM role missingError: Account Region mismatchError: Reboot required after uninstallationError: Unsupported Linux kernel versionError: gcc not foundError: Oracle ASM Filter Driver detectedError: BitLocker is not supportedError: Volume too largeError: Source server already existsError: Missing marketplace license permissions - -# Troubleshooting Agent Issues - -###### Note - -To gather detailed system information for troubleshooting agent installation, replication, or launch issues, use the following tools and attach the output to your support case: - - * **Linux:** [MGN-DRS Linux System Details Tool](https://github.com/awslabs/mgn-drs-linux-system-details-tool) - - * **Windows:** [MGN Toolkit for Windows](https://github.com/awslabs/aws-support-tools/tree/master/MGN/Windows) - +# Troubleshooting agent installation @@ -19,0 +9 @@ To gather detailed system information for troubleshooting agent installation, re +Use this section to troubleshoot issues with installing or running the AWS Replication Agent on your source servers. @@ -20,0 +11,7 @@ To gather detailed system information for troubleshooting agent installation, re +If you need to... | See +---|--- +Check agent status, view logs, or gather diagnostics for a support case | [Agent logs and diagnostics](./agent-diagnostics.html) +Verify your server meets requirements before installing | [Installation prerequisites](./agent-install-prerequisites.html) +Fix errors during installation on Linux (kernel headers, SELinux, permissions, disk issues) | [Linux installation errors](./agent-install-linux-errors.html) +Fix errors during installation on Windows (TLS, BitLocker, PATH, signature issues) | [Windows installation errors](./agent-install-windows-errors.html) +Fix credential, IAM, or account configuration errors (any platform) | [Common installation errors](./agent-install-common-errors.html) @@ -24,570 +21 @@ To gather detailed system information for troubleshooting agent installation, re - * Agent log locations and status - - * Error: Installation Failed - - * This app can't run on your PC error – Windows - - * Is having a mounted '/tmp' directory a requirement for the Agent? - - * Installation Failed – Old Agent - - * Installation Failed on Linux Server - - * Installation Failed on Windows Machine - - * Windows – Installation Failed - Request Signature - - * Error – driver was compiled for a different kernel not loading - - * Error: insmod permission denied or operation not permitted - - * Error: Failed to set system user permissions - - * Error: failed to map segment from shared object - - * Multipath configuration issues - - * Windows: Cannot open self or archive - - * Windows: TLS connection error when downloading installer - - * Windows: The directory is not empty - - * Error – certificate verify failed - - * Error: Account not initialized - - * Error: Failed to validate AWS credentials - - * Error: Missing agent installation policy - - * Error: Agent IAM role missing - - * Error: Account Region mismatch - - * Error: Reboot required after uninstallation - - * Error: Unsupported Linux kernel version - - * Error: gcc not found - - * Error: Oracle ASM Filter Driver detected - - * Error: BitLocker is not supported - - * Error: Volume too large - - * Error: Source server already exists - - * Error: Missing marketplace license permissions - - - - -## Agent log locations and status - -Use the following to check the agent status and view log files: - -Linux - - -Check agent service status: - - - sudo systemctl status aws-replication-agent - -View agent logs: - - - tail -200 /var/lib/aws-replication-agent/agent.log.0 - -Search for errors in agent logs: - - - grep -i "error\|fail\|exception" /var/lib/aws-replication-agent/agent.log.0 | tail -50 - -Windows - - -Check agent service status (PowerShell): - - - Get-Service -Name AwsReplicationService - -View agent logs (PowerShell): - - - Get-Content "C:\Program Files (x86)\AWS Replication Agent\agent.log.0" -Tail 200 - -Search for errors in agent logs (PowerShell): - - - Select-String -Path "C:\Program Files (x86)\AWS Replication Agent\agent.log.0" -Pattern "error|fail|exception" -CaseSensitive:$false | Select-Object -Last 50 - -## Error: Installation Failed - -When the installation of the AWS Replication Agent on a source server fails during the running of the Installer file, you will receive an error message. - -This type of error means that the Agent was not installed on the source server, and therefore the server will not appear on the AWS Elastic Disaster Recovery Console. After you fix the issue that caused the installation to fail, you need to rerun the Agent Installer file to install the Agent. - -## This app can't run on your PC error – Windows - -If you encounter the following error "This app can't run on your PC", when trying to install the AWS Replication Agent on your Windows 10 source machine, try the following. - -This error is indicative that your particular version of Windows 10 is likely the 32-bit version. To verify this, you can - -1\. Use the Windows key + I keyboard shortcut to open the Settings app. - -2\. Click System. - -3\. Click About. - -4\. Under System type, you will see two pieces of information: if it says 32-bit operating system, x64-based processor, then it means that your PC is running a 32-bit version of Windows 10 on a 64-bit processor. - -If it says 32-bit operating system, x86-based processor, then your computer doesn't support Windows 10 (64-bit). - -At the moment, only 64 bit operating systems are supported for Elastic Disaster Recovery Service. - -If your OS is indeed 64-bit, then there may be other elements blocking the installation of your agent. The block is actually coming from the Windows Operating System itself. You would need to identify what the cause is, (for example, broken registry key), - -## Is having a mounted '/tmp' directory a requirement for the Agent? - -The simple requirement is just to have enough free space. There is no need for this to be a separate mount. The need for the '/tmp' requirement is actually only if '/tmp' is a separate mount. If '/tmp' is not a separate mount, then it would fall under '/', for which we have the 2 GiB free requirement. This allows for the '/tmp' to fall into this requirement. - -## Installation Failed – Old Agent - -Installation may fail due to an old AWS Replication Agent. Ensure that you are attempting to install the latest version of the AWS Replication Agent. You can learn how to download the Agent [here](./adding-servers.html). - -## Installation Failed on Linux Server - -If the installation failed on a Linux source server, check the following: - - 1. **Free Disk Space** - -Free disk space on the root directory – verify that you have at least 3 GB of free disk on the root directory (/) of your Source machine. To check the available disk space on the root directory, run the following command: `df -h /` - -Free disk space on the /tmp directory – for the duration of the installation process only, verify that you have at least 500 MB of free disk on the /tmp directory. To check the available disk space on the /tmp directory run the following command: df -h /tmp - -After you have entered the above commands for checking the available disk space, the results will be displayed as follows: - - - - 2. **The format of the list of disks to replicate** - -During the installation, when you are asked to enter the disks you want to replicate, do NOT use apostrophes, brackets, or disk paths that do not exist. Type only existing disk paths, and separate them with a comma, as follows: - -/dev/xvdal,/dev/xvda2. - - 3. **Version of the Kernel headers package** - -Verify that you have kernel-devel/linux-headers installed that are exactly of the same version as the kernel you are running. - -The version number of the kernel headers should be completely identical to the version number of the kernel. To handle this issue, follow these steps: - - 1. **Identify the version of your running kernel.** - -To identify the version of your running kernel, run the following command: - -`uname -r` - - -