Yeah it doesn’t actually need that file. (it’s complicated)
But in case it doesn’t find a file it uses the NaN file so that it’s drawn nonetheless.
That file is only generated when dump1090 is running.
Anyway do a reinstall, i’ve made a small change.
Should make sure the NaN file is always available, but don’t want to just duplicate writing to it.
Oh well maybe i’ll do just that.
reinstalled
system graphs stopped showing data for today
still have error looking for signal_978
mv: cannot stat ‘/run/graphs1090/dump1090-localhost-signal_978-24h.png.tmp’: No such file or directory
other files in /run/graphs1090 with 978
If anything i need to take another look at the output of this:
sudo /usr/share/graphs1090/graphs1090.sh
Edit: Nevermind i looked at what i changed and it was the 1090 counterpart.
978 now changed, try another reinstall.
That’s only the disk graph, and it won’t come back until you change the collectd version.
GitHub - wiedehopf/graphs1090: Graphs for readsb / dump1090-fa / dump1090 (based on dump1090-tools by mutability)
installed new collectd
pi@piawaredump978:~ $ sudo systemctl stop collectd
pi@piawaredump978:~ $ sudo rm /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-978
pi@piawaredump978:~ $ sudo systemctl restart collectd
systems graphs still same.
The data won’t reappear.
New data have to be collected first.
No idea why other UAT graphs would now stop working.
Let it settle 20 minutes and check again.
No idea what’s mucked up now with your installation.
Let’s see this:
cd /var/lib/collectd/rrd/localhost/dump1090-localhost
ls -l *978*
Would you mind deleting all the graph data?
I suspect they somehow are corrupted.
sudo systemctl stop collectd
sudo rm -r /var/lib/collectd/rrd/localhost/
sudo systemctl restart collectd
pi@piawaredump978:~ $ cd /var/lib/collectd/rrd/localhost/dump1090-localhost
pi@piawaredump978:/var/lib/collectd/rrd/localhost/dump1090-localhost $ ls -l 978
-rw-r–r-- 1 root root 515256 Sep 12 2019 dump1090_aircraft-recent_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:15 dump1090_dbfs-median_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:15 dump1090_dbfs-min_signal_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:15 dump1090_dbfs-peak_signal_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:15 dump1090_dbfs-quart1_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:15 dump1090_dbfs-quart3_978.rrd
-rw-r–r-- 1 root root 258272 Sep 12 2019 dump1090_gps-recent_978.rrd
-rw-r–r-- 1 root root 387228 Sep 12 2019 dump1090_messages-messages_978.rrd
-rw-r–r-- 1 root root 387228 Sep 12 2019 dump1090_range-max_range_978.rrd
-rw-r–r-- 1 root root 129316 Aug 12 14:15 dump1090_range-median_978.rrd
-rw-r–r-- 1 root root 129316 Aug 12 14:15 dump1090_range-minimum_978.rrd
-rw-r–r-- 1 root root 129316 Aug 12 14:15 dump1090_range-quart1_978.rrd
-rw-r–r-- 1 root root 129316 Aug 12 14:15 dump1090_range-quart3_978.rrd
-rw-r–r-- 1 root root 258272 Sep 12 2019 dump1090_tisb-recent_978.rrd
pi@piawaredump978:/var/lib/collectd/rrd/localhost/dump1090-localhost $
no UATs visible now. will see if it changes
Your Pi had at some point a system time set to 1 month in the future.
That’s a problem.
Just remove those files which are listed with a date of Sep 12.
Or probably just remove the whole dump1090 data (dump978 data are in the same directory):
sudo systemctl stop collectd
sudo rm -r /var/lib/collectd/rrd/localhost/dump1090-localhost
sudo systemctl restart collectd
Think they’re gone now. Took several tries to fix the system time
pi@piawaredump978:/var/lib/collectd/rrd/localhost/dump1090-localhost $ ls -l
total 2276
-rw-r–r-- 1 root root 772588 Aug 12 14:34 dump1090_aircraft-recent_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:34 dump1090_gps-recent_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:34 dump1090_messages-messages_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:34 dump1090_range-max_range_978.rrd
-rw-r–r-- 1 root root 387228 Aug 12 14:34 dump1090_tisb-recent_978.rrd
pi@piawaredump978:/var/lib/collectd/rrd/localhost/dump1090-localhost $
Thanks
How did it get to the future anyway? 
Really, just nuke the database files as i said.
Just changing the time code of the files isn’t gonna help.
The message rate graph should be empty after doing that.
Let’s hope the graphs behave now then 
Should all be empty right now, or when they are updated.
Thanks for the new UAT Signal Level graph. Will be ready whenever the UATs come back.
UAT started flight at 530am towards destination out of area. Can see the range increasing and DBFS dropping to -30
