problems about installation

Backup agent for Linux servers and workstations on-premises or in the public cloud

problems about installation

Veeam Logoby DaMoRph » Wed Jun 29, 2016 9:21 am

Hi,
i got issues about installing the VAfL
can anyone help me with analyst the Log?

Code: Select all
[root@localhost ~]# rpm -i /tmp/Veeam/VeeamAgentLinux_1.0.0.499BETA/x64/rpm/veeamsnap-1.0.0.499-1.noarch.rpm
Loading new veeamsnap-1.0.0.499 DKMS files...
Building for 3.10.0-327.18.2.el7.x86_64
Building initial module for 3.10.0-327.18.2.el7.x86_64
Done.

veeamsnap:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.10.0-327.18.2.el7.x86_64/extra/
Adding any weak-modules
/sbin/modinfo: invalid option -- 'F'
/sbin/weak-modules: line 24:  1978 Segmentation fault      (core dumped) "$@"
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modprobe: unrecognized option '--set-version'
Failed to install module vmxnet3

Broadcast message from systemd-journald@localhost.localdomain (Wed 2016-06-29 10:01:14 CEST):

dracut[2014]: Failed to install module vmxnet3

modprobe: unrecognized option '--ignore-install'

Message from syslogd@localhost at Jun 29 10:01:14 ...
 dracut:Failed to install module vmxnet3
modprobe: unrecognized option '--show-depends'
modprobe 2.4.26
Load/Unload modules with dependencies

Load module(s):
modprobe [-a -n -v ] [-C config ] [ -t type ] pattern OR module1 module2 ...
List modules:
modprobe [-l ] [-C config ] [ -t type ] pattern
note: wildcard patterns should be escaped
Show configuration:
modprobe [-C config ] -c
Remove module(s) or autoclean:
modprobe [-C config ] -r [ module ...]

options:
-a, --all Load _all_ matching modules
-c, --showconfig Show current configuration
-d, --debug Print debugging information
-h, --help Print this message
-k, --autoclean Set 'autoclean' on loaded modules
-l, --list List matching modules
-n, --show Don't actually perform the action
-q, --quiet Quiet operation
-r, --remove Remove module (stacks) or do autoclean
-s, --syslog Use syslog to report
-t, --type moduletype Only look for modules of this type
-v, --verbose Print all commands
-V, --version Show version
-C, --config configfile Use instead of /etc/modules.conf
depmod: QM_MODULES: Function not implemented

"depmod -a 3.10.0-327.18.2.el7.x86_64" failed.

Broadcast message from systemd-journald@localhost.localdomain (Wed 2016-06-29 10:01:15 CEST):

dracut[2014]: "depmod -a 3.10.0-327.18.2.el7.x86_64" failed.


Message from syslogd@localhost at Jun 29 10:01:15 ...
 dracut:"depmod -a 3.10.0-327.18.2.el7.x86_64" failed.
/sbin/weak-modules: line 75: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
/sbin/weak-modules: line 91: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
/sbin/weak-modules: line 96: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
Unable to decompress /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: Unknown format
/sbin/weak-modules: line 134: /tmp/weak-modules.amFs8Z/new_initramfs.img: No such file or directory
rm: cannot remove '/tmp/weak-modules.amFs8Z/new_initramfs.img': No such file or directory
mv: cannot stat '/boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp': No such file or directory

depmod...(bad exit status: 139)

-------- Uninstall Beginning --------
Module:  veeamsnap
Version: 1.0.0.499
Kernel:  3.10.0-327.18.2.el7.x86_64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.
Removing any linked weak-modules
/sbin/modinfo: invalid option -- 'F'
/sbin/weak-modules: line 24:  6790 Segmentation fault      (core dumped) "$@"
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modinfo: invalid option -- 'F'
modprobe: unrecognized option '--set-version'
Failed to install module vmxnet3
modprobe: unrecognized option '--ignore-install'

Broadcast message from systemd-journald@localhost.localdomain (Wed 2016-06-29 10:01:22 CEST):

dracut[6823]: Failed to install module vmxnet3


Message from syslogd@localhost at Jun 29 10:01:22 ...
 dracut:Failed to install module vmxnet3
modprobe: unrecognized option '--show-depends'
modprobe 2.4.26
Load/Unload modules with dependencies

Load module(s):
modprobe [-a -n -v ] [-C config ] [ -t type ] pattern OR module1 module2 ...
List modules:
modprobe [-l ] [-C config ] [ -t type ] pattern
note: wildcard patterns should be escaped
Show configuration:
modprobe [-C config ] -c
Remove module(s) or autoclean:
modprobe [-C config ] -r [ module ...]

options:
-a, --all Load _all_ matching modules
-c, --showconfig Show current configuration
-d, --debug Print debugging information
-h, --help Print this message
-k, --autoclean Set 'autoclean' on loaded modules
-l, --list List matching modules
-n, --show Don't actually perform the action
-q, --quiet Quiet operation
-r, --remove Remove module (stacks) or do autoclean
-s, --syslog Use syslog to report
-t, --type moduletype Only look for modules of this type
-v, --verbose Print all commands
-V, --version Show version
-C, --config configfile Use instead of /etc/modules.conf
depmod: QM_MODULES: Function not implemented

"depmod -a 3.10.0-327.18.2.el7.x86_64" failed.

Broadcast message from systemd-journald@localhost.localdomain (Wed 2016-06-29 10:01:22 CEST):

dracut[6823]: "depmod -a 3.10.0-327.18.2.el7.x86_64" failed.


Message from syslogd@localhost at Jun 29 10:01:22 ...
 dracut:"depmod -a 3.10.0-327.18.2.el7.x86_64" failed.
/sbin/weak-modules: line 75: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
/sbin/weak-modules: line 91: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
/sbin/weak-modules: line 96: /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: No such file or directory
Unable to decompress /boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp: Unknown format
/sbin/weak-modules: line 134: /tmp/weak-modules.NYZXre/new_initramfs.img: No such file or directory
rm: cannot remove '/tmp/weak-modules.NYZXre/new_initramfs.img': No such file or directory
mv: cannot stat '/boot/initramfs-3.10.0-327.18.2.el7.x86_64.tmp': No such file or directory

veeamsnap.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.10.0-327.18.2.el7.x86_64/extra/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...(bad exit status: 139)

DKMS: uninstall completed.
Error! Problems with depmod detected.  Automatically uninstalling this module.
DKMS: Install Failed (depmod problems).  Module rolled back to built state.
WARNING: Package not configured! See output!
Warnung: %post(veeamsnap-1.0.0.499-1.noarch) Scriptlet fehlgeschlagen, Beenden-Status 1


greets
DaMoRph
DaMoRph
Novice
 
Posts: 4
Liked: 1 time
Joined: Wed Jun 29, 2016 7:50 am
Full Name: Sebastian Meister

Re: problems about installation

Veeam Logoby PTide » Wed Jun 29, 2016 9:42 am

Hi,

Could you please post an output of uname -r command?

Thanks
PTide
Veeam Software
 
Posts: 2886
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: problems about installation

Veeam Logoby DaMoRph » Wed Jun 29, 2016 9:49 am

Hi
here it is

Code: Select all
[root@localhost ~]# uname -r
3.10.0-327.18.2.el7.x86_64
DaMoRph
Novice
 
Posts: 4
Liked: 1 time
Joined: Wed Jun 29, 2016 7:50 am
Full Name: Sebastian Meister

Re: problems about installation

Veeam Logoby PTide » Wed Jun 29, 2016 10:45 am

Does the kernel version match kernel-headers version? To find out the current kernel-headers version please run rpm -qa | grep kernel-header

Thanks
PTide
Veeam Software
 
Posts: 2886
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: problems about installation

Veeam Logoby DaMoRph » Wed Jun 29, 2016 11:40 am

Code: Select all
[root@localhost ~]# rpm -qa | grep kernel-header
kernel-headers-3.10.0-327.18.2.el7.x86_64
DaMoRph
Novice
 
Posts: 4
Liked: 1 time
Joined: Wed Jun 29, 2016 7:50 am
Full Name: Sebastian Meister

Re: problems about installation

Veeam Logoby PTide » Wed Jun 29, 2016 1:58 pm

Is that CentOS installed inside a vSphere VM with vmxnet3? Did you install that CentOS from scratch or you've upgraded from CentOS 6? Please try changing NIC type to e1000 and try again. Also please collect logs from /var/log/messages and share them (you can use dropbox).

Thanks
PTide
Veeam Software
 
Posts: 2886
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: problems about installation

Veeam Logoby DaMoRph » Thu Jun 30, 2016 12:57 pm 1 person likes this post

Hi,
i have fixed it.

1. e1000 NIC
2. a latest version of epel.rpm & DKMS.rpm

just it works ;)

thx
DaMoRph
Novice
 
Posts: 4
Liked: 1 time
Joined: Wed Jun 29, 2016 7:50 am
Full Name: Sebastian Meister

Re: problems about installation

Veeam Logoby poulpreben » Fri Jul 01, 2016 5:59 am

Hi Sebastian. Did you try with VMXNET3 after updating epel and dkms?
poulpreben
Expert
 
Posts: 930
Liked: 391 times
Joined: Mon Jul 23, 2012 8:16 am
Full Name: Preben Berg

Re: problems about installation

Veeam Logoby dellock6 » Fri Jul 01, 2016 6:15 am

That's strange because in my lab that I used for the blog post, the machines are centos 7 with vmxnet3 nic, and I never hit this issue.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 4934
Liked: 1293 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: problems about installation

Veeam Logoby poulpreben » Fri Jul 01, 2016 6:20 am

That's why I am asking, because that is also the configuration I am using.
poulpreben
Expert
 
Posts: 930
Liked: 391 times
Joined: Mon Jul 23, 2012 8:16 am
Full Name: Preben Berg

Re: problems about installation

Veeam Logoby PTide » Fri Jul 01, 2016 10:02 am

That's strange because in my lab that I used for the blog post, the machines are centos 7 with vmxnet3 nic, and I never hit this issue.

Me neither.

I've seen an opinion that vmxnet3 used to be quite problematic, also some people reported that on previous versions of CentOS it was required to install VMware Tools in order to make the adapter to work properly. So I'm not sure if everything's been fixed and works properly in 100% of cases on CentOS 7
PTide
Veeam Software
 
Posts: 2886
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: problems about installation

Veeam Logoby dellock6 » Fri Jul 01, 2016 3:41 pm

Ah wait, my templates have all open vm tools, no idea if this can be the difference.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 4934
Liked: 1293 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: problems about installation

Veeam Logoby PTide » Fri Jul 01, 2016 4:09 pm

Ah wait, my templates have all open vm tools, no idea if this can be the difference.

I believe it can:
<..>Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools or open-vm-tools to have a driver for the VMXNET 3 network adapter available.<...>
PTide
Veeam Software
 
Posts: 2886
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 3 guests