Bug#941088: journald fails to restart
Am 26.09.19 um 08:35 schrieb Jörg Sommer: > Michael Biebl hat am Do 26. Sep, 00:00 (+0200) geschrieben: >> Am 25.09.19 um 14:22 schrieb Jörg Sommer: >>> Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben: output of systemd-analyze dump >>> >>> I've recorded a dump before and after restart. >> >> Seems to be missing? > > Yes. I've send them with a second mail. Sorry, seems I've missed that. >> One thing I noticed is that you seem to have hit the configured size >> limit for the journal. Not sure sure if it's related to your problem but >> you might try to reduce the journal size, say to 3G via journalctl >> --vacuum-size=3G > > Doesn't this happen automagically? I've never done this before and the > journal size stayed at 4GB. It should, yes. I just wanted to rule out any obvious issues that might be related to that auto-vacuum feature. That said, I don't really expect this to be the root cause and tbh so far I don't have an idea yet, what could be causing your problem. 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. -- 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
Bug#941088: journald fails to restart
Michael Biebl hat am Do 26. Sep, 00:00 (+0200) geschrieben: > Am 25.09.19 um 14:22 schrieb Jörg Sommer: > > Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben: > >> output of > >> systemd-analyze dump > > > > I've recorded a dump before and after restart. > > Seems to be missing? Yes. I've send them with a second mail. > One thing I noticed is that you seem to have hit the configured size > limit for the journal. Not sure sure if it's related to your problem but > you might try to reduce the journal size, say to 3G via journalctl > --vacuum-size=3G Doesn't this happen automagically? I've never done this before and the journal size stayed at 4GB. -- Alles, wovor wir Angst haben müssen, ist die Angst selbst. (Franklin D. Roosevelt) signature.asc Description: PGP signature
Bug#941088: journald fails to restart
Am 25.09.19 um 14:22 schrieb Jörg Sommer: > Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben: >> output of >> systemd-analyze dump > > I've recorded a dump before and after restart. Seems to be missing? One thing I noticed is that you seem to have hit the configured size limit for the journal. Not sure sure if it's related to your problem but you might try to reduce the journal size, say to 3G via journalctl --vacuum-size=3G (note, this will delete old log entries). So if you are concerned about that, please backup your journal files beforehand) -- 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
Bug#941088: journald fails to restart
Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben: > output of > systemd-analyze dump I've recorded a dump before and after restart. > systemctl list-jobs No jobs running. > > as well, please. > > It's odd that restarting journald pulls in a start of -.mount and > var.mount, as if this units were not active. > > Have you rebooted after the upgrade to v243? > If not, can you reproduce the problem after a reboot? Yes, I've rebooted after the upgrade and I have to reboot after every restart to get journald running. -- UNIX is user friendly, it's just picky about who its friends are signature.asc Description: PGP signature
Bug#941088: journald fails to restart
output of systemd-analyze dump systemctl list-jobs as well, please. It's odd that restarting journald pulls in a start of -.mount and var.mount, as if this units were not active. Have you rebooted after the upgrade to v243? If not, can you reproduce the problem after a reboot? signature.asc Description: OpenPGP digital signature
Bug#941088: journald fails to restart
Am 25.09.19 um 00:41 schrieb Jörg Sommer: > Michael Biebl hat am Di 24. Sep, 21:50 (+0200) geschrieben: >> Please attach >> journalctl -ub systemd-journald.service systemd-analyze log-level debug systemctl restart systemd-journald journalctl -alb journalctl --verify output please -- 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
Bug#941088: journald fails to restart
Michael Biebl hat am Di 24. Sep, 21:50 (+0200) geschrieben: > Please attach > journalctl -ub systemd-journald.service > ``` -- Logs begin at Thu 2019-04-18 18:24:57 CEST, end at Wed 2019-09-25 00:38:19 CEST. -- Sep 24 17:04:50 systemd-journald[465]: Journal started Sep 24 17:04:50 systemd-journald[465]: Runtime Journal (/run/log/journal/523cb54753234ed08c13ec497d0d3b64) is 8.0M, max 159.9M, 151.9M free. Sep 24 17:04:50 systemd-journald[465]: Time spent on flushing to /var is 72.525ms for 910 entries. Sep 24 17:04:50 systemd-journald[465]: System Journal (/var/log/journal/523cb54753234ed08c13ec497d0d3b64) is 3.9G, max 4.0G, 87.7M free. ``` -- “Politics is for the moment, equations are forever” (Albert Einstein) signature.asc Description: PGP signature
Bug#941088: journald fails to restart
Please attach journalctl -ub systemd-journald.service signature.asc Description: OpenPGP digital signature
Bug#941088: journald fails to restart
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 libaudit11:2.8.5-2 ii libblkid12.34-0.1 ii libc62.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-error01.36-7 ii libidn2-02.2.0-2 ii libip4tc21.8.3-2 ii libkmod2 26-3 ii liblz4-1 1.9.1-1 ii liblzma5 5.2.4-1+b1 ii libmount12.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 mount2.34-0.1 ii util-linux 2.34-0.1 Versions of packages systemd recommends: ii dbus1.13.12-1 ii libpam-systemd 243-2 Versions of packages systemd suggests: ii policykit-10.116-1 pn systemd-container Versions of packages systemd is related to: pn dracut 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
