![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 13/09/2020 10.15, Rodney Baker wrote:
Hi all,
For some time I've been seeing shutdown delays of up to 2min 30 sec on Tumbleweed. The system reports, "A stop job is running for /run/user/
min:sec (counting down)", where min:sec can be anywhere up to 2-3 minutes. Once this timer runs down, shutdown proceeds as normal. If I log out of the desktop session first, then log into a VTY session as root and enter "Poweroff", shutdown takes less than 10 seconds.
My guess is that there is a race condition going on with some process still holding a file open in /run/user/
(whcih is a tmpfs file system, when the system is attempting to destroy it, but I have been so far completely unsuccessful in identifying what that could be. I've even tried enabling a debug terminal session on VTY9 but that's given no clue, either. How should I go about debugging this? So far, I don't even have enough information to raise a useful bug report (if one is even justified, given that it could be a local config issue rather than something systemic with Tumbleweed).
I have, not always but occasionally, perhaps a related issue in Leap 15.1. I command hibernate, by calling "sudo /usr/bin/systemctl hibernate". After a while I come back to power off the UPS, and see the machine still running. I try repeating the hibernate order, sometimes it works. Other times it doesn't, says there is an hibernate in progress. I command a shutdown with poweroff, which also gets stuck. I press rapidly several "ctrl-alt-supr", and I get a message that the key sequence was detected more than seven times in two seconds, rebooting fast. It does not. In the end, I have to remove the power cord. The last time, this resulted in a damaged disk. Never it says what is holding it, there are no messages in the log or screen. :-/ -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)