[SOLVED] LXC won't start after updates

[billbillw]

I posted this in another thread, but it was marked as "solved", so I'm posting here just so that it doesn't get ignored.

Here is what happened last night. I accidentally went through some apt-get update/upgrades for the Promox Host and wasn't paying close attention. (I thought I was updating my Ubuntu container) and after reboot, I can't get any of my containers to start.

According to journal ctl, it is the apparmor issue.

This is what comes up with pveversion -ve:
proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.13-5-pve: 4.13.13-38
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9


I have the recommended sources in /etc/apt/sources.list
I can't copy/past because it has external links, but it definitely has the debian/pve stretch pve-no-subscription line in it.

I tried apt update apt full-upgrade, but it doesn't seem to do anything.

I am fairly novice with linux and proxmox, so any help would be appreciated.

 

[tom]

Please update your host, maybe lxc-pve: 2.1.1-3 fixes your issues (also available in pve-no-subscription repo).

> apt update
> apt dist-upgrade

 

[billbillw]

Tried that just now, result:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded...

 

[billbillw]

I've been wondering, is it normal to get this when doing apt update or apt-get update?

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.proxmox.com/debian/pve stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
W: Some index files failed to download. They have been ignored, or old ones used instead.

I originally installed from the ISO disc. I also ran the the wget line that is shown in the SecureApt section of the Package Repositories wiki page.

 

[billbillw]

Unfortunately, I think I read this post from @fabian too late. I did run apt-get upgrade yesterday. Still learning...I will use apt commands from now on. Anyone know a way to fix my Proxmox VE host?

 

[billbillw]

Tried to update lxc-pve alone, this is what it says:
root@billx2:~# apt upgrade lxc-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
lxc-pve is already the newest version (2.1.1-2).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@billx2:~#

I can see the 2.1.1-3 version in the Repo...

 

[billbillw]

Ok, I solved it on my own..not bad for a linux newb.
I had to clear the apt update list and start over.
rm /var/lib/apt/lists/*
After that, I ran apt update and apt full-upgrade and ended up with this:

proxmox-ve: 5.1-42 (running kernel: 4.13.16-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9


I'm kinda surprised to see the 4.13.16-1-pve kernel, but it works for now.