Hi
I’m running a supported Debian Supervised install, which has been running great for ages and disk usuage has sat consistently around 30% or so. However I checked HA yesterday and there was a low disk notification. Looking on the file systems I can see my /var/log directory is now > 132GB
Things like user.log have very verbose details about bluetooth connections and websockets etc, which I’m not sure if that is normal. (Not necessarily errors just lots of verbose logs). I will say I’ve not changed any logging levels recently and I’ve certainly not used the new integration logging to check anything recently either.
Here is a view of my log directory:
holly@HomeAssistant:/var/log$ ls -l
total 137540776
-rw-r--r-- 1 root root 0 May 1 2022 alternatives.log
-rw-r--r-- 1 root root 14696 Apr 28 2022 alternatives.log.1
drwxr-xr-x 2 root root 4096 Apr 3 2021 apparmor
drwxr-xr-x 2 root root 4096 Nov 2 00:00 apt
-rw-r----- 1 root adm 28866 Dec 15 10:43 auth.log
-rw-r----- 1 root adm 49396 Dec 10 23:17 auth.log.1
-rw-r----- 1 root adm 2452 Dec 3 23:17 auth.log.2.gz
-rw-r----- 1 root adm 2318 Nov 26 23:17 auth.log.3.gz
-rw-r----- 1 root adm 3043 Nov 19 23:17 auth.log.4.gz
-rw-rw---- 1 root utmp 384 Dec 4 19:25 btmp
-rw-rw---- 1 root utmp 384 Nov 17 16:20 btmp.1
-rw-r----- 1 root adm 262858 Dec 15 10:39 daemon.log
-rw-r----- 1 root adm 613116 Dec 11 00:00 daemon.log.1
-rw-r----- 1 root adm 18250 Dec 4 00:00 daemon.log.2.gz
-rw-r----- 1 root adm 14170 Nov 27 00:00 daemon.log.3.gz
-rw-r----- 1 root adm 30363 Nov 20 00:00 daemon.log.4.gz
-rw-r----- 1 root adm 0 Dec 6 00:00 debug
-rw-r----- 1 root adm 6753 Dec 5 19:57 debug.1
-rw-r----- 1 root adm 1336 Nov 1 19:40 debug.2.gz
-rw-r----- 1 root adm 1334 Aug 2 00:33 debug.3.gz
-rw-r----- 1 root adm 1330 Aug 1 22:33 debug.4.gz
-rw-r--r-- 1 root root 0 Nov 2 00:00 dpkg.log
-rw-r--r-- 1 root root 9473 Nov 1 19:40 dpkg.log.1
-rw-r--r-- 1 root root 332 Jun 20 12:12 dpkg.log.2.gz
-rw-r--r-- 1 root root 680 May 3 2022 dpkg.log.3.gz
-rw-r--r-- 1 root root 21406 Apr 29 2022 dpkg.log.4.gz
-rw-r--r-- 1 root root 32032 Nov 1 19:39 faillog
drwxr-xr-x 3 root root 4096 Apr 28 2022 installer
drwxr-sr-x+ 3 root systemd-journal 4096 Apr 28 2022 journal
-rw-r----- 1 root adm 19757 Dec 14 14:11 kern.log
-rw-r----- 1 root adm 129861 Dec 10 16:10 kern.log.1
-rw-r----- 1 root adm 604 Dec 1 15:16 kern.log.2.gz
-rw-r----- 1 root adm 434 Nov 24 23:44 kern.log.3.gz
-rw-r----- 1 root adm 2238 Nov 17 23:44 kern.log.4.gz
-rw-rw-r-- 1 root utmp 292292 Dec 15 10:34 lastlog
-rw-r----- 1 root adm 77575009 Dec 15 10:45 messages
-rw-r----- 1 root adm 1091701234 Dec 11 00:00 messages.1
-rw-r----- 1 root adm 3626919 Dec 4 00:00 messages.2.gz
-rw-r----- 1 root adm 3220449 Nov 27 00:00 messages.3.gz
-rw-r----- 1 root adm 3691610 Nov 20 00:00 messages.4.gz
drwx------ 2 root root 4096 Apr 28 2022 private
drwxr-xr-x 3 root root 4096 Apr 28 2022 runit
-rw-r----- 1 root adm 39752531441 Dec 15 10:45 syslog
-rw-r----- 1 root adm 30064531531 Dec 11 00:00 syslog.1
-rw-r----- 1 root adm 4848242 Dec 4 00:00 syslog.2.gz
-rw-r----- 1 root adm 4053035 Nov 27 00:00 syslog.3.gz
-rw-r----- 1 root adm 4827700 Nov 20 00:00 syslog.4.gz
-rw-r----- 1 root adm 39752235835 Dec 15 10:45 user.log
-rw-r----- 1 root adm 30063767333 Dec 11 00:00 user.log.1
-rw-r----- 1 root adm 4760952 Dec 4 00:00 user.log.2.gz
-rw-r----- 1 root adm 3975558 Nov 27 00:00 user.log.3.gz
-rw-r----- 1 root adm 4708265 Nov 20 00:00 user.log.4.gz
-rw-rw-r-- 1 root utmp 43008 Dec 15 10:34 wtmp
I’ve cleaned up the compressed logs now with:
find /var/log -type f -name "*.gz" -delete
So I can see the heavy hitters are these files now:
Any ideas what I should do to prevent this filling up like this?
Many thanks
Andy