You are not logged in.

#1 2020-03-24 08:54:29

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

waiting for shutdown, reboot (from beginning of march)

Hi,

I cant remember but it must have happened after a pacman -Syu.

My laptop (LXDE/LXDM) used to powered off in less than 3 seconds, but from the beginning of march, I have to wait for about 1mn 30sec after one shutdown, poweroff or reboot command.

Here are some interesting infos:

In the first times, either by a command or hitting the logout button>shutdown, I was normaly sent to a terminal screen. There, systemd said something like "running user task" (duration about 1mn 30sec, sometimes more). Before the remaining operations flushed, I could see the very first line saying something about "login". Perhaps it was about systemd-logind, but it was too fast for me.

So I tried these :
- hit the logout button, then loggout again. Exit from LXDE to LXDM. Then select shutdown : quick/normal shutdown
- in a LXDE session, hit ctrl-alt-F2, login as a regular user, entered a poweroff command : quick/normal shutdown

But I still can't identify the problem.

I made a systemctl status/--failed : everything ok, no fail, including logind.service.

Tried to uncomment reset=1 option in /etc/lxdm/lxdm.conf to refresh xserver on logout, but have the same issue.

Made two recent pacman -Syu but no changes.

Thanks for help.

Last edited by AlphaKiwi (2020-03-24 17:27:45)

Offline

#2 2020-03-24 11:08:36

xerxes_
Member
Registered: 2018-04-29
Posts: 253

Re: waiting for shutdown, reboot (from beginning of march)

Look at the end of listing of command 'journalctl -b-1' or if unsure post output here in [ code ] tags.

Offline

#3 2020-03-24 13:06:25

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

Thanks xerres_

Below are the lasts lines in a 'journalctl -b-1'.

...skipping...
mars 24 13:36:17 venus systemd[1]: Stopped target Basic System.
mars 24 13:36:17 venus systemd[1]: Stopped target Paths.
mars 24 13:36:17 venus systemd[1]: Stopped target Slices.
mars 24 13:36:17 venus systemd[1]: Removed slice User and Session Slice.
mars 24 13:36:17 venus systemd[1]: Stopped target Sockets.
mars 24 13:36:17 venus systemd[1]: dbus.socket: Succeeded.
mars 24 13:36:17 venus systemd[1]: Closed D-Bus System Message Bus Socket.
mars 24 13:36:17 venus systemd[1]: Stopped target System Initialization.
mars 24 13:36:17 venus systemd[1]: Stopped target Local Encrypted Volumes.
mars 24 13:36:17 venus systemd[1]: systemd-ask-password-console.path: Succeeded.
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.079:70): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nftables comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
mars 24 13:36:17 venus systemd[1]: systemd-ask-password-wall.path: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
mars 24 13:36:17 venus systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
mars 24 13:36:17 venus systemd[1]: systemd-binfmt.service: Succeeded.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Stopped Set Up Additional Binary Formats.
mars 24 13:36:17 venus systemd[1]: systemd-sysctl.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Apply Kernel Variables.
mars 24 13:36:17 venus systemd[1]: systemd-modules-load.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Load Kernel Modules.
mars 24 13:36:17 venus systemd[1]: Stopping Network Time Synchronization...
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
mars 24 13:36:17 venus systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded.
mars 24 13:36:17 venus audit[1565]: SYSTEM_SHUTDOWN pid=1565 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:intel_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: systemd-timesyncd.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Network Time Synchronization.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
mars 24 13:36:17 venus systemd[1]: systemd-update-utmp.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped Create Volatile Files and Directories.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus systemd[1]: Stopped target Local File Systems.
mars 24 13:36:17 venus systemd[1]: Unmounting /boot...
mars 24 13:36:17 venus systemd[1]: Unmounting /extra...
mars 24 13:36:17 venus systemd[1]: Unmounting /home...
mars 24 13:36:17 venus systemd[1]: Unmounting Temporary Directory (/tmp)...
mars 24 13:36:17 venus systemd[1]: Stopping Flush Journal to Persistent Storage...
mars 24 13:36:17 venus systemd[1]: boot.mount: Succeeded.
mars 24 13:36:17 venus systemd[1]: Unmounted /boot.
mars 24 13:36:17 venus systemd[1]: tmp.mount: Succeeded.
mars 24 13:36:17 venus systemd[1]: Unmounted Temporary Directory (/tmp).
mars 24 13:36:17 venus systemd[1]: Stopped target Swap.
mars 24 13:36:17 venus systemd[1]: Deactivating swap /dev/disk/by-id/ata-WDC_WD10SPZX-00Z10T0_WD-WX81EB75MZPW-part1...
mars 24 13:36:17 venus systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD.service: Succeeded.
mars 24 13:36:17 venus systemd[1]: Stopped File System Check on /dev/disk/by-label/EFI_SSD.
mars 24 13:36:17 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

...looks like reporting everything is ok(?!).

Offline

#4 2020-03-24 13:36:19

Skunky
Member
Registered: 2018-01-25
Posts: 145

Re: waiting for shutdown, reboot (from beginning of march)

All this stuff seems to stop succesfully, can you post complete journal?

Offline

#5 2020-03-24 14:39:25

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

Thanks for the help Skunky.

Did a 'journalctl -p 5 -x -b-1' (is this ok?)

-- Logs begin at Wed 2020-03-18 20:54:12 CET, end at Tue 2020-03-24 15:24:45 CET. --
mars 24 13:27:25 venus kernel: Linux version 5.5.10-arch1-1 (linux@archlinux) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) >
mars 24 13:27:25 venus kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ca579df0-0590-4537-b4fa-fff5ce9>
mars 24 13:27:25 venus kernel: random: get_random_bytes called from start_kernel+0x3ab/0x586 with crng_init=0
mars 24 13:27:25 venus kernel: *** VALIDATE tmpfs ***
mars 24 13:27:25 venus kernel: *** VALIDATE proc ***
mars 24 13:27:25 venus kernel: *** VALIDATE cgroup1 ***
mars 24 13:27:25 venus kernel: *** VALIDATE cgroup2 ***
mars 24 13:27:25 venus kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/>
mars 24 13:27:25 venus kernel:  #5 #6 #7
mars 24 13:27:25 venus kernel: audit: type=2000 audit(1585052841.376:1): state=initialized audit_enabled=0 res=1
mars 24 13:27:25 venus kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
mars 24 13:27:25 venus kernel: *** VALIDATE bpf ***
mars 24 13:27:25 venus kernel: VFS: Disk quotas dquot_6.6.0
mars 24 13:27:25 venus kernel: *** VALIDATE ramfs ***
mars 24 13:27:25 venus kernel: *** VALIDATE hugetlbfs ***
mars 24 13:27:25 venus kernel: Initialise system trusted keyrings
mars 24 13:27:25 venus kernel: Key type blacklist registered
mars 24 13:27:25 venus kernel: Key type asymmetric registered
mars 24 13:27:25 venus kernel: Asymmetric key parser 'x509' registered
mars 24 13:27:25 venus kernel: efifb: Ignoring BGRT: unexpected or invalid BMP data
mars 24 13:27:25 venus kernel: Loading compiled-in X.509 certificates
mars 24 13:27:25 venus kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 51de9dd133a02ab2d45229cbd2a7081c>
mars 24 13:27:25 venus kernel: Key type ._fscrypt registered
mars 24 13:27:25 venus kernel: Key type .fscrypt registered
mars 24 13:27:25 venus kernel: Key type big_key registered
mars 24 13:27:25 venus kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot wit>
mars 24 13:27:25 venus kernel: SCSI subsystem initialized
mars 24 13:27:25 venus kernel: usb: port power management may be unreliable
mars 24 13:27:25 venus kernel: scsi 0:0:0:0: Direct-Access     ATA      WDC WD10SPZX-00Z 1A01 PQ: 0 ANSI: 5
mars 24 13:27:25 venus kernel: scsi 2:0:0:0: Direct-Access     ATA      LDLC             3A0  PQ: 0 ANSI: 5
mars 24 13:27:25 venus kernel: sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
mars 24 13:27:25 venus kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
...skipping...
mars 24 13:34:47 venus kernel: audit: type=1131 audit(1585053287.049:63): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: State 'stop-sigterm' timed out. Killing.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Killing process 1162 (zeitgeist-fts) with signal SIGKILL.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Killing process 1173 (gdbus) with signal SIGKILL.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Main process exited, code=killed, status=9/KILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit UNIT has exited.
-- 
-- The process' exit code is 'killed' and its exit status is 9.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit UNIT has entered the 'failed' state with result 'timeout'.
mars 24 13:36:16 venus systemd[1019]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[s>
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.819:64): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.832:65): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:16 venus wpa_supplicant[922]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.842:66): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:16 venus wpa_supplicant[922]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
mars 24 13:36:17 venus wpa_supplicant[922]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mars 24 13:36:17 venus wpa_supplicant[922]: wlan0: CTRL-EVENT-TERMINATING
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.046:67): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.066:68): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.076:69): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.079:70): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:71): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:72): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:73): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
lines 168-200/200 (END)
mars 24 13:34:47 venus kernel: audit: type=1131 audit(1585053287.049:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: State 'stop-sigterm' timed out. Killing.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Killing process 1162 (zeitgeist-fts) with signal SIGKILL.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Killing process 1173 (gdbus) with signal SIGKILL.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Main process exited, code=killed, status=9/KILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit UNIT has exited.
-- 
-- The process' exit code is 'killed' and its exit status is 9.
mars 24 13:36:16 venus systemd[1018]: zeitgeist-fts.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit UNIT has entered the 'failed' state with result 'timeout'.
mars 24 13:36:16 venus systemd[1019]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[alexis] ruser=[<unknown>] rhost=[<unknown>]
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.819:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.832:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:16 venus wpa_supplicant[922]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
mars 24 13:36:16 venus kernel: audit: type=1131 audit(1585053376.842:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:16 venus wpa_supplicant[922]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
mars 24 13:36:17 venus wpa_supplicant[922]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mars 24 13:36:17 venus wpa_supplicant[922]: wlan0: CTRL-EVENT-TERMINATING
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.046:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.066:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.076:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.079:70): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nftables comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 13:36:17 venus kernel: audit: type=1131 audit(1585053377.096:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

...at least something wrong can be seen.

Offline

#6 2020-03-24 15:10:12

Skunky
Member
Registered: 2018-01-25
Posts: 145

Re: waiting for shutdown, reboot (from beginning of march)

The service

zeitgeist-fts.service

seems to hang for a while before getting sigtermed, i never used Zeitgeist so i don't think i can i help you further

Offline

#7 2020-03-24 17:02:14

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

Thanks again Skunky, that is probably from where I should start.

Any idea anyone?

Offline

#8 2020-03-24 17:18:28

sevendogs
Member
From: Texas
Registered: 2016-01-24
Posts: 175

Re: waiting for shutdown, reboot (from beginning of march)

According to the article Skunky linked, it is only used by a few apps. I would disable the service to see if the problem goes away then if the apps you do use seem to function OK, then all may be well.  This thread has led me to investigate my installation as well - I am not having this issue but since zeitgeist is a  "service which logs user activities and events", I am not too keen on having it installed if I don't have to.


"Give a man a truth and he will think for a day. Teach a man to reason and he will think for a lifetime"

Offline

#9 2020-03-24 17:43:01

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

I agree with you sevendogs.
I checked too at zeitgeist, and understood it was a dependance of Midori (installed a few weeks ago).
As I don't need Midori for now I uninstalled with pacman -Rs, it removed Midori *and* Zeitgeist.

Then I tried again to shutdown and... same issue, but another reading of 'journalctl -p 5 -x -b-1' below :

...skipping...
mars 24 18:17:45 venus polkitd[1083]: Finished loading, compiling and executing 4 rules
mars 24 18:17:45 venus polkitd[1083]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
mars 24 18:17:45 venus polkitd[1083]: Registered Authentication Agent for unix-session:1 (system bus name :1.23 [lxpolkit], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
mars 24 18:17:45 venus wpa_supplicant[921]: wlan0: SME: Trying to authenticate with a4:3e:51:f3:47:d3 (SSID='Collapse_is_now' freq=2437 MHz)
mars 24 18:17:45 venus wpa_supplicant[921]: wlan0: Trying to associate with a4:3e:51:f3:47:d3 (SSID='Collapse_is_now' freq=2437 MHz)
mars 24 18:17:45 venus udisksd[1154]: udisks daemon version 2.8.4 starting
mars 24 18:17:46 venus udisksd[1154]: Acquired the name org.freedesktop.UDisks2 on the system message bus
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: SME: Trying to authenticate with a4:3e:51:f3:47:d3 (SSID='Collapse_is_now' freq=2437 MHz)
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: Trying to associate with a4:3e:51:f3:47:d3 (SSID='Collapse_is_now' freq=2437 MHz)
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: Associated with a4:3e:51:f3:47:d3
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: WPA: Key negotiation completed with a4:3e:51:f3:47:d3 [PTK=CCMP GTK=TKIP]
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-CONNECTED - Connection to a4:3e:51:f3:47:d3 completed [id=0 id_str=]
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-61 noise=9999 txrate=1000
mars 24 18:17:54 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-61 noise=9999 txrate=130000
mars 24 18:17:54 venus kernel: kauditd_printk_skb: 4 callbacks suppressed
mars 24 18:17:54 venus kernel: audit: type=1130 audit(1585070274.708:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
mars 24 18:18:05 venus kernel: audit: type=1131 audit(1585070285.248:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
mars 24 18:18:07 venus kernel: audit: type=1131 audit(1585070287.971:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:42 venus kernel: usb 1-4: Device not responding to setup address.
mars 24 18:19:42 venus kernel: usb 1-4: Device not responding to setup address.
mars 24 18:19:42 venus kernel: usb 1-4: device not accepting address 6, error -71
mars 24 18:19:53 venus systemd-logind[817]: System is powering down.
mars 24 18:19:53 venus polkitd[1083]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.23, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.367:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-repart comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.371:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=alsa-restore comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus udisksd[1154]: udisks daemon version 2.8.4 exiting
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.384:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.384:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a4:3e:51:f3:47:d3 reason=3 locally_generated=1
mars 24 18:19:53 venus NetworkManager[837]: <warn>  [1585070393.4995] sup-iface[0x55a1864b6900,wlan0]: connection disconnected (reason -3)
mars 24 18:19:53 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
mars 24 18:19:53 venus kernel: audit: type=1130 audit(1585070393.507:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.507:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.584:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.724:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lxdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.767:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tlp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.767:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cpupower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus systemd[1]: session-1.scope: Stopping timed out. Killing.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1072 (pcmanfm) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1095 (gmain) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Failed with result 'timeout'.
mars 24 18:21:23 venus systemd[1018]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[alexis] ruser=[<unknown>] rhost=[<unknown>]
mars 24 18:21:23 venus kernel: kauditd_printk_skb: 4 callbacks suppressed
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.471:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.481:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus wpa_supplicant[921]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.491:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus wpa_supplicant[921]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
mars 24 18:21:23 venus wpa_supplicant[921]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mars 24 18:21:23 venus wpa_supplicant[921]: wlan0: CTRL-EVENT-TERMINATING
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.701:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.708:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.721:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.724:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nftables comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.744:70): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.758:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 18:21:23 venus kernel: audit: type=1131 audit(1585070483.758:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

It seems to point to 'session-1'... and getting a little tougher.

Offline

#10 2020-03-24 18:10:42

sevendogs
Member
From: Texas
Registered: 2016-01-24
Posts: 175

Re: waiting for shutdown, reboot (from beginning of march)

What are these 2 lines for? They seem to be the only ones that don't show "success" at the end.

mars 24 18:19:53 venus kernel: audit: type=1130 audit(1585070393.507:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.507:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >

"Give a man a truth and he will think for a day. Teach a man to reason and he will think for a lifetime"

Offline

#11 2020-03-24 18:36:33

loqs
Member
Registered: 2014-03-06
Posts: 10,045

Re: waiting for shutdown, reboot (from beginning of march)

mars 24 18:21:23 venus systemd[1]: session-1.scope: Stopping timed out. Killing.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1072 (pcmanfm) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1095 (gmain) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Failed with result 'timeout'.

If you do not start pcmanfm does the session still timeout?

Offline

#12 2020-03-24 21:01:25

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

sevendogs wrote:

What are these 2 lines for? They seem to be the only ones that don't show "success" at the end.

mars 24 18:19:53 venus kernel: audit: type=1130 audit(1585070393.507:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mars 24 18:19:53 venus kernel: audit: type=1131 audit(1585070393.507:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >

Well, my knowledge ends very, very near this.


loqs wrote:
mars 24 18:21:23 venus systemd[1]: session-1.scope: Stopping timed out. Killing.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1072 (pcmanfm) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Killing process 1095 (gmain) with signal SIGKILL.
mars 24 18:21:23 venus systemd[1]: session-1.scope: Failed with result 'timeout'.

If you do not start pcmanfm does the session still timeout?

Yes, same timeout.
In fact just login from LXDM, opening a terminal and putting a 'shutdown -h now' command produces the same issue.

One resulting 'journalctl -p 5 -x -b-1' is below :

...skipping...
mars 24 20:40:33 venus wpa_supplicant[916]: wlan0: CTRL-EVENT-CONNECTED - Connection to a4:3e:51:f3:47:d3 completed [id=0 id_str=]
mars 24 20:40:33 venus wpa_supplicant[916]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-59 noise=9999 txrate=1000
mars 24 20:40:33 venus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.7012] device (wlan0): supplicant interface state: 4-way handshake -> completed
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.7012] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Collapse_is_now"
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.7013] device (p2p-dev-wlan0): supplicant management interface state: 4-way handshake -> completed
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.7015] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.7022] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
mars 24 20:40:33 venus wpa_supplicant[916]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise=9999 txrate=144400
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8712] dhcp4 (wlan0): option dhcp_lease_time      => '86400'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8713] dhcp4 (wlan0): option domain_name          => 'home'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8714] dhcp4 (wlan0): option domain_name_servers  => '192.168.1.1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8714] dhcp4 (wlan0): option expiry               => '1585165233'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8714] dhcp4 (wlan0): option ip_address           => '192.168.1.204'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8715] dhcp4 (wlan0): option next_server          => '192.168.1.1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8715] dhcp4 (wlan0): option requested_broadcast_address => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8715] dhcp4 (wlan0): option requested_domain_name => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8716] dhcp4 (wlan0): option requested_domain_name_servers => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8716] dhcp4 (wlan0): option requested_domain_search => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8716] dhcp4 (wlan0): option requested_host_name  => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8717] dhcp4 (wlan0): option requested_interface_mtu => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8717] dhcp4 (wlan0): option requested_ms_classless_static_routes => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8717] dhcp4 (wlan0): option requested_nis_domain => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8717] dhcp4 (wlan0): option requested_nis_servers => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8718] dhcp4 (wlan0): option requested_ntp_servers => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8718] dhcp4 (wlan0): option requested_rfc3442_classless_static_routes => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8718] dhcp4 (wlan0): option requested_root_path  => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8718] dhcp4 (wlan0): option requested_routers    => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8718] dhcp4 (wlan0): option requested_static_routes => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8719] dhcp4 (wlan0): option requested_subnet_mask => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8719] dhcp4 (wlan0): option requested_time_offset => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8719] dhcp4 (wlan0): option requested_wpad       => '1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8719] dhcp4 (wlan0): option routers              => '192.168.1.1'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8720] dhcp4 (wlan0): option subnet_mask          => '255.255.255.0'
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8720] dhcp4 (wlan0): state changed unknown -> bound
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8755] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mars 24 20:40:33 venus dbus-daemon[813]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=835 comm="/usr/bin/NetworkManager -->
mars 24 20:40:33 venus systemd[1]: Starting Network Manager Script Dispatcher Service...
mars 24 20:40:33 venus dbus-daemon[813]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mars 24 20:40:33 venus systemd[1]: Started Network Manager Script Dispatcher Service.
mars 24 20:40:33 venus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 20:40:33 venus kernel: kauditd_printk_skb: 4 callbacks suppressed
mars 24 20:40:33 venus kernel: audit: type=1130 audit(1585078833.881:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8885] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8887] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8894] manager: NetworkManager state is now CONNECTED_LOCAL
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8920] manager: NetworkManager state is now CONNECTED_SITE
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8921] policy: set 'Collapse_is_now' (wlan0) as default for IPv4 routing and DNS
mars 24 20:40:33 venus dbus-daemon[813]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.12' (uid=0 pid=835 comm="/usr/bin/NetworkManager --no-daemon >
mars 24 20:40:33 venus dbus-daemon[813]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mars 24 20:40:33 venus NetworkManager[835]: <info>  [1585078833.8948] device (wlan0): Activation: successful, device activated.
mars 24 20:40:34 venus NetworkManager[835]: <info>  [1585078834.0888] manager: NetworkManager state is now CONNECTED_GLOBAL
mars 24 20:40:44 venus systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mars 24 20:40:44 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 20:40:44 venus kernel: audit: type=1131 audit(1585078844.275:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
mars 24 20:40:47 venus systemd-timesyncd[805]: Initial synchronization to time server 212.85.158.10:123 (2.fr.pool.ntp.org).
mars 24 20:40:48 venus systemd[1]: systemd-hostnamed.service: Succeeded.
mars 24 20:40:48 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 20:40:48 venus kernel: audit: type=1131 audit(1585078848.280:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Offline

#13 2020-03-24 21:43:18

loqs
Member
Registered: 2014-03-06
Posts: 10,045

Re: waiting for shutdown, reboot (from beginning of march)

I can not see session-1.scope: Stopping timed out. Killing. in the latest output you posted.
Please also do not filter by priority and catalog messages just make the output harder to read.

Offline

#14 2020-03-24 21:49:02

xerxes_
Member
Registered: 2018-04-29
Posts: 253

Re: waiting for shutdown, reboot (from beginning of march)

From your last log it doesn't look you have to wait long for shutdown - just 15 seconds, not 1m30s.

Offline

#15 2020-03-25 01:37:05

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

loqs wrote:

I can not see session-1.scope: Stopping timed out. Killing. in the latest output you posted.
Please also do not filter by priority and catalog messages just make the output harder to read.

Ok loqs, thanks again. I manage myself with Arch, I'm not a real beginner but I have not the value of mosts users here.
What about a 'journalctl -x -b-1'? (is this the best display?)

...skipping...
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) tmp.mount a commencé à s'arrêter.
mars 24 20:39:51 venus systemd[1]: Stopping Flush Journal to Persistent Storage...
-- Subject: L'unité (unit) systemd-journal-flush.service a commencé à s'arrêter
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) systemd-journal-flush.service a commencé à s'arrêter.
mars 24 20:39:51 venus systemd[1]: boot.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- The unit boot.mount has successfully entered the 'dead' state.
mars 24 20:39:51 venus systemd[1]: Unmounted /boot.
-- Subject: L'unité (unit) boot.mount a terminé son arrêt
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) boot.mount a terminé son arrêt.
mars 24 20:39:51 venus systemd[1]: tmp.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- The unit tmp.mount has successfully entered the 'dead' state.
mars 24 20:39:51 venus systemd[1]: Unmounted Temporary Directory (/tmp).
-- Subject: L'unité (unit) tmp.mount a terminé son arrêt
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) tmp.mount a terminé son arrêt.
mars 24 20:39:51 venus systemd[1]: Stopped target Swap.
-- Subject: L'unité (unit) swap.target a terminé son arrêt
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) swap.target a terminé son arrêt.
mars 24 20:39:51 venus systemd[1]: Deactivating swap /dev/disk/by-id/ata-WDC_WD10SPZX-00Z10T0_WD-WX81EB75MZPW-part1...
-- Subject: L'unité (unit) dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d00Z10T0_WD\x2dWX81EB75MZPW\x2dpart1.swap a commencé à s'arrêter
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d00Z10T0_WD\x2dWX81EB75MZPW\x2dpart1.swap a commencé à s'arrêter.
mars 24 20:39:51 venus systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- The unit systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD.service has successfully entered the 'dead' state.
mars 24 20:39:51 venus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 24 20:39:51 venus systemd[1]: Stopped File System Check on /dev/disk/by-label/EFI_SSD.
-- Subject: L'unité (unit) systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD.service a terminé son arrêt
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) systemd-fsck@dev-disk-by\x2dlabel-EFI_SSD.service a terminé son arrêt.

xerxes_ wrote:

From your last log it doesn't look you have to wait long for shutdown - just 15 seconds, not 1m30s.

Yes, I had was luck on this shutdown. But... WHERE DO YOU SEE THAT??? cool

Last edited by AlphaKiwi (2020-03-25 01:44:52)

Offline

#16 2020-03-25 19:34:31

xerxes_
Member
Registered: 2018-04-29
Posts: 253

Re: waiting for shutdown, reboot (from beginning of march)

AlphaKiwi wrote:

Yes, I had was luck on this shutdown. But... WHERE DO YOU SEE THAT???

...skipping...
mars 24 20:40:33 venus wpa_supplicant[916]: wlan0 ...
...
mars 24 20:40:48 venus kernel: audit: ...

48 - 33 =

Offline

#17 2020-03-25 19:56:08

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

xerxes_ wrote:
mars 24 20:40:33 venus wpa_supplicant[916]: wlan0 ...
...
mars 24 20:40:48 venus kernel: audit: ...

48 - 33 =

Dead simple roll big_smile
I assume I didn't catch it from the first log (in fact I couldn't). So from this point of view, I missed every other logs.

Well it's ok, I've learned something (out of beeing seriously aware).
Thanks xerxes_

Offline

#18 2020-03-25 20:15:14

loqs
Member
Registered: 2014-03-06
Posts: 10,045

Re: waiting for shutdown, reboot (from beginning of march)

AlphaKiwi wrote:
loqs wrote:

I can not see session-1.scope: Stopping timed out. Killing. in the latest output you posted.
Please also do not filter by priority and catalog messages just make the output harder to read.

Ok loqs, thanks again. I manage myself with Arch, I'm not a real beginner but I have not the value of mosts users here.
What about a 'journalctl -x -b-1'? (is this the best display?)

No -x adds catalog messages.  Almost all of the last example is just catalog messages to the extent it has no useful information.

Offline

#19 2020-03-26 10:22:07

AlphaKiwi
Member
Registered: 2015-07-12
Posts: 9

Re: waiting for shutdown, reboot (from beginning of march)

loqs wrote:

No -x adds catalog messages.  Almost all of the last example is just catalog messages to the extent it has no useful information.

Argh. I understand I've been polluting this thread and this forum hmm, sorry everybody.
Removing -x catalog option and descending priority step by step allows a more understandable shutdown process. I'm still learning smile

I've seen strange things from 'warning' severity, I'll take a look at that.

systemd[1]: session-1.scope: Stopping timed out. Killing.

...seems to be the first hint, I'll search a bit from there.

Thanks again.

Offline

Board footer

Powered by FluxBB