I attempted to reproduce this bug in a Noble container using the
following script:
```bash
sudo tee /etc/systemd/journald.conf <<EOF
[Journal]
RateLimitBurst=10000000000
MaxFileSec=1
SystemMaxFiles=16
EOF
sudo systemctl restart systemd-journald
for _ in `seq 1 16`; do
systemd-cat bash -c 'dd if=/dev/urandom bs=1M count=1 | base64 -w 256' &
sleep 1s
sudo journalctl --rotate
done
SYSTEMD_LOG_LEVEL=debug journalctl --user --verify
```
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version.
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
** Changed in: systemd (Ubuntu)
Assignee: Willow Carlson-Huber (willow-ch) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088163
Title:
Journald file corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2088163/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
