Error during update

meldalinn said:
root@proxmox:~# sudo apt upgrade
Click to expand...
I don't warrant for this in some specific cases like Nvidia, but the usual Proxmox' recommended / required method is

apt full-upgrade
not apt upgrade

Using upgrade instead of full-upgrade sometimes leads to incomplete upgrade, missing packages etc.
 
  • Like
Reactions: leesteken
Yep, it was pinned some time ago after the newest kernel didnt boot - thank you for guiding me through my previous mistakes good sir
 
Hi,

I'm in a similar situation as above, but I'm on Proxmox 8.4.16 running a Ubuntu 22.04.5 LTS container, and my real issue is getting OpenVPN Access Server (v3.0.2) to use DCO (Data Channel Offload) for which this lib: /lib/modules/6.8.12-17-pve is needed.

Why I in turn have tried to run:
  1. apt install pve-headers-$(uname -r)
  2. apt install proxmox-default-headers
  3. apt full-upgrade
And none of it helped, and here are some of the output from above:
Bash: 
root@bt-ovpn-nod01:~# apt install --upgrade r8125-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
r8125-dkms is already the newest version (9.007.01-3ubuntu0.3).
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

root@bt-ovpn-nod01:~# apt install --full-upgrade r8125-dkms
E: Sense full is not understood, try true or false.

root@bt-ovpn-nod01:~# apt install pve-headers-$(uname -r)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pve-headers-6.8.12-17-pve
E: Couldn't find any package by glob 'pve-headers-6.8.12-17-pve'

root@bt-ovpn-nod01:~# apt install proxmox-default-headers
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-default-headers

root@bt-ovpn-nod01:~# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libc-bin libc-dev-bin libc-devtools libc6 libc6-dev libmariadb3 locales mariadb-common
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

root@bt-ovpn-nod01:~# modprobe -r ovpn_dco_v2

root@bt-ovpn-nod01:~# modprobe  ovpn_dco_v2
modprobe: FATAL: Module ovpn_dco_v2 not found in directory /lib/modules/6.8.12-17-pve

Does anyone know how to get around this?

PS. The Access Server is up and running but complains with this message:

Code: 
OpenVPN data-channel offloading was requested but failed to activate.
This typically happens if there is a configuration option that is incompatible with DCO or if the DCO kernel module could not be loaded.
 
Last edited:
If the package was installed but dkms or the headers were missing it will not automatically attempt to build the module again. This should work
Bash: 
apt install openvpn-dco-dkms dkms proxmox-default-headers proxmox-headers-$(uname -r)
dkms autoinstall

Here's the thing though. It's not needed.
Bash: 
# find /lib/ -type f -name "*ovpn*"
/lib/modules/6.17.4-2-pve/kernel/drivers/net/ovpn/ovpn.ko
/lib/modules/6.17.4-1-pve/kernel/drivers/net/ovpn/ovpn.ko
I don't use OpenVPN so I can't tell you specifics.
 
Last edited:
And here are the result of above command:
Bash: 
root@bt-ovpn-nod01:~# apt install openvpn-dco-dkms dkms proxmox-default-headers  proxmox-headers-$(uname -r)
dkms autoinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-default-headers
E: Unable to locate package proxmox-headers-6.8.12-17-pve
E: Couldn't find any package by glob 'proxmox-headers-6.8.12-17-pve'
Error! Your kernel headers for kernel 6.8.12-17-pve cannot be found.
Please install the linux-headers-6.8.12-17-pve package or use the --kernelsourcedir option to tell DKMS where it's located.
Error! Your kernel headers for kernel 6.8.12-17-pve cannot be found.
Please install the linux-headers-6.8.12-17-pve package or use the --kernelsourcedir option to tell DKMS where it's located.

And the next as well:

Bash: 
root@bt-ovpn-nod01:~# find /lib/ -type f -name "*ovpn*"
/lib/modules/5.15.0-164-generic/updates/dkms/ovpn-dco-v2.ko
 
Sorry, I missed that you use PVE 8. I don't have a PVE 8 install to test but I checked the packages and this might here.
Bash: 
apt install openvpn-dco-dkms dkms pve-headers proxmox-headers-$(uname -r)
dkms autoinstall
In case you wonder why two header packages. pve-headers is a meta package that depends on the latest headers and the other command installs the headers for the currently running kernel. That might not be the latest one so we simply install both.
 
Last edited:
Thanks a lot for your contribution, but it still fails:

Bash: 
root@bt-ovpn-nod01:~# apt install openvpn-dco-dkms dkms pve-headers pve-headers-$(uname -r)
dkms autoinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pve-headers
E: Unable to locate package pve-headers-6.8.12-17-pve
E: Couldn't find any package by glob 'pve-headers-6.8.12-17-pve'
Error! Your kernel headers for kernel 6.8.12-17-pve cannot be found.
Please install the linux-headers-6.8.12-17-pve package or use the --kernelsourcedir option to tell DKMS where it's located.
Error! Your kernel headers for kernel 6.8.12-17-pve cannot be found.
Please install the linux-headers-6.8.12-17-pve package or use the --kernelsourcedir option to tell DKMS where it's located.
 
Sorry, I looked at the bullseye (PVE 7) packages. The ones for bookworm (PVE 8) and trixie (PVE 9) are named different. Very confusing.
The meta package for PVE 8 is called pve-headers and the header package for your kernel is called proxmox-headers-6.8.12-17-pve.
pve-headers should absolutely exist. Try this to find the right packages for your system
Bash: 
apt-cache search "$(uname -r)"
apt-cache search "headers" | grep -Ei "pve|proxmox"
 
Last edited:
Then you very likely didn't properly configure the PVE repos. Please share
Bash: 
apt update
apt policy
find /etc/apt/sources.list* -type f -exec tail -n +1 {} +
 
apt update:
Bash: 
root@bt-ovpn-nod01:~# apt update
Hit:1 http://packages.openvpn.net/as/debian jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [3165 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [485 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 c-n-f Metadata [19.1 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [5101 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [957 kB]
Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 c-n-f Metadata [632 B]
Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1249 kB]
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [311 kB]
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [30.1 kB]
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [70.1 kB]
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [15.5 kB]
Get:16 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages [2904 kB]
Get:17 http://archive.ubuntu.com/ubuntu jammy-security/main Translation-en [419 kB]
Get:18 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 c-n-f Metadata [14.1 kB]
Get:19 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1011 kB]
Get:20 http://archive.ubuntu.com/ubuntu jammy-security/universe Translation-en [222 kB]
Get:21 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f Metadata [22.5 kB]
Fetched 16.3 MB in 4s (4369 kB/s)                          
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
10 packages can be upgraded. Run 'apt list --upgradable' to see them.

apt policy:
Bash: 
root@bt-ovpn-nod01:~# apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://packages.openvpn.net/as/debian jammy/main amd64 Packages
     release o=as/debian jammy,a=jammy,n=jammy,l=as/debian jammy,c=main,b=amd64
     origin packages.openvpn.net
 500 http://archive.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=amd64
     origin archive.ubuntu.com
Pinned packages:

find /etc/apt/sources.list* -type f -exec tail -n +1 {} +:
Bash: 
root@bt-ovpn-nod01:~# find /etc/apt/sources.list* -type f -exec tail -n +1 {} +
==> /etc/apt/sources.list <==
deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse

deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse

deb http://archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse


==> /etc/apt/sources.list.d/openvpn-as-repo.list <==
deb [arch=amd64 signed-by=/etc/apt/keyrings/as-repository.asc] http://packages.openvpn.net/as/debian jammy main
 
Last edited:
Oh heck. You're working with ubuntu, not PVE. I'm making way too many mistakes today. I think I'm going to hide :oops:
You can't really install/load kernel modules inside the CT as it shares the kernel with the node.
 
Last edited:
Hmm - interesting!
There seem to be quite a few discussions around this topic on the net, and also here, and hopefully also some workarounds to the issue.
So instead if trying to fix this from the CT, what are the chances of fixing this issue from the PVE?

And how could that potentially look like?
 
I'm not certain as I don't use OpenVPN. Maybe passing /dev/tun like you can for tailscale works here too. Otherwise check the find command above on the node and try to modprobe that module there.
 
You must log in or register to reply here.
Top Bottom
Back