Cannot install Veeam on Debian with Linux kernel v4.19.*

[jdrch]

I'm trying to install Veeam Agent for Linux on Debian with Linux kernel 4.19, which is supported.

The below is what I'm getting from the terminal:

Code: Select all

$ sudo dpkg -i ./veeam-release* && apt-get update
Selecting previously unselected package veeam-release-deb.
(Reading database ... 348595 files and directories currently installed.)
Preparing to unpack .../veeam-release-deb_1.0.7_amd64.deb ...
Unpacking veeam-release-deb (1.0.7) ...
Setting up veeam-release-deb (1.0.7) ...
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)
$ sudo apt-get install veeam
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package veeam

Case ID: 03664821

Any ideas?

[nielsengelen]

This isn't related to Veeam but related to your apt being locked and permission denied on it. Can u try running apt-get update as root?

[danswartz]

I think the sudo is only applying to the first command. Try adding 'sudo' before the apt-get?

[jdrch]

@danswartz: That was definitely the problem, thanks!

@nielsengelen: I strongly suggest updating the documentation to split dpkg + apt-get command into separate sudo commands. The status quo is confusing.

Thanks to both of you; I've gotten it installed now.

[PTide]

Hi,

I strongly suggest updating the documentation to split dpkg + apt-get command into separate sudo commands. The status quo is confusing.

This is a little bit confusing...The only place where we mention this line

Code: Select all

dpkg -i ./veeam-release* && apt-get update

is this page, and it contains no 'sudo'.

So, do you want us to explicitly mention that those two commands require two separate sudo calls, or there is another place in our user guide that mentions a single 'sudo' usage for two command going one after another?

Thanks!