TASK ERROR: command 'systemctl start pve-container@102' failed: exit code 1

renegade992

New Member
May 14, 2018
2
0
1
34
Can`t create lxc on proxmox. Systemctl status show this:
Code:
root@pm3:~# systemctl status pve-container@102.service
● pve-container@102.service - PVE LXC Container: 102
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-05-14 10:26:32 EEST; 6min ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 10727 ExecStart=/usr/bin/lxc-start -n 102 (code=exited, status=1/FAILURE)

May 14 10:26:32 pm3 systemd[1]: Starting PVE LXC Container: 102...
May 14 10:26:32 pm3 lxc-start[10727]: lxc-start: 102: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
May 14 10:26:32 pm3 lxc-start[10727]: lxc-start: 102: tools/lxc_start.c: main: 371 The container failed to start.
May 14 10:26:32 pm3 lxc-start[10727]: lxc-start: 102: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
May 14 10:26:32 pm3 lxc-start[10727]: lxc-start: 102: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
May 14 10:26:32 pm3 systemd[1]: pve-container@102.service: Control process exited, code=exited status=1
May 14 10:26:32 pm3 systemd[1]: pve-container@102.service: Killing process 10740 (lxc-start) with signal SIGKILL.
May 14 10:26:32 pm3 systemd[1]: Failed to start PVE LXC Container: 102.
May 14 10:26:32 pm3 systemd[1]: pve-container@102.service: Unit entered failed state.
May 14 10:26:32 pm3 systemd[1]: pve-container@102.service: Failed with result 'exit-code'.

Version:
Code:
root@pm3:~# pveversion
pve-manager/5.1-41/0b958203 (running kernel: 4.13.13-2-pve)
root@pm3:~# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
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-18
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-12
pve-qemu-kvm: 2.9.1-5
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.3-pve1~bpo9
 
please upgrade to the current version
 
I have got the same problem...
My Server got an restart, and then not LXC can be started.

Code:
systemctl start lxc@105
Job for lxc@105.service failed. See 'systemctl status lxc@105.service' and 'journalctl -xn' for details.
Code:
systemctl status lxc@105.service
● lxc@105.service - LXC Container: 105
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           └─pve-reboot.conf
   Active: failed (Result: exit-code) since Fr 2018-05-25 00:39:10 CEST; 19s ago
     Docs: man:lxc-start
           man:lxc
  Process: 3743 ExecStart=/usr/bin/lxc-start -n %i (code=exited, status=1/FAILURE)

Mai 25 00:39:10 host2 lxc-start[3743]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Mai 25 00:39:10 host2 lxc-start[3743]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Mai 25 00:39:10 host2 lxc-start[3743]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Mai 25 00:39:10 host2 systemd[1]: lxc@105.service: control process exited, code=exited status=1
Mai 25 00:39:10 host2 systemd[1]: Failed to start LXC Container: 105.
Mai 25 00:39:10 host2 systemd[1]: Unit lxc@105.service entered failed state.

Code:
pveversion -v
proxmox-ve: 4.4-110 (running kernel: 4.4.117-2-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.59-1-pve: 4.4.59-87
pve-kernel-4.4.117-2-pve: 4.4.117-110
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.49-1-pve: 4.4.49-86
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+2
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-105
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: not correctly installed
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80

I installed the new version of Proxmox on a 2. Server.
Then I copied a backup to the new server... same problem... the container won't start.
Only new containers works.

But what can I do on the old server... I need the data ...
 
I have the same issue. I did an `apt-get update; apt-get upgrade` on 5.1 and I get this exact issue. All VMs and CTs can no longer find their virtual drives.

Code:
lvscan
  ACTIVE            '/dev/pve/swap' [7.00 GiB] inherit
  ACTIVE            '/dev/pve/root' [37.00 GiB] inherit
  inactive          '/dev/pve/data' [1.13 TiB] inherit
  inactive          '/dev/pve/vm-100-disk-1' [8.00 GiB] inherit
  inactive          '/dev/pve/snap_vm-100-disk-1_Ideal_Start' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-101-disk-1' [18.00 GiB] inherit
  inactive          '/dev/pve/vm-102-disk-2' [4.00 MiB] inherit
  inactive          '/dev/pve/vm-102-disk-1' [32.00 GiB] inherit
  inactive          '/dev/pve/vm-103-disk-1' [12.00 GiB] inherit
  inactive          '/dev/pve/vm-103-disk-2' [4.00 MiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-1_OriginalInstall' [32.00 GiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-2_OriginalInstall' [4.00 MiB] inherit
  inactive          '/dev/pve/vm-105-disk-1' [40.00 GiB] inherit
  inactive          '/dev/pve/vm-106-disk-1' [100.00 GiB] inherit
  inactive          '/dev/pve/vm-107-disk-1' [16.00 GiB] inherit
  ACTIVE            '/dev/pve/data_meta0' [92.00 MiB] inherit
  inactive          '/dev/pve/vm-110-disk-1' [64.00 GiB] inherit
  inactive          '/dev/pve/vm-104-disk-1' [32.00 GiB] inherit

Tried to activate it.

Code:
lvchange -a y pve/data
  Check of pool pve/data failed (status:1). Manual repair required!

Tried to repair it.

Code:
lvconvert --repair pve/data
  Using default stripesize 64.00 KiB.
  Volume group "pve" has insufficient free space (0 extents): 23 required

Tried to resize it (another time it was telling me there wasn't enough free space to do this).

Code:
lvreduce -L -8G pve/data
  Thin pool volumes pve/data_tdata cannot be reduced in size yet.

These were the initial packages I upgraded to produce this error

Code:
cat /var/log/dpkg.log | grep upgrade
2018-05-24 20:38:48 upgrade base-files:amd64 9.9+deb9u3 9.9+deb9u4
2018-05-24 20:38:50 upgrade bsdutils:amd64 1:2.29.2-1 1:2.29.2-1+deb9u1
2018-05-24 20:38:51 upgrade util-linux:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:38:54 upgrade mount:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:38:55 upgrade ncurses-bin:amd64 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:38:58 upgrade libperl5.24:amd64 5.24.1-3+deb9u2 5.24.1-3+deb9u3
2018-05-24 20:39:00 upgrade perl:amd64 5.24.1-3+deb9u2 5.24.1-3+deb9u3
2018-05-24 20:39:00 upgrade perl-base:amd64 5.24.1-3+deb9u2 5.24.1-3+deb9u3
2018-05-24 20:39:02 upgrade perl-modules-5.24:all 5.24.1-3+deb9u2 5.24.1-3+deb9u3
2018-05-24 20:39:04 upgrade libc6-dev:amd64 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:05 upgrade libc-dev-bin:amd64 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:06 upgrade linux-libc-dev:amd64 4.9.65-3+deb9u2 4.9.88-1+deb9u1
2018-05-24 20:39:07 upgrade libquadmath0:amd64 6.3.0-18 6.3.0-18+deb9u1
2018-05-24 20:39:08 upgrade cpp-6:amd64 6.3.0-18 6.3.0-18+deb9u1
2018-05-24 20:39:09 upgrade gcc-6-base:amd64 6.3.0-18 6.3.0-18+deb9u1
2018-05-24 20:39:10 upgrade libgcc1:amd64 1:6.3.0-18 1:6.3.0-18+deb9u1
2018-05-24 20:39:11 upgrade libgfortran3:amd64 6.3.0-18 6.3.0-18+deb9u1
2018-05-24 20:39:12 upgrade libstdc++6:amd64 6.3.0-18 6.3.0-18+deb9u1
2018-05-24 20:39:14 upgrade libc6:amd64 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:16 upgrade libc-bin:amd64 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:18 upgrade ncurses-base:all 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:39:19 upgrade dbus:amd64 1.10.24-0+deb9u1 1.10.26-0+deb9u1
2018-05-24 20:39:20 upgrade libdbus-1-3:amd64 1.10.24-0+deb9u1 1.10.26-0+deb9u1
2018-05-24 20:39:21 upgrade libapparmor1:amd64 2.11.0-3 2.11.0-3+deb9u2
2018-05-24 20:39:22 upgrade systemd-sysv:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:23 upgrade libpam-systemd:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:23 upgrade libsystemd0:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:25 upgrade systemd:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:27 upgrade udev:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:29 upgrade libudev1:amd64 232-25+deb9u1 232-25+deb9u2
2018-05-24 20:39:30 upgrade libuuid1:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:39:31 upgrade libblkid1:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:39:32 upgrade libncurses5:amd64 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:39:33 upgrade libtinfo5:amd64 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:39:34 upgrade libncursesw5:amd64 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:39:35 upgrade libprocps6:amd64 2:3.3.12-3 2:3.3.12-3+deb9u1
2018-05-24 20:39:36 upgrade procps:amd64 2:3.3.12-3 2:3.3.12-3+deb9u1
2018-05-24 20:39:37 upgrade libmount1:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:39:38 upgrade cron:amd64 3.0pl1-128+b1 3.0pl1-128+deb9u1
2018-05-24 20:39:39 upgrade libsmbclient:amd64 2:4.5.12+dfsg-2+deb9u1 2:4.5.12+dfsg-2+deb9u2
2018-05-24 20:39:40 upgrade samba-libs:amd64 2:4.5.12+dfsg-2+deb9u1 2:4.5.12+dfsg-2+deb9u2
2018-05-24 20:39:42 upgrade libwbclient0:amd64 2:4.5.12+dfsg-2+deb9u1 2:4.5.12+dfsg-2+deb9u2
2018-05-24 20:39:42 upgrade smbclient:amd64 2:4.5.12+dfsg-2+deb9u1 2:4.5.12+dfsg-2+deb9u2
2018-05-24 20:39:43 upgrade samba-common:all 2:4.5.12+dfsg-2+deb9u1 2:4.5.12+dfsg-2+deb9u2
2018-05-24 20:39:44 upgrade libcups2:amd64 2.2.1-8 2.2.1-8+deb9u1
2018-05-24 20:39:45 upgrade openssh-sftp-server:amd64 1:7.4p1-10+deb9u2 1:7.4p1-10+deb9u3
2018-05-24 20:39:46 upgrade libssl1.0.2:amd64 1.0.2l-2+deb9u2 1.0.2l-2+deb9u3
2018-05-24 20:39:47 upgrade openssh-server:amd64 1:7.4p1-10+deb9u2 1:7.4p1-10+deb9u3
2018-05-24 20:39:48 upgrade openssh-client:amd64 1:7.4p1-10+deb9u2 1:7.4p1-10+deb9u3
2018-05-24 20:39:49 upgrade ssh:all 1:7.4p1-10+deb9u2 1:7.4p1-10+deb9u3
2018-05-24 20:39:50 upgrade libfdisk1:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:39:51 upgrade libsmartcols1:amd64 2.29.2-1 2.29.2-1+deb9u1
2018-05-24 20:39:52 upgrade multiarch-support:amd64 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:53 upgrade tzdata:all 2017c-0+deb9u1 2018c-0+deb9u1
2018-05-24 20:39:54 upgrade isc-dhcp-client:amd64 4.3.5-3 4.3.5-3+deb9u1
2018-05-24 20:39:55 upgrade isc-dhcp-common:amd64 4.3.5-3 4.3.5-3+deb9u1
2018-05-24 20:39:56 upgrade libssl1.1:amd64 1.1.0f-3+deb9u1 1.1.0f-3+deb9u2
2018-05-24 20:39:57 upgrade wget:amd64 1.18-5+deb9u1 1.18-5+deb9u2
2018-05-24 20:39:58 upgrade libc-l10n:all 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:39:59 upgrade locales:all 2.24-11+deb9u1 2.24-11+deb9u3
2018-05-24 20:40:01 upgrade ncurses-term:all 6.0+20161126-1+deb9u1 6.0+20161126-1+deb9u2
2018-05-24 20:40:02 upgrade reportbug:all 7.1.7 7.1.7+deb9u1
2018-05-24 20:40:03 upgrade python3-reportbug:all 7.1.7 7.1.7+deb9u1
2018-05-24 20:40:04 upgrade libcurl3-gnutls:amd64 7.52.1-5+deb9u4 7.52.1-5+deb9u6
2018-05-24 20:40:05 upgrade libicu57:amd64 57.1-6+deb9u1 57.1-6+deb9u2
2018-05-24 20:40:06 upgrade libvorbisenc2:amd64 1.3.5-4 1.3.5-4+deb9u2
2018-05-24 20:40:07 upgrade libvorbis0a:amd64 1.3.5-4 1.3.5-4+deb9u2
2018-05-24 20:40:08 upgrade openssl:amd64 1.1.0f-3+deb9u1 1.1.0f-3+deb9u2
2018-05-24 20:40:09 upgrade libapparmor-perl:amd64 2.11.0-3 2.11.0-3+deb9u2
2018-05-24 20:40:10 upgrade apparmor:amd64 2.11.0-3 2.11.0-3+deb9u2
2018-05-24 20:40:11 upgrade postfix-sqlite:amd64 3.1.6-0+deb9u1 3.1.8-0+deb9u1
2018-05-24 20:40:12 upgrade postfix:amd64 3.1.6-0+deb9u1 3.1.8-0+deb9u1

Some post somewhere said that the sources.list should have the other source uncommented to fix it so I upgraded those as well but it didn't change anything:

Code:
2018-05-24 22:32:49 upgrade iproute2:amd64 4.10.0-1 4.13.0-3
2018-05-24 22:32:50 upgrade libcorosync-common4:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:51 upgrade libcfg6:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:52 upgrade libcmap4:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:52 upgrade libcpg4:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:53 upgrade libquorum5:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:54 upgrade libtotem-pg5:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:56 upgrade libvotequorum8:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:57 upgrade corosync:amd64 2.4.2-pve3 2.4.2-pve5
2018-05-24 22:32:58 upgrade libuutil1linux:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:32:59 upgrade libnvpair1linux:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:32:59 upgrade libpve-access-control:amd64 5.0-7 5.0-8
2018-05-24 22:33:00 upgrade libpve-guest-common-perl:all 2.0-14 2.0-16
2018-05-24 22:33:01 upgrade librados2-perl:amd64 1.0-4 1.0-5
2018-05-24 22:33:02 upgrade libzpool2linux:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:33:02 upgrade libzfs2linux:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:33:03 upgrade lxcfs:amd64 2.0.8-1 3.0.0-1
2018-05-24 22:33:04 upgrade lxc-pve:amd64 2.1.1-2 3.0.0-3
2018-05-24 22:33:05 upgrade pve-firmware:all 2.0-3 2.0-4
2018-05-24 22:33:11 upgrade pve-ha-manager:amd64 2.0-4 2.0-5
2018-05-24 22:33:12 upgrade pve-kernel-4.13.13-2-pve:amd64 4.13.13-32 4.13.13-33
2018-05-24 22:33:24 upgrade pve-xtermjs:amd64 1.0-2 1.0-5
2018-05-24 22:33:25 upgrade spl:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:33:26 upgrade zfsutils-linux:amd64 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:33:27 upgrade zfs-initramfs:all 0.7.3-pve1~bpo9 0.7.8-pve1~bpo9
2018-05-24 22:33:28 upgrade pve-docs:all 5.1-12 5.2-4
2018-05-24 22:33:29 upgrade pve-qemu-kvm:amd64 2.9.1-5 2.11.1-5

I followed some instructions for downgrading but found that the ProxMox apt repositories no longer stored the older versions to downgrade to.

`apt-get dist-upgrade` says there are no upgrades.

Code:
qm start 107
kvm: -drive file=/dev/pve/vm-107-disk-1,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/pve/vm-107-disk-1': No such file or directory
start failed: command '/usr/bin/kvm -id 107 -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/107.pid -daemonize-smbios 'type=1,uuid=5e8ead06-cf2e-4b92-9e27-5fb397fe34a2' -name SugarCRM -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/107.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 2048 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:d751b3ed7cc' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-107-disk-1,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=DA:D3:A9:9B:E6:AF,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300''
failed: exit code 1

Here's the systemctl status:

Code:
systemctl status pve-container@110.service
● pve-container@110.service - PVE LXC Container: 110
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-05-25 02:11:52 EDT; 17min ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 2192 ExecStart=/usr/bin/lxc-start -n 110 (code=exited, status=1/FAILURE)

May 25 02:11:52 proxmox systemd[1]: Starting PVE LXC Container: 110...
May 25 02:11:52 proxmox lxc-start[2192]: lxc-start: 110: lxccontainer.c: wait_on_daemonized_start:
May 25 02:11:52 proxmox lxc-start[2192]: The container failed to start.
May 25 02:11:52 proxmox lxc-start[2192]: To get more details, run the container in foreground mode.
May 25 02:11:52 proxmox lxc-start[2192]: Additional information can be obtained by setting the --lo
May 25 02:11:52 proxmox systemd[1]: pve-container@110.service: Control process exited, code=exited
May 25 02:11:52 proxmox systemd[1]: Failed to start PVE LXC Container: 110.
May 25 02:11:52 proxmox systemd[1]: pve-container@110.service: Unit entered failed state.
May 25 02:11:52 proxmox systemd[1]: pve-container@110.service: Failed with result 'exit-code'.

At some point I saw this but I don't remember where:

Code:
AVC apparmor="DENIED" operation="mount"
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!