LXC suddenly stopped and are not starting any more

[tgoetten]

Hi everyone,

i'm facing a problem while trying to start all of my lxc containers.

# lxc-start -n lxc-container1 -F

lxc-start: conf.c: mount_autodev: 1175 No such file or directory - Failed mounting tmpfs onto /dev


lxc-start: conf.c: tmp_proc_mount: 3687 No such file or directory - failed to mount /proc in the container.
lxc-start: lsm/apparmor.c: apparmor_process_label_set: 183 No such file or directory - failed to change apparmor profile to lxc-container-default
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4
lxc-start: start.c: __lxc_start: 1211 failed to spawn 'lxc-container1'
lxc-start: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request
lxc-start: cgmanager.c: cgm_remove_cgroup: 525 Error removing all:lxc/lxc-container1-7
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

Please, can someone help me with this issue?

ii  libpve-access-control          4.0-10                         amd64        Proxmox VE access control library
ii  libpve-common-perl             4.0-41                         all          Proxmox VE base library
ii  libpve-storage-perl            4.0-34                         all          Proxmox VE storage management library
ii  pve-cluster                    4.0-29                         amd64        Cluster Infrastructure for Proxmox Virtual Environment
ii  pve-container                  1.0-31                         all          Proxmox VE Container management tool
ii  pve-firewall                   2.0-14                         amd64        Proxmox VE Firewall
ii  pve-firmware                   1.1-7                          all          Binary firmware code for the pve-kernel
ii  pve-ha-manager                 1.0-14                         amd64        Proxmox VE HA Manager
ii  pve-kernel-4.2.2-1-pve         4.2.2-16                       amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.2.3-2-pve         4.2.3-22                       amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.2.6-1-pve         4.2.6-25                       amd64        The Proxmox PVE Kernel Image
ii  pve-libspice-server1           0.12.5-2                       amd64        SPICE remote display system server library
ii  pve-manager                    4.0-64                         amd64        The Proxmox Virtual Environment
ii  pve-qemu-kvm                   2.4-16                         amd64        Full virtualization on x86 hardware

Linux sochi.h-s-l.de 4.2.6-1-pve #1 SMP Tue Dec 1 19:01:21 CET 2015 x86_64 GNU/Linux


Thomas

 

[dietmar]

What is the output of

# systemctl status lxcfs.service

 

[tgoetten]

Hi Dietmar,


here is the output

lxcfs.service - FUSE filesystem for LXC
   Loaded: loaded (/lib/systemd/system/lxcfs.service; enabled)
   Active: active (running) since Tue 2015-12-08 11:24:23 CET; 2h 0min ago
 Main PID: 1071 (lxcfs)
   CGroup: /system.slice/lxcfs.service
           └─1071 /usr/bin/lxcfs -f -s -o allow_other /var/lib/lxcfs/




Dec 08 11:24:23 proxmox-host lxcfs[1071]: hierarchies: 1: name=systemd
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 2: cpuset
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 3: cpu,cpuacct
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 4: blkio
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 5: memory
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 6: devices
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 7: freezer
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 8: net_cls,net_prio
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 9: perf_event
Dec 08 11:24:23 proxmox-host lxcfs[1071]: 10: hugetlb

Thank's for lookin into this issue
Thomas

 

[dietmar]

looks OK so far. I assume you run latest lxc-pve package (1.1.5-5)?

# dpkg -l lxc-pve

If so, can you create and run new containers?

 

[tgoetten]

Hi Dietmar,

you are right about the package version

~ # dpkg -l lxc-pve
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                          Version                     Architecture                Description
+++-=============================================-===========================-===========================-================================================================================================
ii  lxc-pve                                       1.1.5-5                     amd64                       Linux containers usersapce tools

The interesting part is, that a newly created container starts without a problem. So i checked, what is different. It seems, that newly created lxc containers was "missing" two config lines :

lxc.autodev = 1
lxc.kmsg = 0

After removing them, the (old) machines did start again. This is really weired...

Thomas