What does a statement like below mean and did I do something wrong(AGAIN)

English Install/Boot/Login
1

Doing a CLI ‘reboot’ after a ‘zypper up’ says to restart, I get a message similar to the fallowing during the reboot exit scripting;

a stop job is running for session 1 of 'ME" 1min,38sec

It takes the fill 1 minute and 38 seconds before it finishes and goes back to the boot menu.

I had some problem with Thunderbird wanting go open just after boot completion.
I could not find it in “ps”. '‘top’ or in the logs and journal, even when it was present on the screen.

What I ended up doing was to go into YaST(as root), and delete user “ME”, rebooted & logged in as root, and recreate USER “ME”.
Most of my applications, and their settings were still there, with little work to bring it back to where it was.

Curiosity getting the better of me again.

2

I think this is an annoyance of “systemd”.

I rarely see that. When it does show up, it is usually 1 min 30 seconds. I just wait it out. It normally won’t happen again on the next boot.

3

Nope. This is not an annoyance of systemd. This is intended behavior. Systemd terminates processes with signal TERM. If a process hits timeout, systemd terminates it with signal KILL:


**erlangen:~ #** systemctl show node.service -p KillSignal       
KillSignal=15 
**erlangen:~ #** systemctl show node.service -p FinalKillSignal  
FinalKillSignal=9 
**erlangen:~ #**[FONT=monospace]systemctl show node.service -p TimeoutStopUSec 
TimeoutStopUSec=1min 30s 
**erlangen:~ #**[/FONT]

Users may check journal to find out what causes rogue behavior of some processes.

https://unix.stackexchange.com/questions/227017/how-to-change-systemd-service-timeout-value

BTW: Unfiltered output of above command is 219 lines on host erlangen.https://forums.opensuse.org/images/smiliesnew/wink.png

4

Those are not contradictions.

I’m pretty sure that it never happened back in the SySV init days. Yes, shutdown would first send a TERM signal and then a KILL signal. But it did not insert that additional delay between those signals.

I should also add to my earlier reply. I use KDE. I set it to start from a previously saved session. When I want to reboot, I do close all windows first. And maybe that’s part of why I rarely see this. But, of course, occasionally an application will get stuck and keep running even after the window is closed.

5

Busy users may want to run “systemctl isolate reboot.target --force --no-block”:

**erlangen:~ #** journalctl -b -1 --since 07:09:00 -g Stopped -o short-monotonic  
[46843.895675] erlangen systemd[1]: Stopped target Graphical Interface. 
[46843.895771] erlangen systemd[1]: Stopped target Multi-User System. 
[46843.895870] erlangen systemd[1]: Stopped target Login Prompts. 
[46843.896082] erlangen systemd[1]: Stopped target Sound Card. 
[46843.896180] erlangen systemd[1]: Stopped target Timer Units. 
[46843.896430] erlangen systemd[1]: Stopped Backup of /home. 
[46843.896765] erlangen systemd[1]: Stopped Backup of RPM database. 
[46843.914178] erlangen systemd[1]: Stopped Backup of /etc/sysconfig. 
[46843.914695] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
[46843.914897] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
[46843.915103] erlangen systemd[1]: Stopped Discard unused blocks once a week. 
[46843.915289] erlangen systemd[1]: Stopped Daily rotation of log files. 
[46843.915444] erlangen systemd[1]: Stopped Daily man-db regeneration. 
[46843.915602] erlangen systemd[1]: Stopped Daily locate database update. 
[46843.915785] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit. 
[46843.915963] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
[46843.916396] erlangen systemd[1]: Stopped Timeline of Snapper Snapshots. 
[46843.916639] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
[46843.919815] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
[46843.921529] erlangen systemd[1]: Stopped Setup Virtual Console. 
[46843.923835] erlangen systemd[1]: Stopped hd-idle disk spindown service. 
[46843.924538] erlangen systemd[1]: Stopped irqbalance daemon. 
[46843.924839] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon. 
[46843.925411] erlangen systemd[1]: Stopped Avahi mDNS/DNS-SD Stack. 
[46843.925785] erlangen systemd[1]: Stopped CUPS Scheduler. 
[46843.931476] erlangen systemd[1]: Stopped Getty on tty1. 
[46843.932876] erlangen systemd[1]: Stopped Daemon for power management. 
[46843.934701] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
[46843.937299] erlangen systemd[1]: Stopped Power Profiles daemon. 
[46843.938004] erlangen systemd[1]: Stopped Save/Restore Sound Card State. 
[46843.938308] erlangen systemd[1]: Stopped Load/Save Random Seed. 
[46844.005893] erlangen systemd[1]: Stopped Modem Manager. 
[46844.006054] erlangen systemd[1]: Stopped Disk Manager. 
[46844.006417] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown. 
[46844.020438] erlangen systemd[1]: Stopped Session 2 of User karl. 
[46844.030252] erlangen systemd[1]: Stopped Hold until boot process finishes up. 
[46844.043983] erlangen systemd[1181]: Stopped target Main User Target. 
[46844.045014] erlangen systemd[1181]: Stopped Sound Service. 
[46844.045420] erlangen systemd[1181]: Stopped User preferences database. 
[46844.045494] erlangen systemd[1181]: Stopped Virtual filesystem service - Media Transfer Protocol monitor. 
[46844.045569] erlangen systemd[1181]: Stopped Virtual filesystem service - digital camera monitor. 
[46844.047885] erlangen systemd[1181]: Stopped Save jAlbum Project Files. 
[46844.048501] erlangen systemd[1181]: Stopped Virtual filesystem service - GNOME Online Accounts monitor. 
[46844.077854] erlangen systemd[1181]: Stopped D-Bus User Message Bus. 
[46844.078404] erlangen systemd[1181]: Stopped Virtual filesystem service - disk device monitor. 
[46844.079008] erlangen systemd[1181]: Stopped Virtual filesystem service - Apple File Conduit monitor. 
[46844.079929] erlangen systemd[1181]: Stopped Accessibility services bus. 
[46844.080037] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software. 
[46844.084509] erlangen systemd[1]: Stopped Postfix Mail Transport Agent. 
[46844.085072] erlangen systemd[1]: Stopped target Network is Online. 
[46844.085878] erlangen systemd[1181]: Stopped Firefox - Web Browser. 
[46844.086518] erlangen systemd[1]: Stopped Authorization Manager. 
[46844.092005] erlangen systemd[1181]: Stopped Virtual filesystem service. 
[46844.092145] erlangen systemd[1181]: Stopped target Basic System. 
[46844.092239] erlangen systemd[1181]: Stopped target Paths. 
[46844.092329] erlangen systemd[1181]: Stopped target Sockets. 
[46844.092393] erlangen systemd[1181]: Stopped target Timers. 
[46844.113341] erlangen systemd[1181]: Stopped KMail - E-Mail-Programm. 
[46844.431314] erlangen systemd[1]: Stopped Session 4 of User charlemagne. 
[46844.433058] erlangen systemd[8191]: Stopped target Main User Target. 
[46844.443770] erlangen systemd[8191]: Stopped User preferences database. 
[46844.445221] erlangen systemd[8191]: Stopped Virtual filesystem service - Media Transfer Protocol monitor. 
[46844.451472] erlangen systemd[8191]: Stopped D-Bus User Message Bus. 
[46844.451990] erlangen systemd[1181]: Stopped Terminal - Super User Mode. 
[46844.452787] erlangen systemd[8191]: Stopped KActivityManager Activity manager Service. 
[46844.453433] erlangen systemd[8191]: Stopped Sound Service. 
[46844.454211] erlangen systemd[8191]: Stopped Virtual filesystem service - disk device monitor. 
[46844.454972] erlangen systemd[8191]: Stopped Virtual filesystem service - Apple File Conduit monitor. 
[46844.455688] erlangen systemd[8191]: Stopped Virtual filesystem service - digital camera monitor. 
[46844.456393] erlangen systemd[8191]: Stopped Virtual filesystem service - GNOME Online Accounts monitor. 
[46844.457279] erlangen systemd[8191]: Stopped Accessibility services bus. 
[46844.458464] erlangen systemd[8191]: Stopped Virtual filesystem service. 
[46844.459463] erlangen systemd[8191]: Stopped target Basic System. 
[46844.459536] erlangen systemd[8191]: Stopped target Paths. 
[46844.459617] erlangen systemd[8191]: Stopped target Sockets. 
[46844.459684] erlangen systemd[8191]: Stopped target Timers. 
[46844.464189] erlangen systemd[1]: Stopped User Manager for UID 1000. 
[46844.559675] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000. 
[46844.817072] erlangen systemd[8191]: Stopped KMail - Mail Client. 
[46844.831942] erlangen systemd[1]: Stopped User Manager for UID 1001. 
[46844.888430] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1001. 
[46844.931487] erlangen systemd[1]: Stopped D-Bus System Message Bus. 
[46845.544229] erlangen systemd[1]: Stopped X Display Manager. 
[46845.556336] erlangen systemd[1]: Stopped Permit User Sessions. 
[46845.611482] erlangen systemd[1]: Stopped User Login Management. 
[46845.644610] erlangen systemd[1]: Stopped The Apache Webserver. 
[46845.644952] erlangen systemd[1]: Stopped target Remote File Systems. 
[46845.645124] erlangen systemd[1]: Stopped target System Time Synchronized. 
[46845.645746] erlangen systemd[1]: Stopped target System Time Set. 
[46845.647138] erlangen systemd[1]: Stopped NTP client/server. 
[46845.647399] erlangen systemd[1]: Stopped target Basic System. 
[46845.647621] erlangen systemd[1]: Stopped target Network. 
[46845.647836] erlangen systemd[1]: Stopped target Host and Network Name Lookups. 
[46845.648049] erlangen systemd[1]: Stopped target Path Units. 
[46845.654188] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
[46845.702185] erlangen systemd[1]: Stopped Watch for changes in CA certificates. 
[46845.702500] erlangen systemd[1]: Stopped CUPS Scheduler. 
[46845.738206] erlangen systemd[1]: Stopped Watch for changes in issue snippets. 
[46845.754195] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file. 
[46845.754314] erlangen systemd[1]: Stopped target Slice Units. 
[46845.754868] erlangen systemd[1]: Stopped target Socket Units. 
[46845.755849] erlangen systemd[1]: Stopped target System Initialization. 
[46845.756179] erlangen systemd[1]: Stopped target Local Encrypted Volumes. 
[46845.770213] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
[46845.770345] erlangen systemd[1]: Stopped target Local Verity Protected Volumes. 
[46845.773803] erlangen systemd[1]: Stopped Tell Plymouth To Write Out Runtime Data. 
[46845.774613] erlangen systemd[1]: Stopped Coldplug All udev Devices. 
[46845.782927] erlangen systemd[1]: Stopped Load AppArmor profiles. 
[46845.787447] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
[46845.792466] erlangen systemd[1]: Stopped Network Name Resolution. 
[46845.799450] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
[46845.799834] erlangen systemd[1]: Stopped target Local File Systems. 
[46845.817749] erlangen systemd[1]: Stopped Network Configuration. 
**erlangen:~ #**

46843.895675s - 46845.817749s = 1.922074 seconds shutdown time.

Systems using SySV init were plagued by pesky zombies which would never die.

6

This is hardly unusual, but it’s most commonly 1m 30s, and it’s not just openSUSE users it happens to. Systemd not unusually fails to have awareness of something it “thinks” is supposed to be running but that is not running, so thinks it needs to shut it down, but cannot because it is not running. It seems as though there are more than a few unit files that fail to test what needs testing at appropriate times. For me here, the most common troublemaker is the display manager/greeter, following updates.

7

No such behavior observed on host erlangen. I always run “zypper dup” in a root konsole: https://forums.opensuse.org/showthread.php/565261-90-Sekunden-stop-job-beim-Shutdown-Warum-Was?p=3100984#post3100984

Do you have detailed supporting evidence?

8

I rarely have X even running when I zypper dup.

https://forums.opensuse.org/showthread.php/565261-90-Sekunden-stop-job-beim-Shutdown-Warum-Was?p=3100984#post3100984
That lacks enough English for me to grok.

Do you have detailed supporting evidence?
I’ve never had both inclination to pursue and enough time available when it’s happened. For me it’s usually not sufficiently repeatable at will, which makes troubleshooting unusually difficult. I should at least have a clicker to use each time it happens so that I have an idea how often I see it. It’s happened at least 3 times in the past 24 hours, among probably at least 40 boots.

9

I sometime get this.

10

Check for persistent journal:

**erlangen:~ #** find /var/log/journal/ 
/var/log/journal/ 
/var/log/journal/94f3af277bac4a8eb57da425c9677379 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-997.journal 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-1000.journal 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/system.journal 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-998@0005d832d518dd61-dac4c7b35394f1b7.journal~ 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-998.journal 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-1001@0005d838ab2dc533-e6823518aafee484.journal~ 
/var/log/journal/94f3af277bac4a8eb57da425c9677379/user-1001.journal 
**erlangen:~ #**

If nonexistent enable it and report here by showing the journal of the related boot.

11

Hi
If I have a desktop running, I normally reboot as my user, not root. Depending on what is being upgraded I may even log out and switch to a console drop to multi-user to update.