He was able to fix it by doing a kill -9 1, which in his case caused systemd to restart without -switched-root and -deserialize however, when I tried that, systemd ignores the SIGTERM (also, I don't know what side effects I'll get if I try running it without those flags my setup is RAID+LVM+LUKS). I have no idea what's causing this, or how to debug it. This is a production server and I need urgent help resolving this issue. All the standard commands like reboot, shutdown, and systemctl reboot or systemctl shutdown, fail with a timeout error, forcing me to pull the power on the machine. Moreover, rebooting and shutting down is impossible.
This creates the additional problem of not being able to install packages whose RPMs have scriptlet commands that restart services - I can only do so after a fresh reboot, before the problem state develops. However, some time later, the system ends up in a state where virtually all systemctl operations issued as root fail with Failed to execute operation: Connection timed outĮven listing units fails: Failed to list units: Connection timed out
The system would boot normally, with all services running. This started happening a while ago on my x86-64 installation, and continues even with the latest updates as of yesterday.
0 kommentar(er)
