Linux Agent Help required - CentOS 5

Hi,

Sorry for the long post I have ATI Echo Enterprise and I'm practising with getting the linux agent installed onto a virtual pc running CentOS 5 before installing onto a 2TB file server. Now I think the main problem is probably my inexperience with troubleshooting Linux but here's what I've done so far:

Fresh install of CentOS 5.1 final

#/home/AcronisTrueImageAgentLinuxEnterprise.i686.rpm - fails no snapapi

I emailed tech support & was supplied a new snapapi so I found the command to get it installed.

#rpm -Uvh snapapi26_modules-0.7.30-1.noarch.rpm

Preparing... ########################################### [100%]
1:snapapi26_modules ########################################### [100%]
ERROR: Module snapapi26 does not exist in /proc/modules
ERROR: Module snumbd26 does not exist in /proc/modules

------------------------------
Deleting module version: 0.7.29
completely from the DKMS tree.
------------------------------
Done.

This appears to be an error but running it again says it's already installed

#rpm -Uvh /home/snapapi26_modules-0.7.30-1.noarch.rpm
Preparing... ########################################### [100%]
package snapapi26_modules-0.7.30-1 is already installed

After installing the snapapi I was told to do this

dkms ldtarball --archive=/usr/lib/Acronis/kernel_modules/snapapi26-0.7.30-all.tar.gz

which seems to work ok

Warning! This tarball was created with dkms < 2.0 and contains
no arch info. DKMS will assume the arch: i686

Loading tarball for module: snapapi26 / version: 0.7.30

Loading /usr/src/snapapi26-0.7.30...
Creating /var/lib/dkms/snapapi26/0.7.30/source symlink...

DKMS: ldtarball Completed.

At this point I need to build the dkms so a few things needed like source files and a config file

#yum install rpm-build
#yum install redhat-rpm-config
#yum install gcc

#adduser fredb
#passwd fredb

*switch to a new ssh session as user fredb
#cd
#mkdir -p rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
#echo "%_topdir %(echo $HOME)/rpmbuild" > .rpmmacros
#rpm -i http://mirror.centos.org/centos/5/updates/SRPMS/kernel-2.6.18-53.1.14.el5.src.rpm
#cd ~/rpmbuild/SPECS
#rpmbuild -bp --target=`uname -m` kernel-2.6.spec

Now I can issue the command to build the module

#dkms build -m snapapi26 -v 0.7.30 -k 2.6.18-53.el5 --config /boot/config-2.6.18-53.el5 --arch i686 --kernelsourcedir /home/fredb/rpmbuild/BUILD/kernel-2.6.18

Error! DKMS tree does not contain: snapapi26-0.7.30
Build cannot continue without the proper tree.

But I get this error and this is as far as I've got so far, anybody got any ideas whats wrong?

Thanks,

Dave.

 

bump.

Anyone got any ideas?

 

Hello FireBIade,

Thank you for choosing Acronis Remote Server Backup Software.

We are sorry for delayed response.

Could you please let us know your Acronis request number (e.g. [Acronis #123456]) which was sent to you in autoreply to your letter? We will find out how the investigation of your issue is going. If you have not received an autoreply then please send us a Private Message containing your e-mail address.

Thank you.
--
Marat Setdikov

 

Hi,

this is my first time on the Acronis forums but having a similar problem.

Have successfully installed the Acronis True Image Agent on two CentOS 5 machines after installing the usual gcc, glibc-devel, kernel-sources, etc. They were running Kernel 2.6.9-55.0.6.ELsmp.
But on another CentOS 5 running kernel 2.6.18-53.1.13.el5 I cannot get it to setup!
Always fails on the snapapi compiling.

How should I fix this do you think? Am I best to just update the Server to a new kernel or is there an alternative snapapi file I could use as was used above?

Please could someone guide me in the right direction with this because as I said, I'm new to Acronis.

Thanks
Russ

 

Hello russgalleywood,

Thank you for choosing Acronis Remote Server Backup Software.

We are sorry for delayed response.

Please make sure you use the latest build of the respective version of Acronis True Image. To get access to updates you should first register your software.

If the latest build doesn't solve the problem, please try compiling the necessary modules manually. Please install the sources of your running kernel, find appropriate kernel config file and install all packages required for kernel building packages (like gcc, glibc-devel, etc.). You should be prompted about the necessary packages during kernel sources installation.

Usually the snapapi kernel module should be built and installed with the "dkms" command. It can be performed with the following commands:

# dkms build -m <MODULE_NAME> -v <MODULE_VERSION> \
-k <KERNEL_VERSRION> --config <CONFIG_FILE> --arch <KERNEL_ARCH> \
--kernelsourcedir <PATH_TO_KERNEL_SOURCES>

# dkms install -m <MODULE_NAME> -v <MODULE_VERSION> \
-k <KERNEL_VERSRION> --config <CONFIG_FILE> --arch <KERNEL_ARCH> \
--kernelsourcedir <PATH_TO_KERNEL_SOURCES>

<MODULE_NAME> must be "snapapi" for 2.4.x kernels or "snapapi26" for 2.6.x kernels.

<KERNEL_VERSION> is the version of your running kernel. You can find it using

# uname -r

command.

<MODULE_VERSION> can be detected by

# ls /usr/src/snapapi*

<CONFIG_FILE> is your kernel config filename. Usually this file can be found in the /boot directory.

<KERNEL_ARCH> can be detected by

# rpm -q --queryformat "%{ARCH}\n" kernel

for RPM based distributions or by

# uname -m

for non-RPM based distributions.

For details please refer to dkms man page (man dkms).

After successful module building and installation you may try launching trueimage or trueimagecmd (see "man trueimagecmd") utilities or connect to the Linux agent from management console and check the functionality of the software. Respective kernel modules will be loaded automatically.

If the issue persists, please collect some information to let us investigate it thoroughly:

Please download the Linux System Report utility available here and do the following to create the report:

- Unpack the archive: # tar xvf sysinfo.tar

- Make the script executable: # chmod +x sysinfo

- Run the executable: # ./sysinfo

Then submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will do our best to investigate the problem and provide you with a solution.

Thank you.
--
Marat Setdikov