Open ambv opened 2 years ago
image setup is supposed to limit log sizes, so something is not working correctly since we moved to bullseye. if you spot the config problem please let us know.
I discovered that logrotate isn't running, it's failing to start with:
Jun 16 09:53:21 norns systemd[1]: Starting Rotate log files...
Jun 16 09:53:21 norns logrotate[866]: error: /etc/logrotate.conf:18 duplicate log entry for /var/log/wtmp
Jun 16 09:53:21 norns logrotate[866]: error: /etc/logrotate.conf:25 duplicate log entry for /var/log/btmp
Jun 16 09:53:21 norns systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Jun 16 09:53:21 norns systemd[1]: logrotate.service: Failed with result 'exit-code'.
Jun 16 09:53:21 norns systemd[1]: Failed to start Rotate log files.
This is on a clean install of the newest image (+update on device).
The problem is that logrotate.conf
includes sections for wtmp
and btmp
but there are also separate files for those logs in logrotate.d
so they end up being duplicated.
There should be no reason for logrotate because there should be no log files, all logs should be taken care of by systemd/the journal. If there's a log file somewhere that should probably be fixed to make sure the logs end up in the journal.
The log this issue is about is a file under the path /var/log/daemon.log
. Don't you see one on your installations?
In my case there are also auth.log
, debug
, dpkg.log
, kern.log
, messages
, syslog
, user.log
, and wtmp
. All of which see use.
Maybe something went wrong or was changed in the config with the switch/upgrade to Debian Buster?
Likely. This is somewhat high priority because it turns out daemon.log
fills up also with regular operation, like when receiving OSC messages. I filed a separate issue for that.
On OG aluminium Norns with 4GB of storage, the new image takes up quite a bit of space. There's less than a 1GB left for user data after a clean install so it would be nice if we could somehow make logging more efficient.
I'm looking at
daemon.log
and find it pretty big after ~12 hours of runtime. It's 66MB with a number of repeated lines (sorted here):As you can see, there's 250 thousand xruns reported. This log survives a restart.