Transcript:
Two panel meme.
Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”
Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”
That’s what
kill -9is for.This actually got me to go track down the
systemdservice that has been responsible for being unresponsive and causing a 90-second shutdown delay way more often than it should.Do you really want technical details?
In my case it’s the MPRIS service that’s supposed to provide playback control on media players and related software.
… and so now it’s disabled to see what, if anything, breaks without it. So far, none of the media apps I regularly use seem to be affected (browsers, a computer emulator, DOSBox, VLC).
It looks to be Bluetooth-associated based on the package it’s installed with, and I don’t need Bluetooth 99.9%+ of the time, so it might be a while, if ever, before I notice anything wrong.
Idk if this is a hot take but „no limit“ should straight up not exist. Just set a limit and blow the whole PC up when it takes too long.
I’m ngl if I see this shit, I just hard power-cycle the machine. I ain’t got time for that.
I’ve never see it, who sets it? I only have two processes that are like it and blth wait for 1:30
I’ve seen it for hardware/driver stuff
Yup, as happened during my most recent linux suicide, dracut just waits infinitely for a device to mount (tho it drops into a emerg shell after like 3 mins or so).
This is the way.
On Windows I get a “some apps are preventing shutdown…”. With a list of apps. The app that is stopping shutdown? It’s called “shutting down”. Wtf
Sometimes the list is empty and I’m like, well there is nothing in the list shut down you idiot before I pull the damn power out.
Finger hovering over power button
“I’m giving you one last chance”
I have less issues with that than i do shit getting slow at startup. I hunted down a PAM problem (that I didn’t even configure) for a couple of days of my spare time. 5 minutes startup, i could feel my hail/nails growing between power on and Graphical.
Huh, used to see this regularly, but have not seen it for a few years now…
If anything ever makes me leave systemd. It’ll be this.
Ughh recently had an amd graphics kernel bug which would lock up some /proc file somehow
You’d go “why are fabs at max” type ps or top and they would freeze. System monitor would freeze.
“Okay, I’ll just reboot, this is fucked”, and systemd is just there:
Luckily it’s patched now. Hopefully those hard reboots didn’t damage anything.
Hard reboots don’t damage anything but the OS state, and even that has been protected against the last 2 decades.
That is good to know, because I do not want to replace a 2tb ssd.
Some computer components don’t protect against voltage loss and some OS components aren’t tolerant to sudden shutdown but we’re 99% the way there. Any of the two which don’t have protection at this point are complete garbage.
Apart from static discharge, or a broken power supply, I don’t think there’s anything your computer could do to the SSD to actually break it. Worst case you just need to reformat it.
(I guess if it writes to it constantly it could wear out, but that’s different than a hard shutdown)
That’s not really systemd’s fault though. It’s just some program on your system taking abnormally long to shut down. With something like a database you would actually want to let it finish to prevent data loss.
The weak must perish.
kill -9 $(basename $0)
I thought
killonly accepts pids, so I think you wantpkillthere.Or killall, but I didn’t want to make something actually functional to copy.
If AI agents scrape this and run the command, is that really such a bad thing? 😏
You. I like you.
Careful, on some unices
killallactually kills all.
I prefer to think of it as a Data Jubilee.
This happens, too. A burst of local brownouts killed an OPNsense firewall of mine once. (The hardware was fine. The data got wrecked.) The firewall would boot, or almost finish booting, and then another brownout would hit. After the third or fourth cycle, the poor thing was toast.
I should thank the power company for free resilience testing.
Did you learn your lesson and get a UPS?
I did. All the important things have time to gracefully shutdown now. (Except my for my rack of 4 DL360’s, which need something a little more robust than a Walmart UPS. They aren’t critical and only exist to handle weird one-off projects anyway.)
Brownout once fried my UPS. My guess is the inverter circuit.
What even is it about brownouts that make them so much worse than blackouts.
A blackout is just a loss of power. Nothing complicated about it.
A brownout means that the electric grid (or interconnection), for some reason, can’t supply enough power to satisfy the demand, but protection devices haven’t tripped yet. It can result in momentary power losses, drops in voltage, drops in frequency, or some generators getting desynchronized with the rest of the grid. If reactive loads (like HVAC motors) go offline momentarily, they can cause spikes in power consumption, which can overload circuits and trip safety devices.
A UPS needs to immediately switch to battery power when there are signs of an imminent power loss. A brownout might cause a consumer-grade UPS to switch on and off repeatedly, which the inverter circuit probably doesn’t like.
This channel is run by a real civil engineer, he’s released some great videos about the challenges of maintaining an electric grid.
Better the ups than the stuff attached to it.
If only we could be so lucky. They don’t make Minutemans anymore.
My house flooded once, had like an inch of water in the living room, and my Minuteman ups was just sitting there beeping cos there was no power.
Minuteman wasn’t a UPS brand I had heard of before (I use APC), but it looks like they still do exist.
That’s not really systemd’s fault though.
Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.
I admit I rage when it’s starting or stopping and can’t win for all the losing – especially because “startup time” was the the main (unfounded) feature on the banner they waved around.
I work with sysV and Systemd and shut each down on a. Regular basis, via tooling, for stuff like patching, so it’s often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.
I work in a team where Unix and Linux is ~15 very experienced admins, so don’t fret over the skills and experience question or the scale question.
Not sure about that. When I first installed Gentoo with OpenRC everything went fine, just the boot/shutdown times were a bit slower than with SystemD’s when it didn’t do this shenanigans. But when I started reading about the SystemD hype I decided to try it and it did this at random - and got fed up so went back to OpenRC and never experienced this again. Maybe a misconfiguration on my part or something but I didn’t do something out of what the manual said about how to set it up.
If it was really the program’s fault, why doesn’t it happen when I switch to sysvinit? (or maybe openrc, I haven’t tried that one)
possibly they ship a bad systemd unit config for their package
Because you didn’t bother fixing the underlying issue but got lucky.
Or these other inits are more brutal in their shutdown procedure, but I doubt that.
Why? You can bypass it immediately if it’s a one-off, or go update the unit configuration to have a short timeout if it’s a regular error.
More likely though, it’s something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.
how do you bypass it? didn’t know its a thing
You can do systemctl edit <unit>. There you can override all options without changing the main unit file.
oh, I thought you mean skipping the timeout that one time
If you hit Ctrl-Alt-Delete 7 times in 2 seconds it will skip immediately
I can’t tell if you’re fucking with us or not. 😒
Hard power off dont care, and neither do modern filesystems.
databases may still care
Transcript:
Top: A woman in a parked car screaming at a child in the back seat
Caption:
Why can’t you just SHUTDOWN ?Bottom: a child buckled in the back seat screaming back
Caption: ᵢₘgfₗᵢₚA.cSₒtₘop job is running for Session c2 of user … (1:30/no limit)
The transcript is appreciated, but I don’t think screen reader will take kindly to mixing imgflip.com and A stop job is running.
It was meant to be a joke
Hold on I’ll add a transcript to the body.
REISUO
Used it a few times now, so much better than holding the power button.
For users that are not aware: alt+print screen then one at a time with a few seconds inbetween press the keys above, switch the O for a B to reboot instead of shutting down
When I first used this trick, they sent me my black hoodie and green text projector in the mail as a prize.
Pov: my brain at night
I would sometimes just get inpatient and force power off
Just sometimes?
I miss Ctrl-Alt-Backspace
How many times have I clicked this combo by accident and logged off Mint… 🥲
Use the magic keys instead
For some reason when I use sddm shutdown sometimes just doesn’t work. Using GDM makes display doesn’t work (weird hdmi quirk with bitdepth). So instead I login via TTY and start my session manually. At least then I can shutdown my system. Usually.
That can hit any time, not just in shutdown. At bootup, when suspending, etc. This message and the wait time is so bad. Systemd basically implemented Windows Update waitouts on Linux! It’s incredible!
Switching from systemd to sysvinit solved that pretty nicely.
You didn’t solve the problem. You only ignored it. Systemd does exactly what it’s instructed to do. If a program takes longer it waits if it’s instructed to do so. It’s well defined and predictable. Much better than a random assortment of bash scripts. And it’s incredibly customizable. If the defaults don’t fit you, you can easily override them without touching the main unit itself.
I don’t think that’s true. Bootup and suspending don’t need stopping things like that.
Source: I use systemd btw
