Container startet nicht - LXC-"Standardverzeichnis" nicht erreichbar

S

simi

Member
Dec 29, 2019
13
1
23
51
Edit: gelöst - siehe unten

Hallo zusammen,

ich habe die letzten Tage mich an Proxmox versucht und es auch geschafft, einen Turnkey File Server als LXC aufzusetzen. Leider scheint er den Reboot nicht überlebt zu haben. Bei vielen Problemen bin ich hier im Forum weitergekommen, aber jetzt bräuchte ich Eure Hilfe - bin absoluter Linux-Noob...

Der Container mit dem Turnkey Server startet nicht mehr - offenbar scheint das Verzeichnis, in dem der Container gespeicht ist, nicht (mehr?) erreichbar zu sein. Habt Ihr eine Idee, woran das liegen könnte?

Code: 
root@pve1:~# lxc-start -n 201 -F -l DEBUG -o /tmp/lxc-ID.log
lxc-start: 201: conf.c: run_buffer: 352 Script exited with status 2
lxc-start: 201: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "201"
lxc-start: 201: start.c: __lxc_start: 2032 Failed to initialize container "201"
Segmentation fault


root@pve1:~# cat /tmp/lxc-ID.log
lxc-start 201 20200103170212.722 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "[all]"
lxc-start 201 20200103170212.723 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "kexec_load errno 1"
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "open_by_handle_at errno 1"
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 201 20200103170212.724 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "init_module errno 1"
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "finit_module errno 1"
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 201 20200103170212.725 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 201 20200103170212.726 INFO     seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context
lxc-start 201 20200103170212.727 INFO     conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "201", config section "lxc"
lxc-start 201 20200103170212.411 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 201 lxc pre-start produced output: cannot open directory //vm_pool/lxc: No such file or directory

lxc-start 201 20200103170212.417 ERROR    conf - conf.c:run_buffer:352 - Script exited with status 2
lxc-start 201 20200103170212.417 ERROR    start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "201"
lxc-start 201 20200103170212.417 ERROR    start - start.c:__lxc_start:2032 - Failed to initialize container "201"

Im Verzeichnis /vm_pool/lxc liegt der Container

Wenn ich versuche, ins Verzeichnis wechseln oder das Containerverzeichnis zu mounten gibt es auch Fehlermeldungen:
Code: 
root@pve1:~# cd /vm_pool/lxc
-bash: cd: /vm_pool/lxc: No such file or directory

root@pve1:~# pct mount 201
mounting container failed
cannot open directory //vm_pool/lxc: No such file or directory

Containerconfig:
Code: 
root@pve1:~# pct config 201
arch: amd64
cores: 2
hostname: turnkey-fs
memory: 512
mp0: /data1/share,mp=/data
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=1A:74:0D:C1:4D:C9,                                                                                                                                                             ip=192.168.1.110/24,type=veth
onboot: 1
ostype: debian
rootfs: LXC:subvol-201-disk-0,size=8G
swap: 512

Ich nutze ZFS:
Code: 
root@pve1:~# zfs list
NAME                            USED  AVAIL     REFER  MOUNTPOINT
data1                          1.71M  1.76T       96K  /data1
data1/share                     812K  1.76T      812K  /data1/share
rpool                          2.76G   284G      104K  /rpool
rpool/ROOT                     2.46G   284G       96K  /rpool/ROOT
rpool/ROOT/pve-1               2.46G   284G     2.46G  /
rpool/data                      303M   284G      104K  /rpool/data
rpool/data/ISO                  303M   284G      303M  /rpool/data/ISO
rpool/data/template              96K   284G       96K  /rpool/data/template
vm_pool                         689M   898G      104K  /vm_pool
vm_pool/lxc                     688M   898G      104K  /vm_pool/lxc
vm_pool/lxc/subvol-201-disk-0   688M  7.33G      688M  /vm_pool/lxc/subvol-201-disk-0
vm_pool/vm                       96K   898G       96K  /vm_pool/vm

root@pve1:~# zpool status
  pool: data1
state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        data1       ONLINE       0     0     0
          sdc       ONLINE       0     0     0

errors: No known data errors

  pool: rpool
state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          sda3      ONLINE       0     0     0

errors: No known data errors

  pool: vm_pool
state: ONLINE
  scan: none requested
config:

        NAME                      STATE     READ WRITE CKSUM
        vm_pool                   ONLINE       0     0     0
          wwn-0x5001b444a9dadba2  ONLINE       0     0     0

errors: No known data errors

Ein apt-get dist-upgrade mit der No-subcription-Source habe ich durchgeführt.

Habt Ihr eine Idee, was das Problem sein könnte?

Vielen Dank für Eure Hilfe :)
 
Last edited:
Ups - mehr als 10k Zeichen ;)

Hier noch die storage.conf:
Code: 
root@pve1:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content vztmpl,rootdir,images,iso,snippets
        maxfiles 0

zfspool: VM
        pool vm_pool/vm
        content images
        mountpoint /vm_pool/vm
        sparse 1

zfspool: LXC
        pool vm_pool/lxc
        content rootdir
        mountpoint /vm_pool/lxc
        sparse 1

dir: template
        path /rpool/data/ISO
        content images,iso,vztmpl
        shared 1
 
Ich glaube, ich habe das Problem mit diesem Post von oguz gelöst. Der Container wurde beim Booten gestartet.

Wie kann es sein, dass der ZFS-Cache schon corrupted ist, wenn ich eigentlich noch nix mit dem Rechner gemacht habe?
 
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