cannot start LXC

Y

yarii

Renowned Member
Mar 24, 2014
148
8
83
newest proxmox 6.x

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


The I type:

systemctl status pve-container@444.service

Apr 05 10:51:57 vps1 systemd[1]: Starting PVE LXC Container: 444...
Apr 05 10:51:58 vps1 lxc-start[2480]: lxc-start: 444: lxccontainer.c: wait_on_daemonized_start: 874 Received container state "ABORTING" instead of "RUN
Apr 05 10:51:58 vps1 lxc-start[2480]: lxc-start: 444: tools/lxc_start.c: main: 329 The container failed to start
Apr 05 10:51:58 vps1 lxc-start[2480]: lxc-start: 444: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Apr 05 10:51:58 vps1 lxc-start[2480]: lxc-start: 444: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and
Apr 05 10:51:58 vps1 systemd[1]: pve-container@444.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 10:51:58 vps1 systemd[1]: pve-container@444.service: Killing process 2572 (lxc-start) with signal SIGKILL.
Apr 05 10:51:58 vps1 systemd[1]: pve-container@444.service: Failed with result 'exit-code'.
Apr 05 10:51:58 vps1 systemd[1]: Failed to start PVE LXC Container: 444.


What to do with that?
 
This comes after restoring backup from proxmox 5.x with unprivileged=1.

I did:
zfs send | ssh zfs receive
copy config from /etc/pve/lxc/444.conf to new serwer.
pct start 444

Workaround works.
 
Container works but

pct list get an error...

can't open '/sys/fs/cgroup/memory/lxc/444/ns/memory.stat' - No such file or directory

how to live?
 
Hi,
I’m having the exact same issue, restoring containers for 5.X to a new 6.1-8 Proxmox, on a fresh Debian 10

# uname -a
Linux kimsufi 5.3.18-3-pve #1 SMP PVE 5.3.18-3 (Tue, 17 Mar 2020 16:33:19 +0100) x86_64 GNU/Linux


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



# journalctl -xe
Apr 11 16:48:03 kimsufi pct[10235]: <root@pam> starting task UPID:kimsufi:0000280E:0003E383:5E91D8A3:vzstart:103:root@pam:
Apr 11 16:48:03 kimsufi pct[10254]: starting CT 103: UPID:kimsufi:0000280E:0003E383:5E91D8A3:vzstart:103:root@pam:
Apr 11 16:48:03 kimsufi systemd[1]: Starting PVE LXC Container: 103...
-- Subject: A start job for unit pve-container@103.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@103.service has begun execution.
--
-- The job identifier is 3834.
Apr 11 16:48:04 kimsufi systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Apr 11 16:48:04 kimsufi systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 3760.
Apr 11 16:48:06 kimsufi kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null)
Apr 11 16:48:07 kimsufi audit[10315]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-start" name="lxc-103_</var/lib/lxc>" p
Apr 11 16:48:07 kimsufi kernel: audit: type=1400 audit(1586616487.439:22): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-start
Apr 11 16:48:07 kimsufi systemd-udevd[10247]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 11 16:48:07 kimsufi systemd-udevd[10246]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 11 16:48:07 kimsufi systemd-udevd[10247]: Using default interface naming scheme 'v240'.
Apr 11 16:48:07 kimsufi systemd-udevd[10246]: Using default interface naming scheme 'v240'.
Apr 11 16:48:07 kimsufi systemd-udevd[10246]: Could not generate persistent MAC address for vethNDJUAJ: No such file or directory
Apr 11 16:48:10 kimsufi lxc-start[10257]: lxc-start: 103: lxccontainer.c: wait_on_daemonized_start: 874 Received container state "ABORTING" instead of "RUNNING"
Apr 11 16:48:10 kimsufi lxc-start[10257]: lxc-start: 103: tools/lxc_start.c: main: 329 The container failed to start
Apr 11 16:48:10 kimsufi lxc-start[10257]: lxc-start: 103: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Apr 11 16:48:10 kimsufi lxc-start[10257]: lxc-start: 103: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Apr 11 16:48:10 kimsufi systemd[1]: pve-container@103.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit pve-container@103.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Apr 11 16:48:10 kimsufi systemd[1]: pve-container@103.service: Killing process 10264 (lxc-start) with signal SIGKILL.
Apr 11 16:48:10 kimsufi systemd[1]: pve-container@103.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@103.service has entered the 'failed' state with result 'exit-code'.
Apr 11 16:48:10 kimsufi systemd[1]: Failed to start PVE LXC Container: 103.
-- Subject: A start job for unit pve-container@103.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@103.service has finished with a failure.
--
-- The job identifier is 3834 and the job result is failed.
Apr 11 16:48:10 kimsufi pct[10254]: command 'systemctl start pve-container@103' failed: exit code 1
Apr 11 16:48:10 kimsufi pvestatd[1396]: unable to get PID for CT 103 (not running?)
Apr 11 16:48:10 kimsufi pct[10235]: <root@pam> end task UPID:kimsufi:0000280E:0003E383:5E91D8A3:vzstart:103:root@pam: command 'systemctl start pve-container@103' failed: exit code 1



Your workaround doesn’t works for me, the /etc/pve/lxc/103.conf file is already the same (from 5.X to 6.X)

Best


------------------
Edit :
I found the issue, on the last installation (the one on 5.X), my interface was named "vmbr2". On my fresh installation, I decided to name this one "vmbr1". This was a bad idea...
 
Last edited:
I did also some dirty thing after that .... I created that not-existent directories and files manualy using mkdir and touch.

There are several bugs in proxmox or LXC ... with that but I cannot isolate that.
 
You must log in or register to reply here.
Top Bottom