Hi,
After upgrade to Proxmox 5.1 from 4.4, our container can not started.
Previously before upgrading everything work fine and never have problem.
Here is the error that we have from systemctl status pve-container[ID]
# systemctl status pve-container@109.service
● pve-container@109.service - PVE LXC Container: 109
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2017-11-28 09:53:06 WITA; 2h 53min ago
Docs: man:lxc-start
man:lxc
man
ct
Process: 2872 ExecStart=/usr/bin/lxc-start -n 109 (code=killed, signal=TERM)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/system-pve\x2dcontainer.slice/pve-container@109.service
└─2874 [lxc monitor] /var/lib/lxc 109
Nov 28 09:51:36 pve1 systemd[1]: Starting PVE LXC Container: 109...
Nov 28 09:52:01 pve1 ovs-vsctl[3298]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth109i0
Nov 28 09:52:01 pve1 ovs-vsctl[3299]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln109i0
Nov 28 09:52:01 pve1 ovs-vsctl[3300]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl add-port vmbr0 veth109i0 tag=[VLANtag]
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Start operation timed out. Terminating.
Nov 28 09:53:06 pve1 systemd[1]: Failed to start PVE LXC Container: 109.
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Unit entered failed state.
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Failed with result 'timeout'.
Our proxmox current version
# pveversion -v
proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.7.0-2
Please help
update:
after we reboot the host, container is starting again.
After upgrade to Proxmox 5.1 from 4.4, our container can not started.
Previously before upgrading everything work fine and never have problem.
Here is the error that we have from systemctl status pve-container[ID]
# systemctl status pve-container@109.service
● pve-container@109.service - PVE LXC Container: 109
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2017-11-28 09:53:06 WITA; 2h 53min ago
Docs: man:lxc-start
man:lxc
man
ctProcess: 2872 ExecStart=/usr/bin/lxc-start -n 109 (code=killed, signal=TERM)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/system-pve\x2dcontainer.slice/pve-container@109.service
└─2874 [lxc monitor] /var/lib/lxc 109
Nov 28 09:51:36 pve1 systemd[1]: Starting PVE LXC Container: 109...
Nov 28 09:52:01 pve1 ovs-vsctl[3298]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth109i0
Nov 28 09:52:01 pve1 ovs-vsctl[3299]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln109i0
Nov 28 09:52:01 pve1 ovs-vsctl[3300]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl add-port vmbr0 veth109i0 tag=[VLANtag]
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Start operation timed out. Terminating.
Nov 28 09:53:06 pve1 systemd[1]: Failed to start PVE LXC Container: 109.
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Unit entered failed state.
Nov 28 09:53:06 pve1 systemd[1]: pve-container@109.service: Failed with result 'timeout'.
Our proxmox current version
# pveversion -v
proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.7.0-2
Please help
update:
after we reboot the host, container is starting again.
Last edited: