Search results

I used the following approach: In `/etc/systemd/journald.conf`, set: SystemMaxUse=128M RuntimeMaxUse=128M followed by: journalctl --vacuum-size=256M; systemctl force-reload systemd-journald

Yep, can confirm this issue with Ubuntu 16.04 CTs that would generate a lot of logs. Environment slightly differing - Proxmox 4.4. This was a real head scratcher until I came across this thread. Capping the journal size inside the CT has successfully worked around the issue. Does this need a...