Container kann nicht manuell gestartet werden

Bob22

New Member
Sep 11, 2019
17
0
1
32
Ich habe mit Proxmox VE 6.0-4 das Problem, das mein Container 106 nur während einem Reboot startet (da startet er automatisch). Nach einem Shutdown kann ich ihn nicht mehr erneut starten. Der Container liegt in einem LVM-Thin Storage, Template ist der Nextcloud-Turnkey Template, und ich habe auch nicht viel verändert:

# pct start 106
Code:
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

Ich habe versucht, den Container im Foreground-Mode zu starten:

#lxc-start -n 106 -F -l DEBUG -o /tmp/106.log:
Code:
lxc-start: 106: conf.c: run_buffer: 335 Script exited with status 32

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
(das logfile habe ich in den nächsten Post kopiert, ob der 10000 Zeichen-Begrenzung)


journalctl -xe:

Code:
A start job for unit pve-container@106.service has begun execution.

--

-- The job identifier is 1085051.

Apr 06 01:30:20 server1 lxc-start[3771]: lxc-start: 106: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state

Apr 06 01:30:20 server1 lxc-start[3771]: lxc-start: 106: tools/lxc_start.c: main: 330 The container failed to start

Apr 06 01:30:20 server1 lxc-start[3771]: lxc-start: 106: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode

Apr 06 01:30:20 server1 lxc-start[3771]: lxc-start: 106: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options

Apr 06 01:30:20 server1 systemd[1]: pve-container@106.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@106.service has exited.

--

-- The process' exit code is 'exited' and its exit status is 1.

Apr 06 01:30:20 server1 systemd[1]: pve-container@106.service: Failed with result 'exit-code'.

-- 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 'exit-code'.

Apr 06 01:30:20 server1 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 1085051 and the job result is failed.

Apr 06 01:30:20 server1 pvedaemon[3769]: command 'systemctl start pve-container@106' failed: exit code 1

Apr 06 01:30:20 server1 pvedaemon[3250]: <root@pam> end task UPID:server1:00000EB9:0008D4DB:5E8A6A0A:vzstart:106:root@pam: command 'systemctl start pve-container@106' failed: exit code 1

Apr 06 01:30:20 server1 pvestatd[3169]: unable to get PID for CT 106 (not running?)

Apr 06 01:31:00 server1 systemd[1]: Starting Proxmox VE replication runner...

-- Subject: A start job for unit pvesr.service has begun execution

-- Defined-By: systemd

-- Support: https://www.debian.org/support

Ich habe das Gefühl, dass es mit meinem Storage ein Problem gibt, kann aber nicht erkennen, wo genau es liegt.

# vgs:
Code:
VG  #PV #LV #SN Attr   VSize    VFree

  pve   1   4   0 wz--n- <223.07g <16.00g

# lvs:
Code:
LV            VG  Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert

  data          pve twi-aotz-- <141.43g             3.67   1.30                         
  root          pve -wi-ao----   55.75g                                                 
  swap          pve -wi-ao----    7.00g                                                 
  vm-106-disk-0 pve Vwi-a-tz--  100.00g data        5.20

# /etc/pve/storage.cfg:

Code:
dir: local

        path /var/lib/vz
        content vztmpl,iso,snippets,images,rootdir
        maxfiles 0
        shared 0

dir: BigData
        path /mnt/data
        content images,rootdir,vztmpl,iso,backup
        maxfiles 3
        shared 0

lvmthin: Thinpool
        thinpool data
        vgname pve
        content images,rootdir
 
Last edited:
106.log:

Code:
xc-start 106 20200405234201.957 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 106 20200405234201.957 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 20200405234201.957 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 20200405234201.957 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 20200405234201.957 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 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 106 20200405234201.957 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 106 20200405234201.958 INFO     seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 106 20200405234201.958 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 20200405234202.925 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start with output: mount: /var/lib/lxc/106/rootfs: spec$

lxc-start 106 20200405234202.925 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 106 lxc pre-start with output: command 'mount /dev/pve/vm-106-disk-$

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

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!

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!