[SOLVED] lxcfs.service: Main process exited code=killed, status=11/SEGV

michaelj

Active Member
Jun 30, 2016
40
0
26
33
Hi Community,

I wanted to know if anyone has ever encountered the following problem:

logs:

Code:
2020-11-29T04:37:30.054129+01:00        hv18 systemd[1]: lxcfs.service: Main process exited,        code=killed, status=11/SEGV
     2020-11-29T04:37:30.094752+01:00 hv18 systemd[1]: lxcfs.service:      Unit entered failed state.
     2020-11-29T04:37:30.095112+01:00 hv18 systemd[1]: lxcfs.service:      Failed with result 'signal'.
     2020-11-29T04:37:30.423594+01:00 hv18 systemd[1]: lxcfs.service:      Service hold-off time over, scheduling restart.
     2020-11-29T04:37:30.424265+01:00 hv18 systemd[1]: Stopped FUSE        filesystem for LXC.
     2020-11-29T04:37:30.424911+01:00 hv18 systemd[1]: Started FUSE        filesystem for LXC.
     2020-11-29T04:37:30.457851+01:00 hv18 lxcfs[18507]: mount      namespace: 5
     2020-11-29T04:37:30.458194+01:00 hv18 lxcfs[18507]: hierarchies:
     2020-11-29T04:37:30.458425+01:00 hv18 lxcfs[18507]:   0: fd:   6:      rdma
     2020-11-29T04:37:30.458632+01:00 hv18 lxcfs[18507]:   1: fd:   7:      net_cls,net_prio
     2020-11-29T04:37:30.458827+01:00 hv18 lxcfs[18507]:   2: fd:   8:      perf_event
     2020-11-29T04:37:30.458985+01:00 hv18 lxcfs[18507]:   3: fd:   9:      freezer
     2020-11-29T04:37:30.459184+01:00 hv18 lxcfs[18507]:   4: fd:  10:      hugetlb
     2020-11-29T04:37:30.459388+01:00 hv18 lxcfs[18507]:   5: fd:  11:      cpuset
     2020-11-29T04:37:30.459607+01:00 hv18 lxcfs[18507]:   6: fd:  12:      cpu,cpuacct
     2020-11-29T04:37:30.459809+01:00 hv18 lxcfs[18507]:   7: fd:  13:      blkio
     2020-11-29T04:37:30.459973+01:00 hv18 lxcfs[18507]:   8: fd:  14:      pids
     2020-11-29T04:37:30.460179+01:00 hv18 lxcfs[18507]:   9: fd:  15:      devices
     2020-11-29T04:37:30.460371+01:00 hv18 lxcfs[18507]:  10: fd:  16:      memory
     2020-11-29T04:37:30.460572+01:00 hv18 lxcfs[18507]:  11: fd:  17:      name=systemd
     2020-11-29T04:37:30.460816+01:00 hv18 lxcfs[18507]:  12: fd:  18:      unified

The consequence on lxc containers :

Code:
Error: /proc must be mounted
  To mount /proc at boot you need an /etc/fstab line like:
      proc   /proc   proc    defaults
  In the meantime, run "mount proc /proc -t proc"

 /proc/cpuinfo is not accessible: Transport endpoint is not connected

Informations :

proxmox-ve: 5.4-2 (running kernel: 4.15.18-30-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1

novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2


If i umount /proc then remount it inside lxc container, the errors disappear but I would like to know the origin of the problem and know if we can correct it?

Plus, the problem happens randomly.

Regards,

Michael.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!