Your message dated Thu, 26 Sep 2019 21:55:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#941088: journald fails to restart
has caused the Debian Bug report #941088,
regarding journald fails to restart
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.)
--
941088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941088
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 243-2
Severity: normal
Hi,
since the upgrade from 242-7, journald fails to restart:
```
# s restart systemd-journald.service
Job for systemd-journald.service failed because the control process exited with
error code.
See "systemctl status systemd-journald.service" and "journalctl -xe" for
details.
# sst systemd-journald.service
• systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-09-24 17:05:16 CEST; 7s ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 1881 ExecStart=/lib/systemd/systemd-journald (code=exited,
status=1/FAILURE)
Main PID: 1881 (code=exited, status=1/FAILURE)
CPU: 178ms
# j -xe |tail -n30
Sep 24 17:05:02 sudo[1026]: pam_unix(sudo:session): session opened for user
root by joerg(uid=0)
Sep 24 17:05:15 systemd[1]: Stopping Flush Journal to Persistent Storage...
-- Subject: A stop job for unit systemd-journal-flush.service has begun
execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit systemd-journal-flush.service has begun execution.
--
-- The job identifier is 960.
Sep 24 17:05:15 systemd[1]: systemd-journal-flush.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit systemd-journal-flush.service has successfully entered the 'dead'
state.
Sep 24 17:05:15 systemd[1]: Stopped Flush Journal to Persistent Storage.
-- Subject: A stop job for unit systemd-journal-flush.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit systemd-journal-flush.service has finished.
--
-- The job identifier is 960 and the job result is done.
Sep 24 17:05:15 systemd-journald[465]: Journal stopped
-- Subject: The journal has been stopped
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The system journal process has shut down and closed all currently
-- active journal files.
```
I don't know how to dig further into, to see what journald is doing.
Maybe, can you give me some advice?
Bye Jörg
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/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.53-4
ii libapparmor1 2.13.3-5
ii libaudit1 1:2.8.5-2
ii libblkid1 2.34-0.1
ii libc6 2.29-2
ii libcap2 1:2.25-2
ii libcryptsetup12 2:2.2.1-1
ii libgcrypt20 1.8.5-2
ii libgnutls30 3.6.9-5
ii libgpg-error0 1.36-7
ii libidn2-0 2.2.0-2
ii libip4tc2 1.8.3-2
ii libkmod2 26-3
ii liblz4-1 1.9.1-1
ii liblzma5 5.2.4-1+b1
ii libmount1 2.34-0.1
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.32-5+b1
ii libseccomp2 2.4.1-2
ii libselinux1 2.9-2+b2
ii libsystemd0 243-2
ii mount 2.34-0.1
ii util-linux 2.34-0.1
Versions of packages systemd recommends:
ii dbus 1.13.12-1
ii libpam-systemd 243-2
Versions of packages systemd suggests:
ii policykit-1 0.116-1
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.135
ii udev 242-7
-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]
/etc/systemd/system.conf changed [not included]
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Michael Biebl hat am Do 26. Sep, 14:45 (+0200) geschrieben:
> What you might try is to the ExecStart= in systemd-journald.service and
> use strace -vvv to start systemd-journald. Maybe that gives us a clue
> what the failure is.
This hint brought me to *dmesg* in the end and there, I've found the log
entry that the restart violates the AppArmor profile. I've installed it
long time ago and until 242 journald used /run/systemd, but with 243 it
uses /run/log.
Now, after I've updated the AppArmor profile, restart works.
I realised, that systemd puts its log messages in the kernel log buffer,
too. Hence, in such situations where journald is not available, dmesg is a
good place to look for informations.
Thanks for your help!
--
An SQL query walks into a bar and sees two tables.
He walks up to them and says: "Mind if I join you?"
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
