Package: libsystemd-journal0 Version: 44-4 Severity: important File: systemd-journal
Dear Maintainer, When I run 'systemd-journalctl', I get: Failed to iterate through journal: Bad message Sep 27 12:56:05 ding systemd-journal[350]: Journal started I take it this means that the log is corrupted in some way. If systemd pretends to do robust logging, it should recover from this condition in some fashion. As is, it seems stuck in this state. Andreas -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsystemd-journal0:amd64 depends on: ii libc6 2.13-35 ii libcap2 1:2.22-1.2 ii liblzma5 5.1.1alpha+20120614-1 ii libselinux1 2.1.9-5 ii libsystemd-id128-0 44-4 ii multiarch-support 2.13-35 libsystemd-journal0:amd64 recommends no packages. libsystemd-journal0:amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
