reached target shutdown for 2minutes when shutdown

Hi, how can I avoid, when I restart my computer, to have the reached target shutdown message for 2 minutes?

Hi, if that is due to https://bugzilla.opensuse.org/show_bug.cgi?id=1129476 and if you are not using logical volume management, you may disable lvm-related services or uninstall those packages (see comments 4 and 5 on the bug report).

Just a note:

I am using LVM. And I am not having this problem.

Maybe something LVM related is going into a deep sleep if not actually used. Or maybe the shutdown sequence is in the wrong order if LVM is not actually used.

A stop job unable to stop must be identified, then corrected. Typically a stop job that fails is due to a start job that never started.

manythanks orsobruno, I don’t use lvm, the packages mentioned in the bugzilla:
liblvm2app2_2
liblvm2cmd2_02
lvm2
are not installed in my system
the only similar name is
libLLVM5 - Libraries for LLVM
in the bugzilla the system hangs at:

 77.019608] systemd-journald[473]: systemd-journald stopped as pid 473
 167.020886] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
 167.027376] systemd-shutdown[1]: Sending SIGKILL to PID 484 (lvmetad). 

my system hang at

reached target shutdown

…it seems not related my issue to bugzilla bug :slight_smile:
ciao :slight_smile:

My took long time too. Even to boot. Some thread here on forum said to change

WAIT_FOR_INTERFACES="30"

in “/etc/sysconfig/network/config” to a low value. That was for boot, but my system shut down faster also.

here my system hangs:
http://paste.opensuse.org/31364367
http://paste.opensuse.org/31364367I don’t know how to report what is written there in text

https://freedesktop.org/wiki/Software/systemd/Debugging/

I am unable to read any of that. :frowning:

I don’t know how to report what is written there in text

journalctl -b -1 > someappropriatefilename.txt

should produce a log of the entire previous boot and shutdown named someappropriatefilename.txt that you can upload to paste.opensuse.org if by scanning through it yourself you fail to spot any clues.

journalctl -b -1 | grep ailed

will return log lines that include the string Failed, which might include a good enough clue.

Apparently red line near the top of screen is “failed to unmount /home”.

This message is shown during shutdown on my system, but it does not take extra time.
I have no idea why it fails.

manythanks mrmazda, I get this:

ago 05 22:46:21 server3TW.zapto.org dbus-daemon[1915]: [session uid=1000 pid=1915] Reloaded configurationago 05 22:47:34 server3TW.zapto.org dbus-daemon[1915]: [session uid=1000 pid=1915] Reloaded configuration
ago 05 22:47:34 server3TW.zapto.org dbus-daemon[1915]: [session uid=1000 pid=1915] Reloaded configuration
ago 05 22:55:56 server3TW.zapto.org kdesud[4390]: org.kde.kdesud: Exiting on signal  15
ago 05 22:55:56 server3TW.zapto.org at-spi-bus-launcher[2209]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
ago 05 22:55:56 server3TW.zapto.org at-spi-bus-launcher[2209]:       after 0 requests (0 known processed) with 0 events remaining.
ago 05 22:55:56 server3TW.zapto.org obexd[2259]: Terminating
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service - digital camera monitor...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping D-Bus User Message Bus...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped target Default.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Accessibility services bus...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service - Apple File Conduit monitor...
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopping Virtual filesystem service - disk device monitor...
ago 05 22:55:56 server3TW.zapto.org klauncher[1988]: The X11 connection broke: I/O error (code 1)
ago 05 22:55:56 server3TW.zapto.org kdeinit5[1996]: The X11 connection broke: I/O error (code 1)
ago 05 22:55:56 server3TW.zapto.org ksmserver[2025]: QProcess: Destroyed while process ("kwin_x11") is still running.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: at-spi-dbus-bus.service: Main process exited, code=exited, status=1/FAILURE
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Accessibility services bus.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: at-spi-dbus-bus.service: Unit entered failed state.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: at-spi-dbus-bus.service: Failed with result 'exit-code'.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service - Apple File Conduit monitor.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service - digital camera monitor.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service - disk device monitor.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped Virtual filesystem service.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped D-Bus User Message Bus.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped target Basic System.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped target Sockets.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped target Timers.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Stopped target Paths.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Closed D-Bus User Message Bus Socket.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Reached target Shutdown.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Starting Exit the Session...
ago 05 22:55:56 server3TW.zapto.org ksmserver[2025]: ksmserver: ksmserver: Fatal IO error: client killed
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Received SIGRTMIN+24 from PID 15723 (kill).
ago 05 22:55:56 server3TW.zapto.org systemd[1900]: pam_unix(systemd-user:session): session closed for user procuste

it doesn’t hang on failure or FAIL row, the behaviour is that everything go well and fast until:

ago 05 22:55:56 server3TW.zapto.org systemd[1899]: Reached target Shutdown.

here it hangs for two minutes then shutdown…

and here is the failed lines:

procuste@server3TW:~> journalctl -b -1 | grep ailed
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
ago 05 21:08:33 server3TW.zapto.org kdeinit5[1996]: "XOpenDevice f**ailed** on device id '2'!"
ago 05 21:08:33 server3TW.zapto.org kdeinit5[1996]: "XOpenDevice f**ailed** on device id '3'!"
ago 05 21:08:35 server3TW.zapto.org org_kde_powerdevil[2111]: powerdevil: org.kde.powerdevil.backlighthelper.brightness f**ail**
ed
ago 05 21:08:35 server3TW.zapto.org mate-screensave[2262]: F**ailed** to get session presence proxy: Could not get owner of name
 'org.gnome.SessionManager': no such name
ago 05 21:08:36 server3TW.zapto.org plasmashell[2040]: kde.dataengine.notifications`: F**ailed** to register Notifications servi
ce
ago 05 21:08:39 server3TW.zapto.org plasmashell[2040]: kde.dataengine.notifications`: F**ailed** to register Notifications servi
ce
ago 05 21:08:58 server3TW.zapto.org pulseaudio[2088]: [pulseaudio] bluez5-util.c: GetManagedObjects() f**ailed**: org.freedeskto
p.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes
sage bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ago 05 21:08:58 server3TW.zapto.org kdeinit5[1996]: org.kde.bluez: PendingCall Error: "F**ailed** to activate service 'org.bluez
': timed out (service_start_timeout=25000ms)"
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: at-spi-dbus-bus.service: Unit entered f**ailed** state.
ago 05 22:55:56 server3TW.zapto.org systemd[1899]: at-spi-dbus-bus.service: F**ailed** with result 'exit-code'.
procuste@server3TW:~> 


That output was limited to your regular user. I wouldn’t expect KDE errors to delay shutdown 2 minutes, but maybe someone else knows better.

Logging in as root, using sudo, or being a member of wheel and/or adm and/or systemd-journal groups can get the full journal output, which I believe is what needs to be examined.

manythanks, I added the user procuste at wheel and adm and systemd-journal groups, rebooted and rebooted again, here is the output of

journalctl -b -1 > someappropriatefilename.txt

http://paste.opensuse.org/31314602

There are so many problems there I don’t know where to start, or what to do about them. In addition to failing to unmount /home:

  • 85 ssh password failures
  • kglobalaccel5[5942]: qt.qpa.plugin: Could not load the Qt platform plugin “wayland” in “” even though it was found.
  • kglobalaccel5[6531]: qt.qpa.plugin: Could not load the Qt platform plugin “wayland” in “” even though it was found.
  • a flood of “ksmserver[6149]: QSocketNotifier: Invalid socket 11 and type ‘Read’, disabling…” appear every 30 seconds, over 79k lines of them total, possibly overloading the logging system at shutdown time
  • 32 lines about coredumps, ending with “systemd-coredump[11229]: Failed to connect to coredump service: Connection refused”
  • 157 lines with the string Failed

This may require a bug report to find a solution.

If you close the plasma session and shutdown from the greeter instead of shutting down or rebooting directly from plasma, does it help?

If you close the plasma session and open an IceWM session before shutting down or rebooting, does it help?

If instead of opening Plasma via SDDM you login on say vtty3 and start plasma with startx, then close the session before trying to shutdown or reboot, does it help?

Does it help if you disable remote logins via ssh?

Is the problem the same whether your plasma session is in xorg or wayland?

Do you have a DNS mounted folder? Unmount it at log out or try my previous replay.
/J
Edit: A folder mounted on an other machine on a Free Dynamic DNS service?

@pier_andreit:

Btrfs system partition?

Btrfs housekeeping active during the system poweroff?

yes, I have a Free Dynamic DNS service but I don’t have any folder mounted

no Btrfs system partition, I use ext3/4 ntfs partitions
Btrfs housekeeping active during the system poweroff?=this I don’t know