Unable to boot Containers after update

Discussion in 'Proxmox VE: Installation and configuration' started by linuxares, Aug 14, 2019.

  1. linuxares

    linuxares New Member

    Joined:
    Aug 14, 2019
    Messages:
    3
    Likes Received:
    0
    Hi!

    I did a normal "apt update" and all of a sudden my Containers stopped working. Then I noticed you guys had released a new version so I upgraded to 6.0. Still no luck. It's a little homeserver so I run the no-subscription.
    WebGUI won't start them, nor manually via CLI

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

    Code:
    pxeversion -v
    
    proxmox-ve: 6.0-2 (running kernel: 5.0.18-1-pve)
    pve-manager: 6.0-5 (running version: 6.0-5/f8a710d7)
    pve-kernel-5.0: 6.0-6
    pve-kernel-helper: 6.0-6
    pve-kernel-4.15: 5.4-8
    pve-kernel-5.0.18-1-pve: 5.0.18-3
    pve-kernel-4.15.18-20-pve: 4.15.18-46
    pve-kernel-4.15.18-12-pve: 4.15.18-36
    ceph-fuse: 12.2.11+dfsg1-2.1
    corosync: 3.0.2-pve2
    criu: 3.11-3
    glusterfs-client: 5.5-3
    ksm-control-daemon: 1.3-1
    libjs-extjs: 6.0.1-10
    libknet1: 1.10-pve2
    libpve-access-control: 6.0-2
    libpve-apiclient-perl: 3.0-2
    libpve-common-perl: 6.0-3
    libpve-guest-common-perl: 3.0-1
    libpve-http-server-perl: 3.0-2
    libpve-storage-perl: 6.0-7
    libqb0: 1.0.5-1
    lvm2: 2.03.02-pve3
    lxc-pve: 3.1.0-63
    lxcfs: 3.0.3-pve60
    novnc-pve: 1.0.0-60
    proxmox-mini-journalreader: 1.1-1
    proxmox-widget-toolkit: 2.0-5
    pve-cluster: 6.0-5
    pve-container: 3.0-5
    pve-docs: 6.0-4
    pve-edk2-firmware: 2.20190614-1
    pve-firewall: 4.0-7
    pve-firmware: 3.0-2
    pve-ha-manager: 3.0-2
    pve-i18n: 2.0-2
    pve-qemu-kvm: 4.0.0-5
    pve-xtermjs: 3.13.2-1
    qemu-server: 6.0-7
    smartmontools: 7.0-pve2
    spiceterm: 3.1-1
    vncterm: 1.6-1
    zfsutils-linux: 0.8.1-pve1
    root@Proxmox:/etc#
    
    Code:
    root@Proxmox:/etc# pct mount 100                                    
    mounted CT 100 in '/var/lib/lxc/100/rootfs'
    root@Proxmox:/etc# pct unmount 100
    
    /etc/pve/storage.cfg

    Code:
    dir: local
           path /var/lib/vz
           content iso,backup,vztmpl
    
    lvmthin: local-lvm
           thinpool data
           vgname pve
           content rootdir,images
    
    zfspool: Raiden-WD4TB
           pool Raiden-WD4TB
           content rootdir,images
           nodes Proxmox
    
    Code:
    root@Proxmox:/etc# cat debian_version                             
    10.0
    
    Code:
    
    lxc-start 100 20190814203931.821 INFO     confile - confile.c:set_config_idmaps:1673 - Read uid map: type u nsid 0 hostid 100000 range 65536
    lxc-start 100 20190814203931.821 INFO     confile - confile.c:set_config_idmaps:1673 - Read uid map: type g nsid 0 hostid 100000 range 65536
    lxc-start 100 20190814203931.824 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
    lxc-start 100 20190814203931.824 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "keyctl errno 38"
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for keyctl action 327718(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for keyctl action 327718(errno)
    lxc-start 100 20190814203931.825 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for keyctl action 327718(errno)
    lxc-start 100 20190814203931.826 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for keyctl action 327718(errno)
    lxc-start 100 20190814203931.826 INFO     seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
    lxc-start 100 20190814203931.826 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
    lxc-start 100 20190814203931.426 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start with output: unable to detect OS distribution
    
    lxc-start 100 20190814203931.432 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 2
    lxc-start 100 20190814203931.432 ERROR    start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "100"
    lxc-start 100 20190814203931.432 ERROR    start - start.c:__lxc_start:1944 - Failed to initialize container "100"
    lxc-start 100 20190814203931.432 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
    lxc-start 100 20190814203931.432 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
    
    Code:
    root@Proxmox:~# pct config 100       
    arch: amd64 
    cores: 6 
    hostname: Arma3server 
    memory: 11444 
    net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=76:2E:E2:E5:79:0B,ip=dhcp,ip6=dhcp,type=veth 
    onboot: 0 
    ostype: ubuntu 
    rootfs: Raiden-WD4TB:subvol-100-disk-0,size=1000G 
    swap: 512 
    unprivileged: 1
    


    Any suggestion would be really helpful. I've been googling but I seem to come up empty handed.
    All I can think of is that it some how lost the configurations of the CTs.

    VMs work fine however. I got plenty of space left so it isn't that either.

    Regards
     
  2. RobFantini

    RobFantini Well-Known Member
    Proxmox Subscriber

    Joined:
    May 24, 2012
    Messages:
    1,597
    Likes Received:
    26
    try setting lxc > option > features : nested
     
  3. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,484
    Likes Received:
    314
    You get error "unable to detect OS distribution" - So what OS do you run inside the container?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. linuxares

    linuxares New Member

    Joined:
    Aug 14, 2019
    Messages:
    3
    Likes Received:
    0
    I did notice that as well, but the configuration for it do state that it is Ubuntu. It's the CT that Proxmox provides for version 18.04.

    The last log say this: "ostype: ubuntu" do I need to change it to Linux?

    And it's Ubuntu I run on all 3 of my Containers.
     
  5. linuxares

    linuxares New Member

    Joined:
    Aug 14, 2019
    Messages:
    3
    Likes Received:
    0
    More info.

    I created a new container to see if it booted fine. And it did.

    Then I checked the config files etc looked the same.
    Then I checked on my storage if the files looked the same. To my horror this is why I found, 105 is the working unit.

    Code:
    root@Proxmox:/Raiden-WD4TB# ls 
    subvol-100-disk-0  subvol-101-disk-0  subvol-102-disk-0  subvol-105-disk-0 
    root@Proxmox:/Raiden-WD4TB# cd subvol-100-disk-0/ 
    root@Proxmox:/Raiden-WD4TB/subvol-100-disk-0# ls 
    dev 
    root@Proxmox:/Raiden-WD4TB/subvol-100-disk-0# cd .. 
    root@Proxmox:/Raiden-WD4TB# cd subvol-105-disk-0/ 
    root@Proxmox:/Raiden-WD4TB/subvol-105-disk-0# ls 
    bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var 
    root@Proxmox:/Raiden-WD4TB/subvol-105-disk-0# 
    
    Have an update whiped my CTs?!
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice