Hello,
Today I’ve noticed that the used space in the SD Card is slowly increasing. Does your system show a similar behavior?
Currently running PiAware (SD Card) 5.0.
I can’t say it does.
You could do a cleanup on your system with the following commands 
Sudo apt-autoremove ( this will remove no longer used packages)
Sudo apt-get clean ( this will remove the downloaded packages from the local storage). If they are needed in the future they are automaticly downloaded again.
1 Like
There is something really wrong on the device. That fast increase is not normal. Having the feeder only should not take more than 2-3 GB stable.
try running the command
sudo du
from the root folder, this might give you an idea which folder contain the files taking that much.
More options on that command:
Linux commands: du and the options you should be using | Enable Sysadmin (redhat.com)
1 Like
After cleaning log files in /var/log it’s better, have to check this more often.
Thank you all for the information.
1 Like
Yeah but it’s still not normal having such an increase after few months.
That’s mine after 2 1/2 months, using a 64 GB SD card
And beside the feeder i also have WeeWX (weather station software) with Apache and MySQL running together with an InfluxDB/Grafana instance on the same device
1 Like
I’d thought logrotate should keep your files to a reasonable size. Just deleting logs has not fixed the issue which will recur; what is making the logs grow so fast. Some info/warning/error that is repeating frequently ?
Before deleting the files it would have been good looking on their list…
But now it’s too late
I’m monitoring the logs size and next time I will save then before delete.
After 9 days I haven’t seen any major increase in used space.
In the daemon.log I can see a lot of " Can’t connect to 978 source (127.0.0.1:28380). Waiting 5 second…", is there any way to stop this process?
total 234M
-rw-r--r-- 1 root root 0M Sep 14 2020 alternatives.log
-rw-r--r-- 1 root root 1M Sep 7 2020 alternatives.log.1
drwxr-xr-x 2 root root 1M Mar 31 00:00 apt
-rw-r----- 1 root adm 3M May 31 09:35 auth.log
-rw------- 1 root root 4M May 31 00:01 boot.log
-rw-r--r-- 1 root root 0M Mar 24 2020 bootstrap.log
-rw-rw---- 1 root utmp 0M May 31 00:00 btmp
-rw-rw---- 1 root utmp 0M May 28 00:00 btmp.1
-rw-r--r-- 1 root adm 81M May 31 09:35 daemon.log
-rw-r--r-- 1 root adm 1M May 31 00:02 debug
-rw-r--r-- 1 root adm 1M Nov 28 2020 debug.1
drwxrwxrwx 2 root root 1M Apr 17 2020 dirmngr
-rw-r--r-- 1 root root 0M Mar 31 00:00 dpkg.log
-rw-r--r-- 1 root root 1M Mar 26 08:11 dpkg.log.1
-rw-r--r-- 1 root root 1M Sep 16 2020 dpkg.log.1.gz-2020092100.backup
-rw-r--r-- 1 root root 1M Oct 16 2020 dpkg.log.1.gz-2020101800.backup
-rw-r--r-- 1 root root 1M Nov 2 2020 dpkg.log.1.gz-2020110600.backup
-rw-r--r-- 1 root root 1M Sep 15 2020 faillog
-rw-r--r-- 1 root root 0M Mar 24 2020 fontconfig.log
drwxr-xr-x 2 fr24 fr24 1M May 21 12:38 fr24feed
-rw-r--r-- 1 root root 0M Apr 17 2020 fr24feed_install_dump1090.log
-rw-r--r-- 1 root root 1M May 31 08:11 fr24feed_update.log
-rw-r--r-- 1 root adm 7M May 31 00:01 kern.log
-rw-r--r-- 1 root adm 1M Nov 28 2020 kern.log.1
-rw-rw-r-- 1 root utmp 1M May 31 09:20 lastlog
drwxr-x--- 2 www-data www-data 1M May 31 00:00 lighttpd
-rw-r--r-- 1 root adm 6M May 31 00:01 messages
-rw-r--r-- 1 root adm 1M Nov 29 2020 messages.1
-rw-r--r-- 1 root root 9M May 31 09:30 mlat-client.log
-rw-r--r-- 1 root root 3M May 24 00:00 mlat-client.log.1
-rw-r--r-- 1 root root 1M May 19 00:00 mlat-client.log.2
-rw-r--r-- 1 root root 4M May 17 00:00 mlat-client.log.3
-rw-r--r-- 1 root root 1M May 15 00:00 mlat-client.log.4
-rw-r--r-- 1 root root 4M May 10 00:00 mlat-client.log.5
-rw-r--r-- 1 root root 0M Oct 25 2020 nodered-install.log
-rw-r--r-- 1 root root 1M Sep 7 2020 nodered-install.log.1
drwxr-xr-x 2 ntp ntp 1M Mar 21 2019 ntpstats
drwxr-xr-x 2 root root 1M May 30 21:02 pfclient
-rw-r--r-- 1 root adm 2M May 31 09:33 piaware.log
drwx------ 2 root root 1M Mar 24 2020 private
-rw-r--r-- 1 root root 22M May 31 09:35 rbfeeder.log
-rw-r--r-- 1 root adm 83M May 31 09:35 syslog
-rw-r--r-- 1 root adm 9M Dec 1 00:00 syslog.1
-rw-r--r-- 1 root adm 0M Oct 29 2020 syslog.1.gz-2020112200.backup
-rw-r--r-- 1 root adm 1M May 31 00:00 user.log
-rw-r--r-- 1 root adm 1M Nov 28 2020 user.log.1
-rw-r--r-- 1 root root 1M May 31 00:01 vrsw-adsb.log
-rw-r--r-- 1 root root 1M May 31 09:30 vrsw-mlat.log
-rw-rw-r-- 1 root utmp 1M May 31 09:20 wtmp
if you are not using UAT 978 ( USA only) then you can use the following commands to disable the 978 reciever.
If you ever want to add a 978 reciever you can use the 2nd part of the commands below.
9.2 - If you want to run 1090 Mhz only
In this case, you will need only one dongle, but you will have to disable dump978-fa by following command
sudo piaware-config receiver-type rtlsdr
sudo piaware-config uat-receiver-type none
sudo systemctl restart piaware
To re-enable dump978-fa (requires an additional dongle for dump978-fa)
sudo piaware-config uat-receiver-type sdr
sudo systemctl restart piaware
1 Like
You should have log messages in journalctl in memory.
Really there is no need for /var/log very much …
I’d just
sudo apt remove rsyslog
And get rid of redundant logging.
1 Like
I will show your statement to the Radarbox team
On my end this is the one causing most traffic in my var/log without giving much value. Therefore i’ve moved this particular log to Ramdisk and write it once a night to disk.
Checking my CPU use wioth and without Radadrbox24.com active. It takes a lot of CPU when I open the site on my Macbook.
Radarbox24.com open
Without Radarbox
It seems Radarbox is taking a lot of CPU%
Does everyone have the same experience? Noticed it before, but after reading this thread I decided to check it again.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.