Bug#967945: systemd is way too aggressive in deleting journals of yesterday
Michael Biebl
biebl at debian.org
Thu Feb 10 09:11:22 GMT 2022
Control: tags -1 + moreinfo
Am 10.08.20 um 10:26 schrieb Harald Dunkel:
> On 8/10/20 10:19 AM, Harald Dunkel wrote:
>> On 8/8/20 11:54 AM, Michael Biebl wrote:
>>> What's the output of
>>> journalctl -b -u systemd-journald.service
>>>
>>
>> srvvm01:~# journalctl -b -u systemd-journald.service
>> -- Logs begin at Mon 2020-08-10 00:04:18 CEST, end at Mon 2020-08-10
>> 10:19:18 CEST. --
>> -- No entries --
>>
>
> PS: This is a LXC container. Host and container are running
> Debian 10 and esp. systemd 241-7~deb10u4. Its the same host
> as for #968049.
Is this still reproducible?
If so, can you run
- systemctl edit systemd-journald.service
- then add
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
- journalctl -f
- systemctl restart systemd-journald.service
and then attach the output of journalctl.
After that, you can remove
/etc/systemd/system/systemd-journald.service.d/override.conf again
Regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220210/99ec60fa/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list