AWS Elastic Disaster Recovery Agent Installation in VMs inside physical VMWare ESXI server not working due to VM kernel issues

Question

Hi! I've been having a hard time installing the AWS Elastic Disaster Recovery agent inside either an Ubuntu VM or Rocky Linux VM inside a physical VMWare ESXI host.

The error says that Error: Kernel headers are missing or not properly configured. Please install the appropriate kernel headers.
Installation failed.

I checked all the kernel versions and it's all a match. However, I don't understand why it still won't push through even though the kernel version and compatibility is correct.

I can paste here the error logs but it's too long.

Jared · Answer

Hello

I am experiencing the same error with the agent after updating the kernel. 
The `aws-replication-driver-update` systemd service first failed, then I tried uninstalling the agent and reinstalling

Rocky Linux 9.5
Kernel 5.14.0-503.15.1.el9_5.x86_64

```
--- Building software
running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', '/bin/sh configure --with-srcdir=/lib/modules/5.14.0-503.15.1.el9_5.x86_64/build']
retcode: 0
running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', 'make clean'] with environment set to {'SRCDIR': '/lib/modules/5.14.0-503.15.1.el9_5.x86_64/build', 'PWD': '/tmp/tmp_4f8ixqr/AgentDriver'}
retcode: 0
running: 'which zypper'
retcode: 256
running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', 'make'] with environment set to {'SRCDIR': '/lib/modules/5.14.0-503.15.1.el9_5.x86_64/build', 'PWD': '/tmp/tmp_4f8ixqr/AgentDriver'}
retcode: 2
Unexpected error while making agent driver! Are kernel linux headers installed correctly?
StdOut from driver make second run: make -C /lib/modules/5.14.0-503.15.1.el9_5.x86_64/build M=/tmp/tmp_4f8ixqr/AgentDriver modules
make[1]: Entering directory '/usr/src/kernels/5.14.0-503.15.1.el9_5.x86_64'
  CC [M]  /tmp/tmp_4f8ixqr/AgentDriver/src/linux/KernelTracer.o
make[1]: Leaving directory '/usr/src/kernels/5.14.0-503.15.1.el9_5.x86_64'
```

kairu97 · Answer

This is the error logs.

--- Building software running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', '/bin/sh configure --with-srcdir=/lib/modules/4.18.0-553.27.1.el8_10.x86_64/build'] retcode: 0 running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', 'make clean'] with environment set to {'SRCDIR': '/lib/modules/4.18.0-553.27.1.el8_10.x86_64/build', 'PWD': '/tmp/tmp12qb8jax/AgentDriver'} retcode: 0 running: 'which zypper' retcode: 256 running: ['/usr/bin/scl', 'enable', 'gcc-toolset-14', 'make'] with environment set to {'SRCDIR': '/lib/modules/4.18.0-553.27.1.el8_10.x86_64/build', 'PWD': '/tmp/tmp12qb8jax/AgentDriver'} retcode: 0 running: 'chmod 0770 ./aws-replication-driver-commander' retcode: 0 running: 'chcon -t modules_object_t ./aws-replication-driver.ko' retcode: 0 running: '/tmp/tmp12qb8jax/AgentDriver/removeDriver.sh /dev/aws_replication' retcode: 0 running: '/sbin/insmod ./aws-replication-driver.ko' retcode: 256 running: '/tmp/tmp12qb8jax/AgentDriver/removeDriver.sh /dev/aws_replication' retcode: 0 Cannot insert aws-replication-driver Installation returned with code <InstallerStatus.NO_HEADERS_WITH_SYMLINK: 2>

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "dirrus/installer_shared/installer_main.py", line 1446, in _main File "dirrus/installer_shared/installer_main.py", line 1222, in install_agent File "dirrus/installer_shared/installer_main.py", line 974, in install File "dirrus/installer_shared/installer_main.py", line 404, in run_agent_installer File "dirrus/installer_shared/installer_main.py", line 338, in run_agent_installer_command_linux File "dirrus/installer_shared/installer_main.py", line 235, in handle_install_agent_error shared.installer_utils.cloud_utils.Error: Kernel headers are missing or not properly configured. Please install the appropriate kernel headers. [installation_id: 3f208d4b-2784-4eb6-aa96-33118aeea463, agent_version: 6.39.0.2024.294.1550, google_instance_id: <!doctype html public "-//w3c//dtd xhtml 1-0 transitional//en" "http://www-w3-org/tr/xhtml1/dtd/xhtml1-transitional-dtd">

<html xmlns="http://www-w3-org/1999/xhtml"> <head> <meta content="text/html; charset=utf-8" http-equiv="content-type" /> <meta content="no-cache" http-equiv="pragma" /> <title>waiting---</title> <script type="text/javascript"> var pagename = '/'; top-location-replace(pagename); </script> </head> <body></body> </html> , mac_addresses: 52234803952,90520741659819, _origin_client_type: installer]

Jared · Answer

Just a heads up

AWS support has indicated that EDR agent is not compatible yet with Rocky 9.5 , this should probably be mentioned on their docs as they say Rocky 9 , not Rocky 9.4 is supported

To me it feels like more of a kernel(and or headers/source) version thing given that the OP had problems on Ubuntu

Hopefully google index this to help other people looking for answers

J

dnelson · Answer

I had opened a ticket on the EL9.5 kernel issue at the end of November, and their estimated time for a fix is "Q1 2025", which could be as far away as March.  A workaround is to boot the last available EL9.4 kernel ( kernel-5.14.0-427.42.1.el9_4 ), but then you're vulnerable to any kernel bugs in that version that have been fixed in later ones.

AWS Elastic Disaster Recovery Agent Installation in VMs inside physical VMWare ESXI server not working due to VM kernel issues

Add your answer

Relevant content