Hi Community!
I am working on a small server with up-to-date Debian 12, that is hosting LXC containers and VMs. To be more specific, it is a proxmox server but I don’t think that the issue is related to px.
I’m encountering a really strange issue, that is affecting ALL unprivileged containers, new or old. Even if I create a new unpriv. container, I’m getting the same results.
The issue appeared yesterday after a mains power outage/failure.
After the server boot up, all unpriv. LXCs were (and are still) down.
I have checked the logs, and I cannot get past this error. I tried all found Information online but I can’t get it to work, I’m out of ideas that’s why I’m reaching out to you…
The error is this:
lxc-start 103 20240217230903.616 INFO conf - ../src/lxc/conf.c:mount_autodev:1281 - Prepared "/dev"
lxc-start 103 20240217230903.616 DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:736 - Invalid argument - Tried to ensure procfs is unmounted
lxc-start 103 20240217230903.616 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:743 - Created procfs mountpoint under 17
lxc-start 103 20240217230903.616 DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:759 - Invalid argument - Tried to ensure sysfs is unmounted
lxc-start 103 20240217230903.616 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:766 - Created sysfs mountpoint under 17
**lxc-start 103 20240217230903.616 ERROR utils - ../src/lxc/utils.c:safe_mount:1220 - Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc"**
**lxc-start 103 20240217230903.616 ERROR conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:811 - Operation not permitted - Failed to mount "proc" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" with flags 14 **
**lxc-start 103 20240217230903.616 ERROR conf - ../src/lxc/conf.c:lxc_setup:4403 - Failed to setup first automatic mounts**
**lxc-start 103 20240217230903.616 ERROR start - ../src/lxc/start.c:do_start:1272 - Failed to setup container "103"**
lxc-start 103 20240217230903.616 TRACE sync - ../src/lxc/sync.c:lxc_sync_wake_parent:104 - Child waking parent with sequence error
lxc-start 103 20240217230903.620 ERROR sync - ../src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 3)
lxc-start 103 20240217230903.620 TRACE start - ../src/lxc/start.c:lxc_expose_namespace_environment:906 - Set environment variable LXC_USER_NS=/proc/102808/fd/17
- I’ve verified the folder /usr/lib/x86_64-linux-gnu/lxc/rootfs/; It is present and it has the correct user rights. And no, proc doesn’t have to exist. I tried to create it, made no difference. On other hosts “proc” is not even present, there should be just a readme file.
- I’m starting the unpriv. lxc container as root, but this is “normal behavior” in the px envrionment. Actually, the same container is starting on another debian host, with the same settings, user and rights. And as said, it occured only after the power outage.
- On a healthy host, the logs look like this:
lxc-start 103 20240217231011.771 INFO conf - ../src/lxc/conf.c:mount_autodev:1281 - Prepared "/dev"
lxc-start 103 20240217231011.772 DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:736 - Invalid argument - Tried to ensure procfs is unmounted
lxc-start 103 20240217231011.772 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:743 - Created procfs mountpoint under 17
lxc-start 103 20240217231011.773 DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:759 - Invalid argument - Tried to ensure sysfs is unmounted
lxc-start 103 20240217231011.773 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:766 - Created sysfs mountpoint under 17
**lxc-start 103 20240217231011.775 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:820 - Mounted automount "proc" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" read-write with flags 14**
lxc-start 103 20240217231011.777 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:820 - Mounted automount "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys/net" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/tty" read-write with flags 4096
lxc-start 103 20240217231011.778 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:820 - Mounted automount "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys" read-write with flags 4096
lxc-start 103 20240217231011.779 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:818 - Remounted automount "(null)" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys" read-only with flags 4129
lxc-start 103 20240217231011.780 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:820 - Mounted automount "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/tty" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys/net" read-write with flags 8192
lxc-start 103 20240217231011.781 TRACE conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:820 - Mounted automount "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sysrq-trigger" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sysrq-trigger" read-write with flags 4096
- I have verified the virtual storage of the container, it is intact. But this should not matter, as the issue occurs with new containers too.
- Smarttest passed, fsck for /dev/mapper/pve-root on / passed…
- I have compared the mounts with those on the healthy server, looks almost identical, just hardware/size differences.
I suppose that maybe some file or a package got corrupted? Is this even possible, while all the rest is working as expected?!
If anyone has any ideas, I would be thankfull!
PS: I thought of rolling back to an older system backup, but I really want to know, what happened and how it can be fixed. It is also interesting to find out, what lead to this issue and how it can be avoided (as good as possible), in the feature, in case of further power loses.
Thank you!
Teo