-
- Enthusiast
- Posts: 27
- Liked: 7 times
- Joined: Jul 01, 2016 4:07 pm
- Contact:
Issues on CentOS 8 Stream
Hi,
I am trying VAL on CentOS 8 Stream and do not get it to work. The veeamsnap module does not load.
Is it possible to get VAL working on the "Stream" flavor of CentOS 8 or is this not supported? (Going to be?)
https://wiki.centos.org/Manuals/Release ... ntOSStream
https://www.centos.org/download
I am trying VAL on CentOS 8 Stream and do not get it to work. The veeamsnap module does not load.
Is it possible to get VAL working on the "Stream" flavor of CentOS 8 or is this not supported? (Going to be?)
https://wiki.centos.org/Manuals/Release ... ntOSStream
https://www.centos.org/download
-
- Product Manager
- Posts: 5908
- Liked: 1236 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues on CentOS 8 Stream
Which is the error you are receiving?
GitHub: https://github.com/nielsengelen
-
- Enthusiast
- Posts: 27
- Liked: 7 times
- Joined: Jul 01, 2016 4:07 pm
- Contact:
Re: Issues on CentOS 8 Stream
Failed to create snapshot probably related to the fact that there is no veeamsnap for the current kernel:
Code: Select all
# modprobe veeamsnap
modprobe: FATAL: Module veeamsnap not found in directory /lib/modules/4.18.0-144.el8.x86_64
Code: Select all
# uname -a
Linux localhost.localdomain 4.18.0-144.el8.x86_64 #1 SMP Wed Sep 18 16:19:38 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Code: Select all
[18.11.2019 10:35:45] <140585965172480> lpbcore| Requesting snapshot for device sda1 [8:1].
[18.11.2019 10:35:45] <140585965172480> lpbcore| Requesting snapshot for device sda3 [8:3].
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][processing] Creating volume snapshot.
[18.11.2019 10:35:45] <140585965172480> lpbcore| WARN|Method invocation was not finalized. Method id [1]. Class: [lpbcorelib::interaction::ISnapshotOperation]
[18.11.2019 10:35:45] <140585965172480> lpbcore| ERR |Child execution has failed. Exit code: [1].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to execute [modprobe].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to finish snapshot creation process.
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to invoke method [1] in class [lpbcorelib::interaction::ISnapshotOperation].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |An exception was thrown from thread [140585965172480].
[18.11.2019 10:35:45] <140585965172480> lpbcore| ERR |Failed to execute thaw script with status: fail.
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][error] Failed to create volume snapshot.
[18.11.2019 10:35:45] <140585965172480> lpbcore| Taking snapshot. Failed.
[18.11.2019 10:35:45] <140585965172480> lpbcore| BackupJobPerformer: Creating backup. Failed.
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][error] Failed to perform backup.
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][error] Child execution has failed. Exit code: [1].
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0].
[18.11.2019 10:35:45] <140585965172480> vmb | [SessionLog][error] Processing finished with errors at 2019-11-18 10:35:45 GMT.
[18.11.2019 10:35:45] <140585965172480> lpbcore| ERR |Child execution has failed. Exit code: [1].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to execute [modprobe].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to finish snapshot creation process.
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |--tr:Failed to create volume snapshot.
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |Backup job has failed.
[18.11.2019 10:35:45] <140585965172480> lpbcore| >> |An exception was thrown from thread [140585965172480].
[18.11.2019 10:35:45] <140585999297536> | Closing socket device.
[18.11.2019 10:35:45] <140585999297536> lpbcore| LpbManSession: Processing commands. ok.
[18.11.2019 10:35:45] <140585999297536> | Closing socket device.
[18.11.2019 10:35:45] <140585965172480> lpbcore| JOB STATUS: FAILED.
[18.11.2019 10:35:45] <140585965172480> | Thread finished. Role: 'Volume backup job execution'.
[18.11.2019 10:35:45] <140585999297536> | Closing socket device.
[18.11.2019 10:35:45] <140585999297536> | Closing socket device.
[18.11.2019 10:35:45] <140585999297536> lpbman | Application session has been finished.
-
- Product Manager
- Posts: 6579
- Liked: 773 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Issues on CentOS 8 Stream
Hi,
No, VAL doesn't support CentOS Stream.
The error that you see indicates that something went wrong during veeamsnap module installation. Which version did you install - kmod, or dkms?
Thanks!
No, VAL doesn't support CentOS Stream.
The error that you see indicates that something went wrong during veeamsnap module installation. Which version did you install - kmod, or dkms?
Thanks!
-
- Enthusiast
- Posts: 27
- Liked: 7 times
- Joined: Jul 01, 2016 4:07 pm
- Contact:
Re: Issues on CentOS 8 Stream
Code: Select all
# rpm -qa | egrep -i 'veeam|dkms'
kmod-veeamsnap-3.0.2.1185-4.18.0_80.el8.x86_64
veeam-release-el8-1.0.7-1.x86_64
veeam-3.0.2.1185-1.el8.x86_64
dkms-2.7.1-2.el8.noarch
-
- Product Manager
- Posts: 6579
- Liked: 773 times
- Joined: May 19, 2015 1:46 pm
- Contact:
-
- Enthusiast
- Posts: 27
- Liked: 7 times
- Joined: Jul 01, 2016 4:07 pm
- Contact:
Re: Issues on CentOS 8 Stream
Thanks!
Got is working...
Got is working...
Code: Select all
# yum install veeamsnap-3.0.2.1185-1.noarch.rpm
# yum install veeam
# wget https://mirror.hh.se/centos/8-stream/BaseOS/x86_64/os/Packages/kernel-headers-4.18.0-144.el8.x86_64.rpm
# wget https://mirror.hh.se/centos/8-stream/BaseOS/x86_64/os/Packages/kernel-devel-4.18.0-144.el8.x86_64.rpm
# yum localinstall kernel-headers-4.18.0-144.el8.x86_64.rpm kernel-devel-4.18.0-144.el8.x86_64.rpm
# dkms build -m veeamsnap -v 3.0.2.1185
# dkms install -m veeamsnap -v 3.0.2.1185
# dkms status
veeamsnap, 3.0.2.1185, 4.18.0-144.el8.x86_64, x86_64: installed
# veeam
-
- Product Manager
- Posts: 6579
- Liked: 773 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Issues on CentOS 8 Stream
Thank you for getting back to us with the info!
-
- Novice
- Posts: 7
- Liked: 3 times
- Joined: Jan 15, 2019 11:17 pm
- Full Name: John Palys
- Contact:
Re: Issues on CentOS 8 Stream
This solution worked for me as well on Centos 8.0
# uname -r
4.18.0-147.5.1.el8_1.x86_64
# rpm -qa |grep veeam
veeam-3.0.2.1185-1.el8.x86_64
veeam-release-el8-1.0.7-1.x86_64
veeamsnap-3.0.2.1185-1.noarch
1. I uninstalled veeamsnap and veeam > dnf remove kmod-veeamsnap-3.0.2.1185-4.18.0_80.el8.x86_64
Thi uninstalled both the veamsnap and veeam itself.
2. Downloaded and installed > yum install veeamsnap-3.0.2.1185-1.noarch.rpm
This required a slew of other rpms that were installed.
3. Installed veeam > yum install veeam.
Ran the backup and it worked as it should.
# uname -r
4.18.0-147.5.1.el8_1.x86_64
# rpm -qa |grep veeam
veeam-3.0.2.1185-1.el8.x86_64
veeam-release-el8-1.0.7-1.x86_64
veeamsnap-3.0.2.1185-1.noarch
1. I uninstalled veeamsnap and veeam > dnf remove kmod-veeamsnap-3.0.2.1185-4.18.0_80.el8.x86_64
Thi uninstalled both the veamsnap and veeam itself.
2. Downloaded and installed > yum install veeamsnap-3.0.2.1185-1.noarch.rpm
This required a slew of other rpms that were installed.
3. Installed veeam > yum install veeam.
Ran the backup and it worked as it should.
Who is online
Users browsing this forum: No registered users and 17 guests