Linux addiktz

An exception occurred during the request. Replication driver missing; Unable to open driver at ‘/dev/hcp’; No such device or address.

This error indicates that the CDP Agent kernel driver is not installed for the running kernel on the agent’s Operating System. This can happen when the agent OS is rebooted into a new kernel after running an upgrade (usually apt or yum). Or this can occur if you have not installed a CDP Agent kernel driver after the initial install of the CDP Agent.

Resolution

Each time a new kernel is installed on a Linux CDP Agent or upon the first time installing the CDP Agent, you must ensure that you have a CDP Agent kernel driver for your current running kernel. You can install a kernel module for the agent by using the r1soft-setup utility, after ensuring that you have the kernel devel and kernel headers in the Linux OS that match your current running kernel.

Note Please refer to your Linux distribution documentation for more information about kernel devel and kernel headers http://wiki.r1soft.com/display/CDP3/r1soft-setup

You can install a kernel module for your running agent by using the ‘r1soft-setup’ utility, after ensuring that you have the kernel-devel (Redhat/CentOS) or kernel-headers (Debian/Ubuntu) package installed for your current running kernel. There are 3 common types of Redhat based kernel-devel packages that contain the kernel header and source files needed. (kernel-devel, kernel-xen-devel, kernel-PAE-devel) You must match the proper package to your running kernel type.

To find the current running kernel run:

To find what kernel and kernel-devel packages you have installed on a Redhat based system you can use an RPM query like this: (note: the kernel and kernel-devel package versions must match exactly in order to build the correct CDP Agent kernel driver module)

To force a custom build using your kernel headers and source files:

After you have successfully acquired a CDP Agent kernel driver you will need to restart the agent to load the module:

Then you can check that the module is loaded properly with the lsmod command in Linux. http://linux.die.net/man/8/lsmod

Additional information about the kernel module is located at directory listed below.

Note Note that the hcpdriver.o file has a symbolic link to the real kernel driver file. This symbolic link allows CDP to call the file without needing to know the name of the real kernel driver file. +Example:+ls -l /lib/modules/r1soft total 112 1 root root 114618 2011-09-26 12:58 hcpdriver-cki-2.6.38-11-server.ko 1 root root 53 2011-10-10 10:32 hcpdriver.o -> /lib/modules/r1soft/hcpdriver-cki-2.6.38-11-server.ko

You can obtain additional information about the kernel modules such as the version that the module is built for by using the modinfo command in Linux.
http://linux.die.net/man/8/modinfo