udev fails to configure

pbrooks

Member
Apr 9, 2022
2
1
8
One of my hosts is having difficulty upgrading, it all seems to fail with udev.
/run/systemd/unit-root/proc/sys/kernel/domainname doesn't exist on any of my hosts, however on this host it seems to block the udev configure.
I've tried binding proc to /run/systemd/unit-root/proc and that doesn't help, is some kind of sandbox or apparmour getting in the way?

root@vmhost0:/etc/systemd# dpkg --configure udev Setting up udev (247.3-7) ... Job for systemd-udevd.service failed because the control process exited with error code. See "systemctl status systemd-udevd.service" and "journalctl -xe" for details. invoke-rc.d: initscript udev, action "restart" failed. ● systemd-udevd.service - Rule-based Manager for Device Events and Files Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static) Active: activating (auto-restart) (Result: exit-code) since Sat 2022-04-09 08:50:03 BST; 2ms ago TriggeredBy: ● systemd-udevd-control.socket ● systemd-udevd-kernel.socket Docs: man:systemd-udevd.service(8) man:udev(7) Process: 2728695 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=226/NAMESPACE) Main PID: 2728695 (code=exited, status=226/NAMESPACE) CPU: 3ms Apr 09 08:50:03 vmhost0 systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 2. Apr 09 08:50:03 vmhost0 systemd[1]: Stopped Rule-based Manager for Device Events and Files. Apr 09 08:50:03 vmhost0 systemd[1]: Starting Rule-based Manager for Device Events and Files... Apr 09 08:50:03 vmhost0 systemd[2728697]: systemd-udevd.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc/sys/kernel/domainname: No such file or directory Apr 09 08:50:03 vmhost0 systemd[2728697]: systemd-udevd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-udevd: No such file or directory Apr 09 08:50:03 vmhost0 systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=226/NAMESPACE Apr 09 08:50:03 vmhost0 systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Apr 09 08:50:03 vmhost0 systemd[1]: Failed to start Rule-based Manager for Device Events and Files. Apr 09 08:50:03 vmhost0 systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 3. Apr 09 08:50:03 vmhost0 systemd[1]: Stopped Rule-based Manager for Device Events and Files. Apr 09 08:50:03 vmhost0 systemd[1]: Starting Rule-based Manager for Device Events and Files... dpkg: error processing package udev (--configure):
 

About

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!