bjoern_tantau 111 points 21 days ago

A stop job is running

path: 0 25041149, hotness: undefined, score: 111, children: 15

TwilightKiddy 46 points 21 days ago

At least it tells you how long it'll take before it decides to SIGKILL whatever is holding the shutdown sequence.

save

path: 0 25041149 25041367, hotness: undefined, score: 46, children: 7

Thorry 20 points 21 days ago

Well you say that, but I've seen the countdown go past and then reset to a higher number often.

save

path: 0 25041149 25041367 25041483, hotness: undefined, score: 20, children: 4

TwilightKiddy 15 points 20 days ago

I entrust you with this horror, go figure out what to blame. ::: spoiler shutdown-analyze.sh

#! /usr/bin/env bash
shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP)
shutdown_start=$((shutdown_start / 1000000))
units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message)

for u in $units; do
    stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope)
    stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope)
    duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //')
    printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u"
done | sort -rn | cut -f 2

:::

save

path: 0 25041149 25041367 25041483 25043280, hotness: undefined, score: 15, children: 2

Thorry 4 points 20 days ago

Thanks, I usually know what it is tho. Most often it's VMs I was using for testing stuff, which I forgot to shutdown. It takes a while for them to cleanly shutdown, which is what the wait is for. I have a shortcut on my desktop to a script that checks for any running VMs still and shuts them down. But I forget to click it sometimes and then I have to wait. No big deal, except I like to switch off the power bar that powers the computer and everything attached to it. An old habit from when such a thing mattered, these days standby power is probably nothing to worry about. But still I wait patiently for the computer to shut down till I switch off the power strip.

save

path: 0 25041149 25041367 25041483 25043280 25043760, hotness: undefined, score: 4, children: 1

TwilightKiddy 7 points 20 days ago

If your script somehow shuts them down faster than plain old SIGTERM, putting it under /usr/lib/systemd/system-shutdown/ might be a good idea. Check man 8 systemd-shutdown for more info on that.

save

path: 0 25041149 25041367 25041483 25043280 25043760 25044863, hotness: undefined, score: 7, children: 0