RHEL 8 Agent Install Fails with 'failed to setup a network impact (os error 2)'

Modified on Tue, 21 May at 1:56 PM

If installing the Gremlin agent on RHEL 8 fails, check the logs located at

/var/log/gremlin/daemon.log

The following error messages indicate that required dependencies are not installed correctly:

Validating host Latency
Attack failed:
stdout: Setting up latency gremlin with guid 'validation-guid' for 1 second
eth0: Setting up network impact
Creating network impact: Latency (10ms)
setup failed: network: failed to setup up a network impact:  make sure there are no other attacks running and try again
Error reverting impact: network: failed to tell kernel to teardown: it may have been torn down already, check if any other attacks are active: No such file or directory (os error 2).
Please run `gremlin rollback`.
Gremlin attack terminated with an error: GREMLIN: network: failed to setup up a network impact:  make sure there are no other attacks running and try again: No such file or directory (os error 2)

stderr: GREMLIN: network: failed to setup up a network impact:  make sure there are no other attacks running and try again: No such file or directory (os error 2)

You can run the following commands in order to install the missing dependencies:

sudo yum install -y iproute-tc
sudo yum install -y kernel-modules-extra

Then, restart the gremlind service via systemctl:

systemctl stop gremlind.service
systemctl start  gremlind.service