Giters

veeam / veeamsnap

Veeam Agent for Linux kernel module

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Veeamsnap not installing on Debian 11

541263 opened this issue · comments

commented

Can't install veeamsnap-5.0.0.4318 after upgrading to Debian 11 Bullseye.

Error! Bad return status for module build on kernel: 5.10.0-8-amd64 (x86_64)

make: Entering directory '/usr/src/linux-headers-5.10.0-8-amd64'
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/log.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist_ex.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_direct.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_redirect.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_deferred.o
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c: In function ‘blk_dev_open’:
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:15: error: implicit declaration of function ‘bdget’; did you mean ‘dget’? [-Werror=implicit-function-declaration]
17 | blk_dev = bdget( dev_id );
| ^~~~~
| dget
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:13: warning: assignment to ‘struct block_device *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
17 | blk_dev = bdget( dev_id );
| ^
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:26:16: error: implicit declaration of function ‘blkdev_get’; did you mean ‘blkdev_put’? [-Werror=implicit-function-declaration]
26 | refCount = blkdev_get( blk_dev, FMODE_READ | FMODE_WRITE, NULL );
| ^~~~~~~~~~
| blkdev_put
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-5.10.0-8-common/scripts/Makefile.build:284: /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-headers-5.10.0-8-common/Makefile:1845: /var/lib/dkms/veeamsnap/5.0.0.4318/build] Error 2
make: *** [/usr/src/linux-headers-5.10.0-8-common/Makefile:185: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.0-8-amd64'

commented

Yeah related to #10 . 1 year without a fix.

commented

Yeah related to #10 . 1 year without a fix.

well... shit

commented

As you say. Bullseye is now stable, which means veeamsnap is now broken.

commented

As you say. Bullseye is now stable, which means veeamsnap is now broken.

'Broken' is not really a correct terms to describe a situation when something is used out of it's supported scope.
Debian 11 uses kernel version which is not on the list of kernels that veeamsnap fully supports (mind the experimental support part).

Good news though - we've found a way to support even that, so be patient, please.

Thanks!

commented

You will be happy to know that since the release of 5.0.1 (released today) veeamsnap now supports up to Kernel 5.13 from "master"

commented

You will be happy to know that since the release of 5.0.1 (released today) veeamsnap now supports up to Kernel 5.13 from "master"

I'm not happy. It doesn't work.

[12.10.2021 12:40:22.527] <139652992325376> lpbcore| WARN|Snapshot storage type by default is stretch.
[12.10.2021 12:40:22.527] <139652992325376> vsnap | Checking the compatibility of the kernel module with others
[12.10.2021 12:40:22.528] <139652992325376> vsnap | Loading kernel 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 logmaxsize=15728640].
[12.10.2021 12:40:22.528] <139652992325376> | Creating child process: modinfo with arguments: -F, version, blk-snap
[12.10.2021 12:40:22.532] <139652992325376> vsnap | WARN|Module [blk-snap] is not available.
[12.10.2021 12:40:22.532] <139652992325376> | Arguments: [modprobe veeamsnap zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0 logmaxsize=15728640].
[12.10.2021 12:40:22.541] <139652992325376> vsnap | Try to cleanup old veeamsnap logs
[12.10.2021 12:40:22.542] <139652992325376> vsnap | Obtain module compatibility flags
[12.10.2021 12:40:22.542] <139652992325376> vsnap | Veeamsnap compatibility flags: [0x000000000000000d]
[12.10.2021 12:40:22.542] <139652992325376> vsnap | Get unspecified kernel entries
[12.10.2021 12:40:22.542] <139652992325376> vsnap | blk_mq_submit_bio
[12.10.2021 12:40:22.542] <139652992325376> vsnap | Fake system map was found in file [/boot/System.map-5.10.0-9-amd64]
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| Snapshot service: request snapshots. Failed.
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| ERR |Snapshot creation operation has failed.
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| >> |System.map file not found
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| >> |--tr:in void veeamsnap::SpecifyKernelEntries(const std::set<std::__cxx11::basic_string >&, std::__cxx11::listveeamsnap::SKernelEntry&) at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/KernelEntry.cpp:60
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| >> |Cannot specify kernel entries
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| >> |--tr:in void veeamsnap::CVeeamSnapIo::OpenCtrl() at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/VeeamSnapIo.cpp:196
[12.10.2021 12:40:22.542] <139652992325376> lpbcore| >> |An exception was thrown from thread [139652992325376].
[12.10.2021 12:40:22.542] <139652992325376> | Thread finished. Role: 'snapshot operation'.
[12.10.2021 12:40:22.590] <139652589672192> prtcl | ERR |System.map file not found
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:in void veeamsnap::SpecifyKernelEntries(const std::set<std::__cxx11::basic_string >&, std::__cxx11::listveeamsnap::SKernelEntry&) at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/KernelEntry.cpp:60
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |Cannot specify kernel entries
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:in void veeamsnap::CVeeamSnapIo::OpenCtrl() at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/VeeamSnapIo.cpp:196
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:Failed to finish snapshot creation process.
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:in virtual lpbcorelib::interaction::ISnapshotResourceLockPtr lpbcorelib::service::CSnapshotOperation::EndCreateSnapshot(lpbcorelib::service::CSnapshotTask::Ptr&) at /mnt/Sources/LPBCoreLib/lpbcorelib/service/SnapshotOperation.cpp:33
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::ISnapshotOperation].
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |--tr:in void remoting::CStubBase<TStub, TObject>::ExecuteMethod(remoting::method_id_t, remoting::IStub::SDispatchContext&) const [with TStub = lpbcorelib::interaction::proxystub::CSnapshotOperationStub; TObject = lpbcorelib::interaction::ISnapshotOperation; remoting::method_id_t = unsigned int] at /mnt/Sources/LPBCoreLib/lpbcorelib/interaction/proxystub/../../../../ProtocolLib/remoting/StubBase.h:78
[12.10.2021 12:40:22.590] <139652589672192> prtcl | >> |An exception was thrown from thread [139652992325376].
[12.10.2021 12:40:22.643] <139652589672192> lpbcore| Unregister client: {00000000-0000-0000-0000-000000000000}.
[12.10.2021 12:40:22.643] <139652589672192> | Thread finished. Role: 'peer local sock peer for user 0'.
[12.10.2021 12:40:22.645] <139652598064896> lpbcore| Manager process [845699] has been shutdown.
[12.10.2021 12:40:22.645] <139652598064896> | Thread finished. Role: 'Manager process [845699] shutdown handler.'.
[12.10.2021 12:40:22.645] <139652967147264> lpbcore| Cleaning up resources for job process [845699].
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| ERR |Backup job has failed.
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |System.map file not found
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in void veeamsnap::SpecifyKernelEntries(const std::set<std::__cxx11::basic_string >&, std::__cxx11::listveeamsnap::SKernelEntry&) at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/KernelEntry.cpp:60
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |Cannot specify kernel entries
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in void veeamsnap::CVeeamSnapIo::OpenCtrl() at /mnt/Sources/VeeamLPBSnapLib/veeamsnap/VeeamSnapIo.cpp:196
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:Failed to finish snapshot creation process.
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in virtual lpbcorelib::interaction::ISnapshotResourceLockPtr lpbcorelib::service::CSnapshotOperation::EndCreateSnapshot(lpbcorelib::service::CSnapshotTask::Ptr&) at /mnt/Sources/LPBCoreLib/lpbcorelib/service/SnapshotOperation.cpp:33
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::ISnapshotOperation].
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in void remoting::CStubBase<TStub, TObject>::ExecuteMethod(remoting::method_id_t, remoting::IStub::SDispatchContext&) const [with TStub = lpbcorelib::interaction::proxystub::CSnapshotOperationStub; TObject = lpbcorelib::interaction::ISnapshotOperation; remoting::method_id_t = unsigned int] at /mnt/Sources/LPBCoreLib/lpbcorelib/interaction/proxystub/../../../../ProtocolLib/remoting/StubBase.h:78
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:Failed to take volume snapshot.
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in static lpbcorelib::interaction::ISnapshotResourceLockPtr lpbcorelib::backup::CSnapshotHelper::TakeSnapshot(vmbplatform::model::CBackupJobPtr, const std::__cxx11::list<boost::shared_ptrlpbcorelib::backup::IBackupObject >&, const object_id_t&, vmbplatform::model::CSessionLoggerPtr, lpbcorelib::backup::CCbtDataContainer&) at /mnt/Sources/LPBCoreLib/lpbcorelib/backup/snapshot/SnapshotHelper.cpp:126
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |Backup job has failed.
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |--tr:in virtual void lpbcorelib::backup::CBackupJobPerformer::execute() at /mnt/Sources/LPBCoreLib/lpbcorelib/backup/BackupJobPerformer.cpp:158
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| >> |An exception was thrown from thread [139652589672192].
[12.10.2021 12:40:22.645] <139652606457600> lpbcore| WARN|Job has failed. [0] attempts left.
[12.10.2021 12:40:22.653] <139652606457600> lpbcore| Job can not be retried. All attempts were made.
[12.10.2021 12:40:22.653] <139652606457600> | Thread finished. Role: 'backup job retry handler'.
[12.10.2021 12:40:34.145] <139653000718080> lpbcore| Unregister client: {5e86c3ec-7170-4f64-bb76-23636e348472}.
[12.10.2021 12:40:34.146] <139653000718080> | Thread finished. Role: 'peer local sock peer for user 0'.

commented
commented

Reading system requirements before installing products will make you more happy. You should try ;)

You still don't support Debian 11 and are happy about it? :(

commented
commented

That is not a correct statement that shows me you STILL didn't bother reading system requirements.

I double checked all the installation instructions and still can't use Veeam Agent for Linux (it installs fine, no errors, but doesn't work).
Maybe I'm missing something, then don't be smart, but tell me what.

uname -a: Linux debra 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
i downloaded veeam-release-deb_1.0.8_amd64.deb
dpkg -i veeam-release-deb_1.0.8_amd64.deb
apt update
apt install veeam

root# apt-get install veeam
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
veeamsnap
The following NEW packages will be installed:
veeam veeamsnap
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 49.3 MB of archives.
After this operation, 51.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://repository.veeam.com/backup/linux/agent/dpkg/debian/public stable/veeam amd64 veeamsnap all 5.0.1.4493 [84.9 kB]
Get:2 http://repository.veeam.com/backup/linux/agent/dpkg/debian/public stable/veeam amd64 veeam amd64 5.0.1.4493 [49.3 MB]
Fetched 49.3 MB in 5s (10.3 MB/s)
Selecting previously unselected package veeamsnap.
(Reading database ... 148966 files and directories currently installed.)
Preparing to unpack .../veeamsnap_5.0.1.4493_all.deb ...
Unpacking veeamsnap (5.0.1.4493) ...
Selecting previously unselected package veeam.
Preparing to unpack .../veeam_5.0.1.4493_amd64.deb ...
Unpacking veeam (5.0.1.4493) ...
Setting up veeamsnap (5.0.1.4493) ...
Loading new veeamsnap-5.0.1.4493 DKMS files...
Building for 5.10.0-9-amd64
Building initial module for 5.10.0-9-amd64
Done.

veeamsnap.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/5.10.0-9-amd64/updates/dkms/

depmod...

DKMS: install completed.
Setting up veeam (5.0.1.4493) ...
Enable veeamservice
Synchronizing state of veeamservice.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable veeamservice
insserv: warning: current start runlevel(s) (empty) of script veeamservice' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script veeamservice' overrides LSB defaults (0 1 6).
Created symlink /etc/systemd/system/multi-user.target.wants/veeamservice.service → /usr/lib/systemd/system/veeamservice.service.
Try to stop veeamservice
Start veeamservice
Processing triggers for man-db (2.9.4-2) ...

aaaand backup jobs fails anyway

commented
commented

You’re missing software pre-requisites. Search the System Requirements document for “Debian 11”:

In a tiny font ... install a 750MB linux-image-dbg! Agggrrrrr!!!!!!!!!

commented
commented

Yeah Debian decided to be different from any other distribution out there and for whatever reason dropped the system.map file from its default install.

Can I hope that in the future it will be resolved somehow more adequately? At your side?

commented
commented

It’s unlikely as system.map is essential to the only remaining way left for us to intercept I/O starting from kernel 5.8. I hope that the Debian community can convince its maintainers to put system.map back (as literally EVERY other distro includes it by default).

Understood. Thanks for the help.