[SOLVED] No more CT or VM could launch after a crash

S

Singman

Active Member
Sep 13, 2019
20
0
41
57
Hi,
My Proxmox server crashed due to hardware failure. I fixed it and started it again. But now, CT dont start nor VM.

root@pve:~# systemctl status pve-container@106
● pve-container@106.service - PVE LXC Container: 106
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-09-13 23:11:28 CEST; 32min ago
Docs: man:lxc-start
man: lxc
man: pct
Process: 3779 ExecStart=/usr/bin/lxc-start -n 106 (code=exited, status=1/FAILURE)

Sep 13 23:46:18 pve systemd[1]: Starting PVE LXC Container: 106...
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 330 The container failed to start
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Control process exited, code=exited status=1
Sep 13 23:46:19 pve systemd[1]: Failed to start PVE LXC Container: 106.
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Unit entered failed state.
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Failed with result 'exit-code'.

root@pve:~# journalctl -u pve-container@106
-- Logs begin at Fri 2019-09-13 22:56:26 CEST, end at Fri 2019-09-13 23:45:01 CEST. --
Sep 13 23:46:18 pve systemd[1]: Starting PVE LXC Container: 106...
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 330 The container failed to start
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Sep 13 23:46:19 pve lxc-start[7829]: lxc-start: 106: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Control process exited, code=exited status=1
Sep 13 23:46:19 pve systemd[1]: Failed to start PVE LXC Container: 106.
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Unit entered failed state.
Sep 13 23:46:19 pve systemd[1]: pve-container@106.service: Failed with result 'exit-code'.

root@pve:~# lxc-start -lDEBUG -F -n 106 -o log.txt
lxc-start: 106: conf.c: run_buffer: 335 Script exited with status 13
lxc-start: 106: start.c: lxc_init: 861 Failed to run lxc.hook.pre-start for container "106"
lxc-start: 106: start.c: __lxc_start: 1944 Failed to initialize container "106"
lxc-start: 106: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: 106: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
 
root@pve:~# cat log.txt
lxc-start 106 20190913215028.646 INFO confile - confile.c:set_config_idmaps:1673 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 106 20190913215028.646 INFO confile - confile.c:set_config_idmaps:1673 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 106 20190913215028.646 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 106 20190913215028.646 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"
lxc-start 106 20190913215028.646 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20190913215028.646 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "keyctl errno 38"
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for keyctl action 327718(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for keyctl action 327718(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for keyctl action 327718(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for keyctl action 327718(errno)
lxc-start 106 20190913215028.647 INFO seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 106 20190913215028.647 INFO conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "106", config section "lxc"
lxc-start 106 20190913215029.280 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start with output: volume 'FreenasVM:106/vm-106-disk-0.raw' does not exist

lxc-start 106 20190913215029.288 ERROR conf - conf.c:run_buffer:335 - Script exited with status 13
lxc-start 106 20190913215029.288 ERROR start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "106"
lxc-start 106 20190913215029.288 ERROR start - start.c:__lxc_start:1944 - Failed to initialize container "106"
lxc-start 106 20190913215029.288 ERROR lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 106 20190913215029.288 ERROR lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options

root@pve:~# ls -ail /usr/share/lxc/hooks/
total 68
133917 drwxr-xr-x 2 root root 4096 Aug 20 23:06 .
133874 drwxr-xr-x 6 root root 4096 Aug 20 23:06 ..
140202 -rwxr-xr-x 1 root root 1048 Aug 13 14:41 clonehostname
140203 -rwxr-xr-x 1 root root 3283 Aug 13 14:41 dhclient
140204 -rwxr-xr-x 1 root root 13718 Aug 13 14:41 dhclient-script
131379 -rwxr-xr-x 1 root root 2388 Jul 26 09:08 lxc-pve-autodev-hook
131380 -rwxr-xr-x 1 root root 3166 Jul 26 09:08 lxc-pve-poststop-hook
131381 -rwxr-xr-x 1 root root 3752 Jul 26 09:08 lxc-pve-prestart-hook
140205 -rwxr-xr-x 1 root root 2604 Aug 13 14:41 mountecryptfsroot
140206 -rwxr-xr-x 1 root root 8149 Aug 13 14:41 nvidia
140207 -rwxr-xr-x 1 root root 1805 Aug 13 14:41 squid-deb-proxy-client
140208 -rwxr-xr-x 1 root root 6755 Aug 13 14:41 ubuntu-cloud-prep
 
lxc-start 106 20190913215029.280 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start with output: volume 'FreenasVM:106/vm-106-disk-0.raw' does not exist

huho, missed that....
Maybe I should check if my NAS dont get something wrong
 
Ok, problem resolved, my NAS dropped some permission on directory where IMG files are stored. Corrected, everything boot fine now.
 
Glad you found a solution by yourself! Please mark the thread as 'SOLVED' since this helps others in a similar situation.

Thanks!
 
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