Hello,
after a manually stop of a container it isn't possible to start it again.
Job for pve-container@386.service failed because the control process exited with error code.
See "systemctl status pve-container@386.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@386' failed: exit code 1
after a manually stop of a container it isn't possible to start it again.
Job for pve-container@386.service failed because the control process exited with error code.
See "systemctl status pve-container@386.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@386' failed: exit code 1
Code:
proxmox-ve: 5.2-2 (running kernel: 4.13.13-6-pve)
pve-manager: 5.2-3 (running version: 5.2-3/785ba980)
pve-kernel-4.15: 5.2-3
pve-kernel-4.13: 5.1-45
pve-kernel-4.15.17-3-pve: 4.15.17-13
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.13.16-3-pve: 4.13.16-49
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.6-1-pve: 4.4.6-48
corosync: 2.4.2-pve5
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-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-34
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-12
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9
Code:
systemctl status pve-container@386.service
● pve-container@386.service - PVE LXC Container: 386
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-07-20 21:01:23 CEST; 7min ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 30878 ExecStart=/usr/bin/lxc-start -n 386 (code=exited, status=1/FAILURE)
Jul 20 21:01:22 host systemd[1]: Starting PVE LXC Container: 386...
Jul 20 21:01:23 host lxc-start[30878]: lxc-start: 386: lxccontainer.c: wait_on_daemonized_start: 815 No such file or directory - Failed to receive the container state
Jul 20 21:01:23 host lxc-start[30878]: The container failed to start.
Jul 20 21:01:23 host lxc-start[30878]: To get more details, run the container in foreground mode.
Jul 20 21:01:23 host lxc-start[30878]: Additional information can be obtained by setting the --logfile and --logpriority options.
Jul 20 21:01:23 host systemd[1]: pve-container@386.service: Control process exited, code=exited status=1
Jul 20 21:01:23 host systemd[1]: Failed to start PVE LXC Container: 386.
Jul 20 21:01:23 host systemd[1]: pve-container@386.service: Unit entered failed state.
Jul 20 21:01:23 host systemd[1]: pve-container@386.service: Failed with result 'exit-code'.
