Linux Agent - Error - Replication Driver Missing

Linux Agent - Error - Replication Driver Missing

If any policy fails in R1soft, then you need to click on the failed policy and check the field "Alerts". If you see error related to "hcpdriver module", like

============================

An exception occurred during the request. The replication driver was not detected (detail:

An error occurred while loading the hcpdriver module, please check your system logs;

Please run "r1soft-setup --get-module " on your Agent to install one. ).

============================

Then you need to make sure you have installed Kernel-devel & Kernel-headers on your "Agent Server".

Run (On clients server);

# lsmod | grep hcp

If it returns no value, then the hcpdriver not running on your client machine. After that you need perform below steps,

1. Check the current running Kernel

# uname -r

2. Check you installed correct Kernel-devel & Kernel-headers

# rpm -qa | grep kernel

3. If it's not showing correct Kernel packages, then you need to remove those packages and install correct one,

# yum install "kernel-devel-uname-r == $(uname -r)"

# yum install "kernel-headers-uname-r == $(uname -r)"

If you are using custom Kernel, then  you need to install it using RPM package.

4. Then you need install the required r1soft modules using below command

# r1soft-setup --get-module

# r1soft-setup --get-module --no-binary (Use after checking his use)

5. Then restart the R1soft Agent

# /etc/init.d/cdp-agent restart

6. Then you need to check the hcpdriver loaded,

[root@server log]#  lsmod | grep hcpdriver

hcpdriver              81014  4

If all went fine, then you will get a result like

============================

[root@server log]#  lsmod | grep hcpdriver

hcpdriver              81014  4

[root@server log]# ll /lib/modules/r1soft/

============================

Exception;

If you fail to get module loaded, then do below steps (I tried this for my openvz node)

*) Remove current loaded modules

# rm -f /lib/modules/r1soft/*

*) Load new modules using

# r1soft-setup --get-module --no-binary

OR

# r1soft-setup --get-module --no-binary --force

It will fix the policy error and the connection will fine after that.