Today I made upgraded my proxmox host pve and unfortunately after upgrade process one of my LXC container stopped working.
Now I'm struggling how to solved trhis issue, but I'm not very familiar with proxmox .....
Now I'm struggling how to solved trhis issue, but I'm not very familiar with proxmox .....
Code:
Linux pve 4.16.0-041600-generic #201804012230 SMP Sun Apr 1 22:31:39 UTC 2018 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@pve:~# systemctl status lxc@100.service
● lxc@100.service - LXC Container: 100
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/lxc@.service.d
└─pve-reboot.conf
Active: inactive (dead)
Docs: man:lxc-start
man:lxc
root@pve:~# journalctl -xe
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Oct 02 14:26:37 pve pvedaemon[1742]: <root@pam> end task UPID:pve:0000126E:0002A1B9:5D949743:vncshell::root@pam: OK
Oct 02 14:26:38 pve pvedaemon[4818]: starting CT 100: UPID:pve:000012D2:0002B8FC:5D94977E:vzstart:100:root@pam:
Oct 02 14:26:38 pve pvedaemon[1743]: <root@pam> starting task UPID:pve:000012D2:0002B8FC:5D94977E:vzstart:100:root@pam:
Oct 02 14:26:38 pve systemd[1]: Starting PVE LXC Container: 100...
-- Subject: Unit pve-container@100.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@100.service has begun starting up.
Oct 02 14:26:39 pve kernel: EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null)
Oct 02 14:26:40 pve audit[4842]: AVC apparmor="STATUS" info="failed to unpack end of profile" error=-71 profile="unconfined" name="lxc-100_</var/lib/lxc>" pid=4842 comm="
Oct 02 14:26:40 pve kernel: audit: type=1400 audit(1570019200.836:11): apparmor="STATUS" info="failed to unpack end of profile" error=-71 profile="unconfined" name="lxc-1
Oct 02 14:26:41 pve lxc-start[4820]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Oct 02 14:26:41 pve lxc-start[4820]: lxc-start: 100: tools/lxc_start.c: main: 330 The container failed to start
Oct 02 14:26:41 pve lxc-start[4820]: lxc-start: 100: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Oct 02 14:26:41 pve lxc-start[4820]: lxc-start: 100: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority option
Oct 02 14:26:41 pve pvedaemon[1743]: unable to get PID for CT 100 (not running?)
Oct 02 14:26:41 pve systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Oct 02 14:26:41 pve pvedaemon[4818]: command 'systemctl start pve-container@100' failed: exit code 1
Oct 02 14:26:41 pve systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: Unit pve-container@100.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@100.service has failed.
--
-- The result is failed.
Oct 02 14:26:41 pve pvedaemon[1743]: <root@pam> end task UPID:pve:000012D2:0002B8FC:5D94977E:vzstart:100:root@pam: command 'systemctl start pve-container@100' failed: exi
Oct 02 14:26:41 pve systemd[1]: pve-container@100.service: Unit entered failed state.
Oct 02 14:26:41 pve systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Oct 02 14:26:41 pve pvedaemon[4845]: starting termproxy UPID:pve:000012ED:0002B9DC:5D949781:vncshell::root@pam:
Oct 02 14:26:41 pve pvedaemon[1744]: <root@pam> starting task UPID:pve:000012ED:0002B9DC:5D949781:vncshell::root@pam:
Oct 02 14:26:41 pve pvedaemon[1742]: <root@pam> successful auth for user 'root@pam'
Oct 02 14:26:41 pve login[4850]: pam_unix(login:session): session opened for user root by root(uid=0)
Oct 02 14:26:41 pve login[4855]: ROOT LOGIN on '/dev/pts/0
you can always verify with "uname -a" that you are not currently running the kernel you are about to remove..