[SOLVED] Einige LXC Container nach Serverneustart nicht mehr lauffähig

S

Stumpy

Member
Jan 2, 2020
12
2
23
36
Guten Tag

Ich hatte meinen Server gestern Abend herunter gefahren und heute morgen gestartet um weiter daran zu arbeiten.
Leider kann ich die meisten meiner LXC nicht mehr starten.
Die Windows 10 VM startet und einer meiner Ubuntu LXC startet.
5 Ubuntu und 1 debian LXC starten nicht mehr.

Anbei die beiden los die man für Details anschauen soll.

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


Code: 
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 7951.
Jan 02 20:37:50 StumpysProxi systemd-logind[2007]: Session 26 logged out. Waiting for processes to exit.
Jan 02 20:37:50 StumpysProxi systemd[1]: session-26.scope: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit session-26.scope has successfully entered the 'dead' state.
Jan 02 20:37:50 StumpysProxi systemd-logind[2007]: Removed session 26.
-- Subject: Session 26 has been terminated
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A session with the ID 26 has been terminated.
Jan 02 20:37:50 StumpysProxi pvedaemon[2681]: <root@pam> end task UPID:StumpysProxi:00006AC0:0007478F:5E0E464D:vncshell::root@pam: OK
Jan 02 20:37:52 StumpysProxi pvedaemon[27709]: starting CT 200: UPID:StumpysProxi:00006C3D:000761B7:5E0E4690:vzstart:200:root@pam:
Jan 02 20:37:52 StumpysProxi pvedaemon[2681]: <root@pam> starting task UPID:StumpysProxi:00006C3D:000761B7:5E0E4690:vzstart:200:root@pam:
Jan 02 20:37:52 StumpysProxi systemd[1]: Starting PVE LXC Container: 200...
-- Subject: A start job for unit pve-container@200.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@200.service has begun execution.
--
-- The job identifier is 8023.
Jan 02 20:37:53 StumpysProxi kernel: EXT4-fs (dm-18): mounted filesystem with ordered data mode. Opts: (null)
Jan 02 20:37:53 StumpysProxi kernel: lxc-start[27717]: segfault at 50 ip 00007f75f5f04f8b sp 00007ffe2f2c63d0 error 4 in liblxc.so.1.6.0[7f75f5eab000+8a000]
Jan 02 20:37:53 StumpysProxi kernel: Code: 9b c0 ff ff 4d 85 ff 0f 85 82 02 00 00 66 90 48 8b 73 50 48 8b bb f8 00 00 00 e8 80 78 fa ff 4c 8b 74 24 10 48 89 de 4c 89 f7 <
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container s
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 329 The container failed to start
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logprior
Jan 02 20:37:53 StumpysProxi systemd[1]: pve-container@200.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@200.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jan 02 20:37:53 StumpysProxi systemd[1]: pve-container@200.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@200.service has entered the 'failed' state with result 'exit-code'.
Jan 02 20:37:53 StumpysProxi systemd[1]: Failed to start PVE LXC Container: 200.
-- Subject: A start job for unit pve-container@200.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@200.service has finished with a failure.
--
-- The job identifier is 8023 and the job result is failed.
Jan 02 20:37:53 StumpysProxi pvedaemon[27709]: command 'systemctl start pve-container@200' failed: exit code 1
Jan 02 20:37:53 StumpysProxi pvedaemon[2681]: <root@pam> end task UPID:StumpysProxi:00006C3D:000761B7:5E0E4690:vzstart:200:root@pam: command 'systemctl start pve-containe
Jan 02 20:37:57 StumpysProxi pvedaemon[27732]: starting termproxy UPID:StumpysProxi:00006C54:00076375:5E0E4695:vncshell::root@pam:
Jan 02 20:37:57 StumpysProxi pvedaemon[2681]: <root@pam> starting task UPID:StumpysProxi:00006C54:00076375:5E0E4695:vncshell::root@pam:
Jan 02 20:37:58 StumpysProxi pvedaemon[2682]: <root@pam> successful auth for user 'root@pam'
Jan 02 20:37:58 StumpysProxi login[27738]: pam_unix(login:session): session opened for user root by root(uid=0)
Jan 02 20:37:58 StumpysProxi systemd-logind[2007]: New session 27 of user root.
-- Subject: A new session 27 has been created for user root
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 27 has been created for the user root.
--
-- The leading process of the session is 27738.
Jan 02 20:37:58 StumpysProxi systemd[1]: Started Session 27 of user root.
-- Subject: A start job for unit session-27.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-27.scope has finished successfully.
-- -- The job identifier is 8027.
Jan 02 20:37:58 StumpysProxi login[27744]: ROOT LOGIN  on '/dev/pts/1'
Jan 02 20:38:00 StumpysProxi 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
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 8103.

Code: 
root@StumpysProxi:~# systemctl status pve-container@200.service
● pve-container@200.service - PVE LXC Container: 200
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-01-02 20:37:53 CET; 3min 22s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 27711 ExecStart=/usr/bin/lxc-start -n 200 (code=exited, status=1/FAILURE)

Jan 02 20:37:52 StumpysProxi systemd[1]: Starting PVE LXC Container: 200...
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container s
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 329 The container failed to start
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Jan 02 20:37:53 StumpysProxi lxc-start[27711]: lxc-start: 200: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logprior
Jan 02 20:37:53 StumpysProxi systemd[1]: pve-container@200.service: Control process exited, code=exited, status=1/FAILURE
Jan 02 20:37:53 StumpysProxi systemd[1]: pve-container@200.service: Failed with result 'exit-code'.
Jan 02 20:37:53 StumpysProxi systemd[1]: Failed to start PVE LXC Container: 200.
lines 1-16/16 (END)
 
Zusätzliche Logs

Code: 
lxc-start 200 20200102194912.606 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "[all]"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "kexec_load errno 1"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "open_by_handle_at errno 1"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "init_module errno 1"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "finit_module errno 1"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 200 20200102194912.606 INFO     seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context
lxc-start 200 20200102194912.606 INFO     conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "200", config s$
lxc-start 200 20200102194912.997 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 200 lxc pre-start produced output: direct$
lxc-start 200 20200102194913.211 ERROR    conf - conf.c:run_buffer:352 - Script exited with status 2
lxc-start 200 20200102194913.215 ERROR    start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "200"
lxc-start 200 20200102194913.219 ERROR    start - start.c:__lxc_start:2032 - Failed to initialize container "200"

Code: 
root@StumpysProxi:~# pct config 200
arch: amd64
cores: 1
hostname: smb
memory: 512
mp0: /tank/data,mp=/data
mp2: /scratch/torrent,mp=/torrent
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.10,hwaddr=86:D0:ED:0F:36:17,ip=192.168.1.200/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-200-disk-0,size=8G
swap: 512

edit: hab eben mal nachgeschaut um zu erfahren, wieso der eine container funktioniert, die anderen aber nicht.
Einziger unterschied ist, das der funktionierende keinen mp hat.
Also testweise bei einem anderen LXC den mp entfernt... und der container startet.
Bei der Übersicht wird bei Disks -> ZFS der "tank" als Online und fehlerfrei dargestellt.
In der Shell kann ich auf /tank und sehe dort mit "ls" aber nur mein "backup" verzeichnis, nicht aber mein "media".

zfs list ergibt aber die richtige anzeige, wie ich es eingerichtet hatte.

Code: 
root@StumpysProxi:/tank# zfs list
NAME              USED  AVAIL     REFER  MOUNTPOINT
scratch          2.65T  6.16T       96K  /scratch
scratch/torrent  2.65T  6.16T     2.65T  /scratch/torrent
tank             35.5T   115T      205K  /tank
tank/backup      17.7G   115T     17.7G  /tank/backup
tank/data        35.5T   115T     35.5T  /tank/data

Edit2 : hab herausgefunden woran es lag. mein Backup ordner wurde beim serverneustart schon geschrieben, bevor der mountvorgang vom tank abgeschlossen war, wodurch dieser dann abgebrochen ist und meine lxc aufgrund des fehlenden mp nicht starten wollten.

ich hab den backupordner erst einmal deaktiviert, in der shell dann entfernt, den tank gemountet und es funktioniert wieder.
der thread kann also direkt geschlossen werden.

frage zum lösen des problems, das der Ordner erst geschrieben wird wenn der mountvorgang abgeschlossen ist habe ich bereits im englischen forum gestellt.
 
Last edited:
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
Back