Your message dated Thu, 28 Feb 2019 19:29:15 +0100
with message-id <[email protected]>
and subject line Re: systemd: several errors at shutdown, 2-minute timeout
has caused the Debian Bug report #921341,
regarding systemd: several errors at shutdown, 2-minute timeout
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
921341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921341
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 240-5
Severity: important
When rebooting after an upgrade, I got several error messages,
with a 2-minute timeout:
Feb 04 13:00:31 cventin systemd[1]: Stopping User Manager for UID 1000...
Feb 04 13:00:31 cventin systemd[1]: Stopping Disk Manager...
Feb 04 13:00:31 cventin systemd[1201]:
/usr/lib/systemd/user/systemd-exit.service:16: Failed to parse failure action
specifier, ignoring: exit-force
Feb 04 13:00:31 cventin systemd[1]: Stopping Modem Manager...
Feb 04 13:00:31 cventin systemd[1]: anacron.timer: Succeeded.
Feb 04 13:00:31 cventin systemd[1]: Stopped Trigger anacron every hour.
Feb 04 13:00:31 cventin systemd[1201]: systemd-exit.service: Service lacks both
ExecStart= and ExecStop= setting. Refusing.
Feb 04 13:00:31 cventin systemd[1201]: Failed to enqueue exit.target job: Unit
systemd-exit.service has a bad unit file setting.
[...]
Feb 04 13:02:31 cventin systemd[1]: [email protected]: State 'stop-sigterm'
timed out. Killing.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 1201
(systemd) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 8480
(pulseaudio) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 1439
(gvfsd) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 1444
(gvfsd-fuse) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 22747
(gpg-agent) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 19393
(dirmngr) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 2206
(at-spi-bus-laun) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 2211
(dbus-daemon) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 1326
(dbus-daemon) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 1436
(dconf-service) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Killing process 22757
(gnome-keyring-d) with signal SIGKILL.
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Main process exited,
code=killed, status=9/KILL
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Failed with result
'timeout'.
Feb 04 13:02:31 cventin systemd[1]: Stopped User Manager for UID 1000.
Feb 04 13:02:31 cventin systemd[1]: Stopping User Runtime Directory
/run/user/1000...
Feb 04 13:02:31 cventin systemd[28798]: [email protected]: Failed
to attach to cgroup
/system.slice/system-user\x2druntime\x2ddir.slice/[email protected]:
No such file or directory
Feb 04 13:02:31 cventin systemd[28798]: [email protected]: Failed
at step CGROUP spawning /lib/systemd/systemd-user-runtime-dir: No such file or
directory
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Control
process exited, code=exited, status=219/CGROUP
Feb 04 13:02:31 cventin systemd[1]: [email protected]: Failed with
result 'exit-code'.
Feb 04 13:02:31 cventin systemd[1]: Stopped User Runtime Directory
/run/user/1000.
Feb 04 13:02:31 cventin systemd[1]: Removed slice User Slice of UID 1000.
Feb 04 13:02:31 cventin systemd[1]: Stopping Permit User Sessions...
Feb 04 13:02:31 cventin systemd[1]: systemd-user-sessions.service: Succeeded.
Feb 04 13:02:31 cventin systemd[1]: Stopped Permit User Sessions.
Feb 04 13:02:31 cventin systemd[1]: Stopped target Remote File Systems.
Feb 04 13:02:31 cventin systemd[1]: Stopped target Network.
Feb 04 13:02:31 cventin systemd[1]: Stopping Network Manager...
[...]
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.13.2-7
ii libaudit1 1:2.8.4-2
ii libblkid1 2.33.1-0.1
ii libc6 2.28-5
ii libcap2 1:2.25-1.2
ii libcryptsetup12 2:2.0.6-1
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.6-2
ii libgpg-error0 1.35-1
ii libidn11 1.33-2.2
ii libip4tc0 1.8.2-3
ii libkmod2 25-2
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii libmount1 2.33.1-0.1
ii libpam0g 1.1.8-4
ii libseccomp2 2.3.3-3
ii libselinux1 2.8-1+b1
ii libsystemd0 240-5
ii mount 2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus 1.12.12-1
ii libpam-systemd 240-5
Versions of packages systemd suggests:
ii policykit-1 0.105-25
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.132
ii udev 240-5
-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=persistent
/etc/systemd/system.conf changed:
[Manager]
DefaultTimeoutStopSec=20s
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 4 Feb 2019 13:12:01 +0100 Vincent Lefevre <[email protected]>
wrote:
> Package: systemd
> Version: 240-5
> Severity: important
>
> When rebooting after an upgrade, I got several error messages,
> with a 2-minute timeout:
I've seen this issue as well, but only for the v239 -> v240 upgrade.
I haven't seen it for v232 -> v241 updates or for updates from v240 ->
v241.
I'm thus closing this bug report.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
