[systemd-devel] systemd-journald[257]: Allocation limit reached, rotating

[Mirco Tischler]

2012/10/17 Reindl Harald <h.reindl at thelounge.net>:
> how large is the limit here?
>
> a machine running F17 since this night has a dedicated
> /var/log/ with 1 GB and after send out a small newsletter
> this happens 4 times in "dmesg"
>
> for me it seems the limits are too tight in the case of
> small but dedicated /var/log disks
>
> the machine itself is running rsyslog for persistent storage
>
> systemd-journald[257]: Allocation limit reached, rotating.
> systemd-journald[257]: Rotating...
> systemd-journald[257]: Vacuuming...
> systemd-journald[257]: Retrying write.
> systemd-journald[257]: Allocation limit reached, rotating.
> systemd-journald[257]: Rotating...
> systemd-journald[257]: Vacuuming...
> systemd-journald[257]: Retrying write.
> systemd-journald[257]: Allocation limit reached, rotating.
> systemd-journald[257]: Rotating...
> systemd-journald[257]: Vacuuming...
> systemd-journald[257]: Retrying write.
> systemd-journald[257]: Allocation limit reached, rotating.
> systemd-journald[257]: Rotating...
> systemd-journald[257]: Vacuuming...
> systemd-journald[257]: Retrying write.
>
You can configure the limits in journald.conf. The default file size
is 1,25% (1/8 of 10%) of the filesystem

Mirco