LCX-Container starten nicht nach Update auf 4.15.17-3-pve #1 SMP PVE 4.15.17-13

MartinZie

New Member
Jun 26, 2018
3
0
1
43
Hallo,

wir haben heute ein paar Server von "4.15.17-2-pve #1 SMP PVE 4.15.17-10" auf "4.15.17-3-pve #1 SMP PVE 4.15.17-13" aktualisiert- ab dem Neustart können kein lxc-Container gestartet werden.

Meldung:
Job for pve-container@106.service failed because the control process exited with error code.
See "systemctl status pve-container@106.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@106' failed: exit code 1

pve-container@111.service - PVE LXC Container: 111
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-06-26 07:07:06 CEST; 4h 14min ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 7310 ExecStart=/usr/bin/lxc-start -n 111 (code=exited, status=1/FAILURE)

Jun 26 07:07:05 ariel4 systemd[1]: Starting PVE LXC Container: 111...
Jun 26 07:07:06 ariel4 lxc-start[7310]: lxc-start: 111: lxccontainer.c: wait_on_daemonized_start: 824 Received container state "ABORTING" instead of "RUNNING"
Jun 26 07:07:06 ariel4 lxc-start[7310]: The container failed to start.
Jun 26 07:07:06 ariel4 lxc-start[7310]: To get more details, run the container in foreground mode.
Jun 26 07:07:06 ariel4 lxc-start[7310]: Additional information can be obtained by setting the --logfile and --logpriority options.
Jun 26 07:07:06 ariel4 systemd[1]: pve-container@111.service: Control process exited, code=exited status=1
Jun 26 07:07:06 ariel4 systemd[1]: pve-container@111.service: Killing process 7312 (lxc-start) with signal SIGKILL.
Jun 26 07:07:06 ariel4 systemd[1]: Failed to start PVE LXC Container: 111.
Jun 26 07:07:06 ariel4 systemd[1]: pve-container@111.service: Unit entered failed state.
Jun 26 07:07:06 ariel4 systemd[1]: pve-container@111.service: Failed with result 'exit-code'.

Hat Jemand zufällig eine Idee?
Danke!

Gruß
MartinZ