Debian 9 Support?

[MRRamsay]

Hello;

I'm new to the Linux side of things being a Windows guy since V3.1, but I'm looking into options for a client to back up a single Linux VM running Debian 9.1.0 (kernel 4.9.0). The sepc's for Veeam Agent for Linux say Debian 6 to 8 but not 9, however do say Linux kernel 2.6.32 or later is required with no upper limit specified.

So, is it compatible?

Thanks.

Marc

[PTide]

Hi,

Any kernel > 2.6.32 is supported as long as it is supplied by your distribution. The latest kernel for Debian 8 is 3.16. Debian 9 will be supported in VAL 2.0 which is coming soon. You may try to install it on Debian 9, it should work, however in this case support will be provided via forum and on the best effort basis only.

Thank you

[MRRamsay]

Thanks for the response PTide. What is VAL 2.0?

[nielsengelen]

Veeam Agent for Linux v2 which is currently in development.

[MRRamsay]

Thank you. I'll try the existing Agent and see how it goes.

[obrobertsen]

I had Veeam Linux repository working perfect on Debian 8 - Then I installed a new server on Debian 9
And can confirm that this is not working.
VeeamAgent is an ELF file been droppet to /tmp and executed. And I can se dmesg errors like:

Code: Select all

[ 2006.311480] VeeamAgent84703[5274] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7fffb5b960d8 ax:ffffffffff600000 si:0 di:7fffb5b960f0
[ 2006.311486] VeeamAgent84703[5274]: segfault at ffffffffff600000 ip ffffffffff600000 sp 00007fffb5b960d8 error 15

root@server:/# uname -a
Linux server 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) x86_64 GNU/Linux

root@server:/tmp# perl -v

This is perl 5, version 24, subversion 1 (v5.24.1) built for x86_64-linux-gnu-thread-multi

Anyone got this working? Someone says only 32bit Perl is supported?

[nielsengelen]

Hi Owe, please contact support for additional help. If this is a normal kernel it should work as we support Debian 9 and default kernels.

[sibio]

I have the same issue. We are using OpenMediaVault 4, built on Debian 9 and the same error message occurs in syslog:

Code: Select all

[1039323.138249] VeeamAgente4921[17712] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7ffcbbe62908 ax:ffffffffff600000 si:0 di:7ffcbbe62920
[1039323.138255] VeeamAgente4921[17712]: segfault at ffffffffff600000 ip ffffffffff600000 sp 00007ffcbbe62908 error 15

[sibio]

The support can provide a patch (named Fix_132244_32ce1dab47.zip) but I am not permited to provide it myself, you'll have to ask them. It is supposed to be integrated in a future release however this is not yet the case.

[PTide]

I just want to clarify that fixes that we provided are often tailored to a particular use case, therefore it is simply might be not safe to share fixes.

Thanks

[vladimirh]

Hi,

below is solution for Debian 9 and higher Backup Repository (i.e. also OMV 4.x and higher).

I had to add it to /etc/default/grub like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet vsyscall=emulate"
After run command:
update-grub
reboot

[rawtaz]

@vladimirh Thank you very very much for posting that solution.

I can verify that adding "quiet vsyscall=emulate" to the GRUB_CMDLINE_LINUX_DEFAULT setting in /etc/default/grub on a Debian 10 Buster (`uname -a` == "Linux altitude 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux") system running as a VPS on KVM mitigates the following segfaults by the /tmp/VeeamAgent* binary (`file VeeamAgent*` == "ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.18, stripped"):

Code: Select all

Apr 23 00:26:19 altitude kernel: [ 4935.069208] VeeamAgent24d3f[3532] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7ffea462a788 ax:ffffffffff600000 si:0 di:7ffea462a7b0
Apr 23 00:26:19 altitude kernel: [ 4935.076703] VeeamAgent24d3f[3532]: segfault at ffffffffff600000 ip ffffffffff600000 sp 00007ffea462a788 error 15
Apr 23 00:26:19 altitude kernel: [ 4935.082740] Code: Bad RIP value.

Can you please elaborate on how you came to this conclusion? That is, what was the process of debugging the problem, and what made you realize you needed this specific setting in GRUB? It would be great to learn from, if you could tell us.

[PTide]

Hi @rawtaz,

Just FYI - VAL v4.0 is already available so I suggest you to try it and see if the problem persists.

Thanks!

[rawtaz]

@PTide Thanks. In my case I had the problems with the agent that Backup & Replication for vSphere deploys on the target repository server (a Linux one) in order to send backups and do other things like scan the server.

May be that if I upgrade to B&R v10 the problem is resolved and the workaround not needed, I can check that whenever I get to that point