Error with Acronis installation : precompiled snapapi module not found
Reber, Simon
simon.reber at roche.com
Fri Apr 17 12:53:04 UTC 2009
Do you have the kernel source (rpm kernel-devel) available in /usr/src and linked from /lib/modules/`uname -r`/build to /usr/src/kernel?
>-----Original Message-----
>From: redhat-list-bounces at redhat.com
>[mailto:redhat-list-bounces at redhat.com] On Behalf Of sunhux G
>Sent: Friday, April 17, 2009 2:48 PM
>To: General Red Hat Linux discussion list
>Subject: Error with Acronis installation : precompiled snapapi
>module not found
>
>Hi,
>
>Anyone has installed Acronis True Image Echo Enterprise agent on
>Linux.
>
>I got the following error after running its *.i686 install file :
>
> ââââââââââââââââââââââââââââ⤠Message
>ââââââââââââââââââââââââââââââ
> â
> â
> â Acronis True Image Echo Enterprise Server has not
>found â
> â precompiled snapapi module for running kernel. It is
> â
> â suggested to compile it now.
> â
> â
> â
> â You may choose "Skip" and compile snapapi module
>later. Please â
> â read readme.txt and HOWTO.INSTALL for compile
>instructions. â
> â
> â
> â ââââââââââââ ââââââââ
> â
> â â Continue â â Skip â
> â
> â ââââââââââââ ââââââââ
> â
> â
> â
> â
> â
>
>ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
>Here's a list of RPMs listed at the time I hit above error and
>I pause at
>above screen and pending a solution, will not proceed :
>
># rpm -qa | grep -i gcc-
>compat-libgcc-296-2.96-132.7.2
>gcc-g77-3.4.6-9
>libgcc-3.4.6-9
>gcc-c++-3.4.6-9
>gcc-objc-3.4.6-9
>gcc-java-3.4.6-9
>gcc-3.4.6-9
>
># rpm -qa | grep -i glibc-
>glibc-devel-2.3.4-2.39
>acronis-glibc-1.0-0
>glibc-common-2.3.4-2.39
>glibc-headers-2.3.4-2.39
>glibc-2.3.4-2.39
>glibc-kernheaders-2.4-9.1.100.EL
>
># rpm -qa | grep -i libgomp-
>libgomp-4.1.2-14.EL4
>
>What should I do next?
>Nothing much in readme.txt but I'm sorry to append below the lengthy
>HOWTO.INSTALL file :
>
>===============================================
>
>Table of content
>Introduction
>I. Common procedure to build and install kernel module
>. . . . .
>VIII. Installing on RedHat 8.0
>IX. Installing on TurboLinux 8.0
>X .FAQ:
>. . . . .
>Introduction
>Sometimes Acronis True Image Echo Enterprise Server setup
>can not compile the necessary kernel modules or prepare
>required execution environment for "trueimage" and
>"trueimagecmd" utilities. Usually it prompts you about such
>problem and refers you to this file.
>Section I describes common "how to build and install module"
>procedure. Most offten you will have to read it if you have
>custom kernel or non-stantard kernel sources location.
>Sections II,III and others provide necessary information for
>specific distributions.
>Please note that Redhat 9.0, Fedora Core 1, 2, 3, 4, 5, 6, 7,
>Redhat Advanced Server 3.0, 4.0, 5.0,SuSE 8.2, 9.0, 9.1, 9.2,
>9.3, 10.1, 10.2, Mandrake 10, Slackware 10, 11, ASPLinux 9.2,
>ASPLinux 10, ASPLinux Server II and Gentoo with stock kernels
>do not have problems with Acronis True Image Echo Linux
>Server and are not mentioned below.
>I. Building and installing kernel module in general case
>If the setup cannot compile the necessary kernel module you
>will have to do it manually. Please install kernel sources,
>apropriate config file and all required for kernel build
>packages (like gcc, glibc-devel, etc). You will be prompted
>about necessary packages while kernel sources install.
>Most often the snapapi kernel module should be built and
>installed by "dkms" command. It may be done by the following
>commands:
># dkms build -m <MODULE_NAME> -v <MODULE_VERSION> \
> --config <CONFIG_FILE> --arch <KERNEL_ARCH> \
> --kernelsourcedir <PATH_TO_KERNEL_SOURCES>
># dkms install -m <MODULE_NAME> -v <MODULE_VERSION> \
> --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.
><MODULE_VERSION> could be detected by
># ls /usr/src/snapapi*
><CONFIG_FILE> is your kernel config filename. Usually this
>file may be found in /boot directory.
><KERNEL_ARCH> may be detected by
># rpm -q --queryformat "%{ARCH}\n" kernel
>for RPM based distrubutions or by
># uname -m
>for non-RPM based distributions.
>For details please refer to dkms man page.
>After succesful module build and install you may try to
>launch "trueimage" or "trueimagecmd" utilities and check
>their functionality. Appropriate kernel modules will be
>loaded automatically.
>II. Installing on Mandrake 9.2 with kernel 2.4.X
>1. Please install kernel sources and prepare kernel to build
>by:
># make -C /usr/src/linux-2.4.22-37mdk/ mrproper
># cp /boot/config-2.4.22-37mdksmp /usr/src/linux-2.4.22-37mdk/.config
># make -C /usr/src/linux-2.4.22-37mdk/ oldconfig
># make -C /usr/src/linux-2.4.22-37mdk/ dep
>2. Please build and install snapapi module by the following
>commands:
># dkms build -m snapapi -v 0.6.4 -k 2.4.22-37mdksmp --arch i686 \
> --config /boot/config-2.4.22-37mdksmp --kernelsourcedir \
> /usr/src/linux-2.4.22-37mdk/ --no-prepare-kernel
># dkms install -m snapapi -v 0.6.4 -k 2.4.22-37mdksmp \
> --arch i686
>It is supposed that you have kernel 2.4.22-37mdksmp, kernel
>architecture is i686 and module version is 0.6.4.
>2. Activate devfs support by commands:
># mkdir /devfs
># mount -t devfs devfs /devfs
>3. Make devfs support permanent by adding
>"devfs /devfs devfs defaults 0 0" to your /etc/fstab file.
>III. Installing on Mandrake 10 with kernel 2.6.3-4mdk
>Mandrake Linux kernel 2.6.3-4 is not supported by Acronis
>True Image Echo Linux Server. Please upgrade kernel up to
>2.6.3-7mdk or later and repeate install. Some Mandrake
>10 kernels (i.e.2.6.3-19mdk) have broken "build" and "source"
>link in /lib/modules/... directory so dkms can not build
>snapapi26 kernel module. In such a case please locate kernel
>sources or includes in /usr/src directory and build snapapi26
>kernel module manually according to the section I.
>IV. Common installation procedure on Debian
>a) If you are installing the software on a 2.4 kernel based
>distribution:
>1. Install kernel sources.
>2. Build and install kernel module.
># dkms build -m snapapi -v <SNAPAPI_VERSION> -k 2.4.25-1 \
> --config /boot/config-2.4.25-1-386 --arch i686 \
> --kernelsourcedir /usr/src/kernel-sources-2.4.25
># dkms install -m snapapi -v <SNAPAPI_VERSION> -k 2.4.25-1 \
> --config /boot/config-2.4.25-1-386 --arch i686 \
> --kernelsourcedir /usr/src/kernel-sources-2.4.25
><SNAPAPI_VERSION> is current snapapi version.
>It is supposed that you have kernel 2.4.25-1, kernel
>architecture is i686.
>3. Most probably raw-devices were not created during Debian
>3.0 installation/configuring. Following simple script can be
>used to check and create the devices if needed (root
>permissions required):
>#!/bin/bash
>mkdir -p /dev/raw/
>if [ ! -e /dev/rawctl ] ;then
> mknod /dev/rawctl c 162 0
>fi
>for i in `seq 1 128`; do
> if [ ! -e /dev/raw/raw${i} ] ;then
> mknod /dev/raw/raw${i} c 162 ${i}
> fi
>done
>4. Activate devfs support by commands:
># mkdir /devfs
># mount -t devfs devfs /devfs
>5. Make devfs support permanent by adding the following line
>to your /etc/fstab file:
>devfs /devfs devfs defaults 0 0
>
>VIII. Installing on RedHat 8.0.
>On stock RedHat 8.0 kernel (2.4.18-14) installer can't build
>kernel module. It is recommended to upgrade kernel up to
>2.4.20-28.8 (or higher) located on RedHat site in updates
>for RedHat 8.0.
>If you want to keep old kernel you can follow section II
>("Installing on Mandrake 9.2 with kernel 2.4.X") subsections
>I and II and build kernel module.
>IX. Installing on TurboLinux 8.0.
>On stock TurboLinux 8.0 if the installer cannot build
>kernel modules please build them manually:
>1. Install the below packages from CD 2 if they are have
>not been installed earlier:
>kernel-source-2.4.18-5.i586.rpm
>kernel-headers-2.4.18-5.i586.rpm
>gcc-2.96-9.i586.rpm cpp-2.96-9.i586.rpm
>glibc-devel-2.2.5-13.i586.rpm
>2. Detect your kernel release by
># uname -r
>3. Build snapapi modules by
># dkms build -m snapapi -v 0.6.4 --config \
> /usr/src/linux/configs/kernel-2.4.18-5smp-i586.config
>Please use correct config file according your kernel release.
>In our example kernel release was 2.4.18-5smp.
>X. FAQ:
> Q: How do I run *.i686 installation file?
> A: This is a standard binary file. In order to start the
>installation, do:
># chmod +x <file_name>.i686
># ./<file_name>.i686
>where <file_name>.i686 is the name of your installation file.
> Q: Is *.i686 installation file compatible with my x86_64
> arch?
> A: Yes.In order to install Acronis True Echo Linux Server
>software on x86_64 Linux distribution follow the standard
>installation procedure.
> Q: Can I install Acronis True Image Echo Linux Servert on
> an ia64 system?
> A: No, this architecture is not supported by the current
>versions of Acronis True Image Echo Linux Server.
> Q: The installer complains that it cannot find kernel
> sources in /lib/modules/<MY_KERNEL>/build or in
> /lib/modules/<MY_KERNEL>/source directories. What should
> I do?
> A: This usually means that you do not have the sources of
>your running kernel installed. We suggest you to check the
>documentation for your Linux distribution to find the
>correct sources.
>Note: kernel sources should 100% correspond to your running
>kernel!
>Some examples are below:
>If you have Fedora Core Linux distribution:
>You may install the sources using rpm manager or using yum.
>Find your kernel version by entering:
># uname -r
>Let us suppose it is 2.6.12-1.1372_FC3
>And your kernel architecture by entering:
># uname -m
>Suppose it is i686
>So you should install kernel-devel-2.6.12-1.1372_FC3.i686.rpm
>package. You may find it on your Fedora Core installation CD
>or download from Fedora ftp server.In order to use yum to
>install the kernel sources, consult with the appropriate
>documentation.
>If you have RHEL4/CentOS 4.x Linux:
>Find your kernel version by entering:
># uname -r
>FSuppose it is 2.6.9-34.ELsmp
>Detect your kernel package architecture:
># uname -m
>Suppose it is i686.
>So you should install the kernel-smp-devel-2.6.9-34.EL.i686.rpm
>package. You should be able to find it on your Linux
>distribution CD.
>Note: on RHEL3/CentOS the name of the kernel source package
>should be kernel-source-<your_version>, where <your_version>
>is the name of your running kernel.
>If you are using SUSE Linux distribution:
>Find your kernel version:
># uname -r
>Suppose it is 2.6.5-7.244
>Detect your kernel package architecture:
># uname -m
>Suppose it is i686
>Note, most of all SUSE packages have i586 architecture, so
>you should install the package kernel-source-2.6.5-7.244.i586.rpm.
>You can find it on your Linux distribution CD or download
>from SUSE Linux ftp server.
>If you are using Debian distribution.
>The easiest way is to install the sources is to use apt-get
>utility.
>Find your kernel version:
># uname -r
>Suppose it is 2.6.18-3-686
>So, to install the sources of your kernel you should use the
>command below:
># apt-get install linux-source-2.6.18-3-686
>Note: "apt-get install linux-source" will download the
>sources of the most recent kernel. Use it only if you are
>completely sure that you are using the most recent kernel.
>Note: If you are using Debian Sarge, the command should be
>similar to:
># apt-get install kernel-source-<your_kernel>
>where <your_kernel> is the name of your kernel image.
>Q: I cannot connect to Acronis True Image Echo Enterprise
>Linux Agent installed on 64 bit Debian (or Debian-based)
>system. What should I do?
>A: At the moment Debian x86_64 does not support running
>32-bit applications to its full extent.
>Acronis True Image Echo Enterprise Linux Agent is a 32-bit
>application and it tries to authenticate against 64-bit PAM
>module by default. To solve this issue, you should install
>a minimal set of 32-bit libraries:
># apt-get install ia32-libs
>Download i386 package libpam-modules and the packages it
>depends on:
>libselinux1 libsepol1 from packages.debian.org
>For example, packages for Debian Etch can be downloaded from:
>http://packages.debian.org/stable/libs/libpam-modules
>http://packages.debian.org/stable/libs/libselinux1
>http://packages.debian.org/stable/libs/libsepol1
>Extract the downloaded packages. For example:
># dpkg --extract libpam-modules_0.79-4_i386.deb <TEMPORARY_DIRECTORY>
># dpkg --extract libselinux1_1.32-3_i386.deb <TEMPORARY_DIRECTORY>
># dpkg --extract libsepol1_1.14-2_i386.deb <TEMPORARY_DIRECTORY>
>Put the extracted shared libraries to /lib32/
># mkdir /lib32/security
># cp <TEMPORARY_DIRECTORY>/lib/security/* /lib32/security/
># cp <TEMPORARY_DIRECTORY>/lib/libselinux.so.1 /lib32/
># cp <TEMPORARY_DIRECTORY>/lib/libsepol.so.1 /lib32/
>Add the path to the extracted libraries to /etc/pam.d/acronisagent
>-----------
>#%PAM-1.0
>auth required /lib32/security/pam_unix.so
>account required /lib32/security/pam_unix.so
>-----------
>Restart Acronis True Image Echo Enterprise Linux Agent:
># /etc/init.d/acronis_trueimage_agent restart
>--
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request at redhat.com?subject=subscribe
>https://www.redhat.com/mailman/listinfo/redhat-list
>
More information about the redhat-list
mailing list