On 12/4/18 10:27 AM, lord_Niedzwiedz wrote: > root@hayne:~# systemctl start pve-container@108 > Job for pve-container@108.service failed because the control process exited > with error code. > See "systemctl status pve-container@108.service" and "journalctl -xe" for > details. > > root@hayne:~# systemctl status pve-container@108.service > ● pve-container@108.service - PVE LXC Container: 108 > Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor > preset: enabled) > Active: failed (Result: exit-code) since Tue 2018-12-04 10:25:45 CET; 12s > ago > Docs: man:lxc-start > man:lxc > man:pct > Process: 9268 ExecStart=/usr/bin/lxc-start -n 108 (code=exited, > status=1/FAILURE) > > Dec 04 10:25:44 hayne systemd[1]: Starting PVE LXC Container: 108... > Dec 04 10:25:45 hayne systemd[1]: pve-container@108.service: Control process > exited, code=exited status=1 > Dec 04 10:25:45 hayne systemd[1]: Failed to start PVE LXC Container: 108. > Dec 04 10:25:45 hayne systemd[1]: pve-container@108.service: Unit entered > failed state. > Dec 04 10:25:45 hayne systemd[1]: pve-container@108.service: Failed with > result 'exit-code'. >
How about at least some minimal context and more telling logs? ^^ # lxc-start -n 108 -l DEBUG -o ct108-start.log optionally add the "-F" flag to start the CT in foreground.. cheers, Thomas _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
