Forums

Resolved
0 votes
Hello,

I'm trying to install the Datto Linux Agent in order to backup my server. ClearOS is not one of their officially supported operating systems, but CentOS is.

Because of the similarities between CentOS and ClearOS, I was able to install all of the dependencies listed in their KB article, and start their installation script. At first it failed because it couldn't find the kernel-devel dependency. The problem was that the script was checking for the existence of a package named "kernel-devel-2.6.32-696.18.7.v6.x86_64" when the ClearOS package is just called "kernel-devel". Looking at the yum info of the ClearOS package shows that it is the same version (2.6.32) as the package the script needs and a slightly newer release (696.20.1.v6), so I thought I might get by this by modifying the script.

I opened the installation script and commented out the code that checks for the kernel-devel dependency. I then ran my modified version, and the installation went smoothly until the end where I received two messages:

Loading new dattobd-0.10.4 DKMS files...
Building for 2.6.32-696.18.7.v6.x86_64
Module build for kernel 2.6.32-696.18.7.v6.x86_64 was skipped since the
kernel headers for this kernel does not seem to be installed.

and

iptables: unrecognized service
warning: %post(dlad-1.0.13-35.4.el6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package dlad-1.0.13-35.4.el6.x86_64

I'm assuming the second message about iptables is the package failing to open its own ports in the firewall. I can do that manually; not a big deal. The first message about DKMS is definitely a showstopper though. It's saying it cant find the kernel headers which should be included in kernel-devel. It probably can't find them for the same reason I had to modify the installer earlier.

I thinking I could probably resolve this with another bit of manual intervention, but this is where my Linux experience runs out. These message came from the post-installation scripts of those two packages "dlad" and "dattobd". Maybe I could modify the post installation scripts, but even if I knew how to do that I'm not sure if its a good idea. If I instead modified the name of the kernel-devel headers folder or created a soft link to the headers folder with the correct name would that work? So far I've been assuming that the release numbers are backwards compatible but I could be wrong.

I would greatly appreciate any help you could give me. I feel like this is very close to working.
Thank you.
In Backup
Wednesday, April 04 2018, 06:36 PM
Share this post:

Accepted Answer

Wednesday, April 04 2018, 09:13 PM - #Permalink
Resolved
0 votes
I've never used DKMS, but things which work in Centos should generally work in ClearOS.

First of all, can you bring your system up to date with a "yum update" then reboot. Once done, "uname -r" should return "2.6.32-696.20.1.v6.x86_64". Also if not installed, install kernel devel with:
yum install kernel-devel
It should install the matching kernel-devel package although I think their script looks after kernel-devel.

In their script I'd disable the section which installs the epel repo and, instead temporarily enable the clearos-epel repo but do not leave it enabled and do not do a yum update with it enabled.

Then run the script. if you still get a failure from the post-installation script, download the dlad rpm locally (possibly from https://cpkg.datto.com/datto-rpm/EnterpriseLinux/6.9/x86_64/dlad-1.0.13-35.4.el6.x86_64.rpm and have a look in the rpm for the scripts with a:
rpm -qp --scripts dlad...........rpm
Use the tab key to autocomplete the dlad rpm name.
The reply is currently minimized Show
Responses (3)
  • Accepted Answer

    M J S
    M J S
    Offline
    Tuesday, April 17 2018, 02:35 PM - #Permalink
    Resolved
    0 votes
    Glad to hear you were able to make it work. In most cases as long as the dependencies are met, it's not hard to get it to install.
    Probably isn't a bad idea to note, though, that even though backups are successful they probably will not offer much in the way of support for restores.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 05 2018, 07:26 AM - #Permalink
    Resolved
    0 votes
    It looks like all the post-installation is trying to do is add the following firewall rule:
    iptables -I INPUT 1 -p tcp --dport 25567 -j ACCEPT
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 05 2018, 05:56 AM - #Permalink
    Resolved
    0 votes
    Thank you Nick. I stupidly assumed that the packages were already up to date. All I needed was the yum update and reboot, and the vanilla installation worked correctly. It still gave me a warning about iptables, but the backup feature is fully functional so I'm not worried about it.
    The reply is currently minimized Show
Your Reply