Your message dated Wed, 27 Jun 2018 23:22:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#897266: systemd: journalctl assertion failure
has caused the Debian Bug report #897266,
regarding systemd: journalctl assertion failure
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.)
--
897266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897266
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u2
Severity: normal
Dear Maintainer,
I tried to see cron messages using:
journalctl -fu cron
but journalctl aborted with an assertion failure:
Assertion 'p > 0' failed at ../src/journal/journal-file.c:2280, function
test_object_offset(). Aborting.
Aborted
[Exit 134 (SIGABRT)]
-- Package-specific info:
-- System Information:
Debian Release: 9.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.37-041437-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-3+deb9u2
ii libaudit1 1:2.6.7-2
ii libblkid1 2.29.2-1+deb9u1
ii libc6 2.24-11+deb9u3
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-4
ii libgcrypt20 1.7.6-2+deb9u2
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-6
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.2-1+deb9u1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b3
ii libsystemd0 232-25+deb9u2
ii mount 2.29.2-1+deb9u1
ii procps 2:3.3.12-3
ii util-linux 2.29.2-1+deb9u1
Versions of packages systemd recommends:
ii dbus 1.10.26-0+deb9u1
ii libpam-systemd 232-25+deb9u2
Versions of packages systemd suggests:
ii policykit-1 0.105-18
pn systemd-container <none>
ii systemd-ui 3-4+b1
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 232-25+deb9u2
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
UserTasksMax=50%
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 5 Jun 2018 19:55:44 +0200 Michael Biebl <[email protected]> wrote:
> Am 05.06.2018 um 19:37 schrieb Marc Lehmann:
> > I have an update to this, and can reproduce this: systemd is likely off the
> > hook for the corruption itself. Clearly it shouldn't crash, but I can
> > reproduce the corruption now, and it's a almost certainly a linux 4.14 bug.
>
> [snip]
>
> Thanks for the detailed reply!
Closing this bug report. If there is anything left to do on the systemd
side, feel free to reopen.
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
