[SOLVED] Segmentation fault while starting any container

Feb 27, 2020
Hi, just writing this in case it helps anyone else.

Suddenly all the lxc containers of a node in a cluster failed to start, the only clues were as follows

root@proxmox-2:/var/log# pct start 129
setup_resource_limits: 2517 Unknown resource
lxc_spawn: 1813 Failed to setup resource limits
__lxc_start: 1999 Failed to spawn container "129"
startup for container '129' failed

root@proxmox-2:~# lxc-start -n 129 -F -l DEBUG -o /tmp/lxc-129.log
Segmentation fault

This happened with all the containers, but not with KVM servers.

The reason was a mistake (my mistake) when modifying /usr/share/lxc/config/common.conf.
I use ansible to set some node parameters and I had wrongly added the same line twice:

lxc.prlimit.nofile = 65536
lxc.prlimit.nofile = 1024

once i remove the duplicated row, all containers were back to normal.
  • Like
Reactions: Dunuin


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!

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!