I just started getting this kind of error:-
/etc/cron.daily/openmediavault-cron-apt: cat: write error: No space left on device
Investigating with df -h, I find that /var/log/ is 100% used (460M). Looking in /var/log, I find 100 files mainly .gz, and 20 are over a year old, although small. Two files, syslog and daemon.log are 40M each and current. One sub directory, /var/log/journal, is 370M and contains 800 files, all less than 1 week old, with names like this "system@cf9a9b1b3ba64f8784ed8d0871e91499-0000000000000001-0006128712e34746.journal". Their contents are not human-readable. 48 of these are 5M or 8M in size.
I guess I can go through deleting files which are deemed to be non-essential, and increasing the size of /var/log/, but I would prefer to find why this is happening and whether there is some kind of configuration I should change to improve log rotation and clean up. I am conscious that OMV likes to maintain its own configs, so I don't want to just change things blindly.
Should I be looking for a problem with systemd that is creating these journal files, or is there some other way of changing log managaement within OMV?
Mystified Marmite.