Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
A stop job is running for Session 2 of user username
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
A stop job is running for Session 2 of user username
Debian 11 32bit on reboot. All applications were correctly closed. Is it please possible to avoid this ?
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
Not sure why you would be seeing stop jobs on reboot. This will give you error messages from the previous boot:
Code: Select all
# journalctl -b-1
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
Re: A stop job is running for Session 2 of user username
Thank you.FreewheelinFrank wrote: ↑2021-12-12 14:04 Not sure why you would be seeing stop jobs on reboot. This will give you error messages from the previous boot:
Code: Select all
# journalctl -b-1
Code: Select all
journalctl -b-1
Dec 12 10:30:02 maketopsite CRON[3640]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; t>
Dec 12 10:30:02 maketopsite CRON[3639]: pam_unix(cron:session): session closed for user root
Dec 12 10:32:13 maketopsite systemd[1]: Started Run anacron jobs.
Dec 12 10:32:14 maketopsite anacron[3698]: Anacron 2.3 started on 2021-12-12
Dec 12 10:32:14 maketopsite anacron[3698]: Normal exit (0 jobs run)
Dec 12 10:32:14 maketopsite systemd[1]: anacron.service: Succeeded.
Dec 12 10:33:02 maketopsite su[1356]: pam_unix(su-l:session): session closed for user root
Dec 12 10:33:06 maketopsite /usr/libexec/gdm-x-session[1251]: IceWM: Attention : 'icewm-menu-fdo' timed out!
Dec 12 10:33:12 maketopsite /usr/libexec/gdm-x-session[1251]: IceWM: reboot... (test -e /run/systemd/system && syste>
Dec 12 10:33:14 maketopsite systemd-logind[651]: System is rebooting.
Dec 12 10:33:14 maketopsite systemd[1]: unattended-upgrades.service: Succeeded.
Dec 12 10:33:14 maketopsite systemd[1]: Stopping Session 2 of user maketopsite.
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
Is that the end of the log or just the first page? This will give you the end:
Code: Select all
# journalctl -b-1 -n 100 --no-pager
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
Re: A stop job is running for Session 2 of user username
It is the only part of log which could contain that delay. I will check it once again.FreewheelinFrank wrote: ↑2021-12-12 15:23 Is that the end of the log or just the first page? This will give you the end:
Code: Select all
# journalctl -b-1 -n 100 --no-pager
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
OK, thanks.
Does the stop job complete after the default time (1.30m)?
Is this literally the last entry in journalctl?
I would expect some stuff after that like
Does the stop job complete after the default time (1.30m)?
Is this literally the last entry in journalctl?
Code: Select all
Dec 12 10:33:14 maketopsite systemd[1]: Stopping Session 2 of user maketopsite.
and hopefully something likeRemoved W
Deactivated X
Stopped Y
or some sort of "Failed" entry.Z timed out
Killing Z
Z Failed with result timeout
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
Re: A stop job is running for Session 2 of user username
Yes stop job complete after the default time (1.30m)FreewheelinFrank wrote: ↑2021-12-18 08:39 OK, thanks.
Does the stop job complete after the default time (1.30m)?
Is this literally the last entry in journalctl?
I would expect some stuff after that likeCode: Select all
Dec 12 10:33:14 maketopsite systemd[1]: Stopping Session 2 of user maketopsite.
and hopefully something likeRemoved W
Deactivated X
Stopped Y
or some sort of "Failed" entry.Z timed out
Killing Z
Z Failed with result timeout
This is not the last entry in journalctl:
(lines are in reverse order)
Code: Select all
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Daily man-db regeneration.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: avahi-daemon 0.8 exiting.
Dec 12 10:33:14 maketopsite systemd[1]: man-db.timer: Succeeded.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Daily rotation of log files.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
Dec 12 10:33:14 maketopsite systemd[1]: logrotate.timer: Succeeded.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: Leaving mDNS multicast group on interface eth3.IPv4 with address 10.0.0.40.
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: Leaving mDNS multicast group on interface eth3.IPv6 with address XXXXXXXXXX>
Dec 12 10:33:14 maketopsite systemd[1]: e2scrub_all.timer: Succeeded.
Dec 12 10:33:17 maketopsite smartd[649]: smartd is exiting (exit status 0)
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Daily atop restart.
Dec 12 10:33:17 maketopsite smartd[649]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD>
Dec 12 10:33:14 maketopsite systemd[1]: atop-rotate.timer: Succeeded.
Dec 12 10:33:17 maketopsite avahi-daemon[583]: Got SIGTERM, quitting.
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Daily apt download activities.
Dec 12 10:33:16 maketopsite gdm3[804]: Gdm: Failed to contact accountsservice: Error during the call StartServiceByName >
Dec 12 10:33:14 maketopsite systemd[1]: apt-daily.timer: Succeeded.
Dec 12 10:33:16 maketopsite dbus-daemon[587]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Ref>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Daily apt upgrade and clean activities.
Dec 12 10:33:16 maketopsite dbus-daemon[587]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit=>
Dec 12 10:33:14 maketopsite systemd[1]: apt-daily-upgrade.timer: Succeeded.
Dec 12 10:33:16 maketopsite smartd[649]: smartd received signal 15: Terminated
Dec 12 10:33:14 maketopsite systemd[1]: Stopped Trigger anacron every hour.
Dec 12 10:33:15 maketopsite atopacctd[589]: Terminated by signal 15
Dec 12 10:33:14 maketopsite systemd[1]: anacron.timer: Succeeded.
Dec 12 10:33:15 maketopsite ModemManager[715]: <info> caught signal, shutting down...
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Timers.
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr XXXXXXXXXX -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Sound Card.
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr 10.0.0.40 -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target RPC Port Mapper.
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr 10.0.0.40 -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Printer.
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr 10.0.0.40 -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Login Prompts.
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr 10.0.0.40 -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Multi-User System.
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (II) event0 - AT Translated Set 2 keyboard: device removed
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (**) Option "fd" "27"
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (II) event3 - PixArt Dell MS116 USB Optical Mouse: device rem>
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (**) Option "fd" "26"
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (II) event1 - Sleep Button: device removed
Dec 12 10:33:19 maketopsite /usr/libexec/gdm-x-session[1170]: (**) Option "fd" "25"
Dec 12 10:33:15 maketopsite ntpd[736]: XXXXXXX local addr 10.0.0.40 -> <null>
Dec 12 10:33:14 maketopsite systemd[1]: Stopped target Graphical Interface.
Dec 12 10:33:18 maketopsite /usr/libexec/gdm-x-session[1170]: (II) event2 - Power Button: device removed
Dec 12 10:33:18 maketopsite /usr/libexec/gdm-x-session[1170]: (**) Option "fd" "22"
Dec 12 10:33:14 maketopsite acpid[578]: exiting
Dec 12 10:33:14 maketopsite systemd[1]: Removed slice system-modprobe.slice.
Dec 12 10:33:18 maketopsite /usr/libexec/gdm-x-session[1250]: X connection to :0 broken (explicit kill or server shutdown).
Dec 12 10:33:14 maketopsite ntpd[736]: ntpd exiting on signal 15 (Terminated)
Dec 12 10:33:14 maketopsite systemd[1]: Removed slice system-getty.slice.
Dec 12 10:33:16 maketopsite at-spi-bus-launcher[1289]: X connection to :0 broken (explicit kill or server shutdown).
Dec 12 10:33:16 maketopsite /usr/libexec/gdm-x-session[1251]: X connection to :0 broken (explicit kill or server shutdown).
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
Normal output from journalctl is in chronological order. I don't understand why yours isn't. Was there some other filter applied?
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
Re: A stop job is running for Session 2 of user username
FreewheelinFrank wrote: ↑2021-12-18 10:39 Normal output from journalctl is in chronological order. I don't understand why yours isn't. Was there some other filter applied?
Code: Select all
journalctl -r
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
The entries don't seem to be in reverse chronological order.
I would expect
But we get
Then 14/16, 14/16, 14/15, 14/19, 14/18.
Maybe there is something I don't understand about how journalctl sorts entries?
Could you just post the output after
In forward chronological order?
I would expect
Code: Select all
10:33:19
10:33:18
10:33:17
10:33:16
10:33:15
10:33:14
Code: Select all
10:33:14
10:33:17
10:33:14
10:33:17
10:33:14
10:33:17
etc
Maybe there is something I don't understand about how journalctl sorts entries?
Could you just post the output after
Code: Select all
Stopping Session 2 of user maketopsite.
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times
Re: A stop job is running for Session 2 of user username
I understand thatFreewheelinFrank wrote: ↑2021-12-18 16:11 The entries don't seem to be in reverse chronological order.
I would expect
But we getCode: Select all
10:33:19 10:33:18 10:33:17 10:33:16 10:33:15 10:33:14
Then 14/16, 14/16, 14/15, 14/19, 14/18.Code: Select all
10:33:14 10:33:17 10:33:14 10:33:17 10:33:14 10:33:17 etc
Maybe there is something I don't understand about how journalctl sorts entries?
Could you just post the output after
In forward chronological order?Code: Select all
Stopping Session 2 of user maketopsite.
Code: Select all
10:33:14
10:33:17
10:33:14
10:33:17
10:33:14
10:33:17
Code: Select all
journalctl -r
Output you are asking for is already here: viewtopic.php?p=747324#p747324
It's result of
Code: Select all
journalctl -r
- FreewheelinFrank
- Global Moderator
- Posts: 2111
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 231 times
Re: A stop job is running for Session 2 of user username
It's not the order that's the problem (although you wouldn't have to manually reverse the lines - just remove the reverse switch) it's the fact that they jump around.
-
- Posts: 112
- Joined: 2021-01-20 08:44
- Has thanked: 8 times