Hi,
I’ve got emonSD-03May16 running on a Pi, which was rebooted 6 days ago. Today I found that that /var/log Filesystem is full, and looks like it filled up around 08:26:16 yesterday (Monday 23rd), and it looks like logrotate hasn’t been working.
The logrotate log file shows zero length, but with a recent timestamp:
-rw-r--r-- 1 root root 0 May 24 21:17 /var/log/logrotate/logrotate.log
The status file shows timestamp from when logging filled up:
-rw-r--r-- 1 root root 29 May 23 08:17 /var/log/logrotate/logrotate.status
pi@emonbase:/etc $ cat /var/log/logrotate/logrotate.statu
s
logrotate state -- version 2
When I look in /var/log, there are no .gz files - but the logrotate.conf shows it should compress in place?
ls -l /var/log
total 42352
drwxr-xr-x 2 root adm 60 May 17 21:02 apache2
-rw-r----- 1 root adm 25419776 May 24 21:46 auth.log
-rw------- 1 root utmp 0 May 17 21:01 btmp
-rw-r----- 1 root adm 229376 May 24 21:46 daemon.log
-rw-r----- 1 root adm 989 May 17 21:02 debug
-rw-rw-rw- 1 root root 405 May 17 22:03 emoncms.log
drwxr-xr-x 2 emonhub root 80 May 23 04:02 emonhub
drwxr-xr-x 2 pi root 60 May 17 21:01 emonpilcd
-rw-r----- 1 root adm 49152 May 24 21:17 kern.log
drwxr-xr-x 2 pi pi 80 May 24 21:17 logrotate
-rw-r----- 1 root adm 49152 May 24 21:17 messages
-rw-rw-rw- 1 root root 0 May 17 21:02 mqtt_input.log
drwxr-xr-x 2 mysql adm 60 May 17 21:02 mysql
-rw-rw-rw- 1 root root 0 May 17 21:02 mysql.log
drwxr-xr-x 2 openhab openhab 240 May 23 23:59 openhab
drwxr-xr-x 2 redis redis 60 May 17 21:02 redis
-rw-rw-rw- 1 root root 1740800 May 24 21:45 service-runner.log
-rw-r----- 1 root adm 15863808 May 24 21:46 syslog
-rw-rw-r-- 1 root utmp 6528 May 24 20:47 wtmp
/etc/logrotate.conf is a link to /var/www/emoncms/scripts/logger/logrotate.conf which I haven’t changed:
-rw-r--r-- 1 pi pi 768 Apr 29 10:46 /var/www/emoncms/scripts/logger/logrotate.conf
The logrotate.conf has a comment
# default is daily run, move cron script to make this happen hourly:
# sudo mv /etc/cron.daily/logrotate /etc/cron.hourly/logrotate
so I looked in /etc/cron.daily/logrotate and it’s a zero length file:
-rw-r--r-- 1 root root 0 Apr 28 22:17 /etc/cron.daily/logrotate
And logrotate also exists in cron.hourly and it’s a link:
lrwxrwxrwx 1 root root 41 Jan 26 15:35 /etc/cron.hourly/logrotate -> /var/www/emoncms/scripts/logger/logrotate
-rwxrwxr-x 1 pi pi 175 Feb 20 15:57 /var/www/emoncms/scripts/logger/logrotate
cat /var/www/emoncms/scripts/logger/logrotate
#!/bin/sh
test -x /usr/sbin/logrotate || exit 0
/usr/sbin/logrotate -v -s /var/log/logrotate/logrotate.status /etc/logrotate.conf 2>&1 | tee /var/log/logrotate/logrotate.log
Any ideas ? should I try to delete the empty logrotate file from /etc/cron.daily/ ?
Also, I don’t know if this is related or not, but root crontab seems to contain lots of identical entries:
sudo crontab -l
<comments snipped>
# m h dom mon dow command
*/5 * * * * /usr/local/bin/wifi-check > /home/pi/data/wificheck.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
- /home/pi/emonpi/service-runner >> /var/log/service-runner.log 2>&1
I don’t understand why service-runner needs so many entries?
Any help is appreciated.
Ian