LXC Fails To Start

I

infinityM

Well-Known Member
Dec 7, 2019
179
1
58
31
Hey Guys,

I have a LXC container that keeps failing to start...

All others have started successfully except for this one.
I get a timeout message on the container start then it just fails.

root@c1:~# systemctl status pve-container@106.service
● pve-container@106.service - PVE LXC Container: 106
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2020-05-04 08:05:17 SAST; 13min ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 3053 ExecStart=/usr/bin/lxc-start -n 106 (code=killed, signal=TERM)

May 04 08:03:47 c1 systemd[1]: Starting PVE LXC Container: 106...
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Start operation timed out. Terminating.
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Control process exited, code=killed, status=15/TERM
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Killing process 3064 (lxc-start) with signal SIGKILL.
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Killing process 3065 (lxc-pve-prestar) with signal SIGKILL.
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Killing process 3106 (mount) with signal SIGKILL.
May 04 08:05:17 c1 systemd[1]: pve-container@106.service: Failed with result 'timeout'.
May 04 08:05:17 c1 systemd[1]: Failed to start PVE LXC Container: 106.

I am not sure why this lxc fails to start though...
I have migrated it to another server to test, and I have updated all servers to latest proxmox and other repo updates.
I have also rebooted the server, still no success...

ANY ASSISTANCE WOULD BE AMAZING PLZ D:
 
Not sure if this helps... I have the journalctl -xe aswell

--
-- The job identifier is 2813.
May 04 08:23:01 c1 pve-ha-lrm[13180]: Task 'UPID:c1:0000337F:0001C8B5:5EAFB46B:vzstart:106:root@pam:' still active, waiting
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Start operation timed out. Terminating.
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Control process exited, code=killed, status=15/TERM
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit pve-container@106.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 15.
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Killing process 13193 (lxc-start) with signal SIGKILL.
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Killing process 13194 (lxc-pve-prestar) with signal SIGKILL.
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Killing process 13196 (mount) with signal SIGKILL.
May 04 08:23:01 c1 kernel: EXT4-fs warning (device rbd1): ext4_multi_mount_protect:324: MMP startup interrupted, failing mount
May 04 08:23:01 c1 pvestatd[1697]: unable to get PID for CT 106 (not running?)
May 04 08:23:01 c1 systemd[1]: pve-container@106.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@106.service has entered the 'failed' state with result 'timeout'.
May 04 08:23:01 c1 systemd[1]: Failed to start PVE LXC Container: 106.
-- Subject: A start job for unit pve-container@106.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@106.service has finished with a failure.
--
-- The job identifier is 2737 and the job result is failed.
May 04 08:23:01 c1 pve-ha-lrm[13183]: command 'systemctl start pve-container@106' failed: exit code 1
May 04 08:23:01 c1 pve-ha-lrm[13180]: <root@pam> end task UPID:c1:0000337F:0001C8B5:5EAFB46B:vzstart:106:root@pam: command 'systemct
May 04 08:23:01 c1 pve-ha-lrm[13180]: unable to start service ct:106
 
Hi,
could you post the output of pveversion -v and the log file produced by running the following command?
Code: 
lxc-start -n 106 -F -l DEBUG -o ~/lxc-106.log
 
Fabian_E said:
Hi,
could you post the output of pveversion -v and the log file produced by running the following command?
Code: 
lxc-start -n 106 -F -l DEBUG -o ~/lxc-106.log
Click to expand...


hey Fabian,

Thank's for the response.

The pveversion -v response is:

root@c1:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.9-pve1
ceph-fuse: 14.2.9-pve1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

And the lxc-start -n 106 -F -l DEBUG -o ~/lxc-106.log response is:

lxc-start: 106: conf.c: run_buffer: 352 Script exited with status 255
lxc-start: 106: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "106"
lxc-start: 106: start.c: __lxc_start: 2032 Failed to initialize container "106"
Segmentation fault
 
infinityM said:
And the lxc-start -n 106 -F -l DEBUG -o ~/lxc-106.log response is:

lxc-start: 106: conf.c: run_buffer: 352 Script exited with status 255
lxc-start: 106: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "106"
lxc-start: 106: start.c: __lxc_start: 2032 Failed to initialize container "106"
Segmentation fault
Click to expand...

The command should create a file lxc-106.log in your home directory. And that file normally contains more details.
 
Fabian_E said:
The command should create a file lxc-106.log in your home directory. And that file normally contains more details.
Click to expand...

Hey bud, I have pasted it below :)

root@c1:~# cat lxc-106.log
lxc-start 106 20200504162505.727 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 106 20200504162505.728 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 106 20200504162505.733 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 106 20200504162505.733 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "[all]"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "kexec_load errno 1"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "open_by_handle_at errno 1"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "init_module errno 1"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "finit_module errno 1"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "keyctl errno 38"
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for keyctl action 327718(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for keyctl action 327718(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for keyctl action 327718(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for keyctl action 327718(errno)
lxc-start 106 20200504162505.734 INFO seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context
lxc-start 106 20200504162505.734 INFO conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "106", config section "lxc"
lxc-start 106 20200504162506.412 DEBUG conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start produced output: CT is locked (backup)

lxc-start 106 20200504162506.421 ERROR conf - conf.c:run_buffer:352 - Script exited with status 255
lxc-start 106 20200504162506.421 ERROR start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "106"
lxc-start 106 20200504162506.422 ERROR start - start.c:__lxc_start:2032 - Failed to initialize container "106
 
infinityM said:
lxc-start 106 20200504162505.734 INFO conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "106", config section "lxc"
lxc-start 106 20200504162506.412 DEBUG conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start produced output: CT is locked (backup)
Click to expand...

Was there a failed backup job for this container?
Please make sure that there is no currently running backup job for the container and use pct unlock 106 to remove the lock.
 
Fabian_E said:
Was there a failed backup job for this container?
Please make sure that there is no currently running backup job for the container and use pct unlock 106 to remove the lock.
Click to expand...

I don't understand what went wrong.... I tried to unlock it before also, both times now and before, it said there is no lock.
When I started it up now, it booted up...

I'm completely at a los... But thank you very very much!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom