FlightAware Discussions

Graphs for dump1090 -- my version with install script

Thanks. Yes I appreciate I can change the timezone to Europe/London. Anyone else know if that’s sensible on the PiAware image? While it will make the graphs show local time, I’m wary of breaking how data is fed to FA, scewing MLAT, etc. I think it’s always fed as UTC data anyway, but then perhaps the timezone setting is specifically set to None for a reason and should not be changed.

It won’t affect piaware etc.

On Ubuntu Server 20.04 arm64 / Pi 4

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"

EDIT:
Tried to uninstall, got this error message

ubuntu@ubuntu:~$ sudo bash /usr/share/graphs1090/uninstall.sh
mv: cannot stat '/etc/collectd/collectd.conf.graphs1090': No such file or directory
rm: cannot remove '/etc/cron.d/cron-graphs1090': No such file or directory

Uninstall did what it’s supposed to do …

Also you know i can’t fix anything without the proper logs: https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#graphs1090

Oops, too late, I have reimaged the microSD card few minutes ago.

Thanks Oliver, I had wondered whether there was no overt timezone setting in the image because PiAware has no need of it in its presentation layer, but as soon as we add third-party graphs then we have created that need and the timezone becomes relevant. And therefore it could make sense for PiAware image devs to come to rely on the timezone remaining as None/UTC, and then the user comes along and changes it and breaks this reliance. I changed it earlier today to see what happens anyway, and it’s all good so far with graphs also showing local time now.

Internally unix always references everything to the epoch and runs on UTC time.
Only the stuff shown to the user is then translated by the timezone.

Most software just uses UTC time as well and only translates by timezone when showing to the user.

Windows actually setting the RTC of the computer to the local timezone could be quite annoying when running with Linux dual boot.
Not sure if that’s still an issue.

No problem, i don’t particularly care about fixing graphs1090 for that platform.
Just saying, if you’re gonna post about the failure to run it at all, why not provide the relevant logs.
I think we’ve had this discussion before :wink:
Maybe next time with the relevant logs when you encounter an issue for one of my scripts on one of the platforms / operating systems you try :slight_smile:

Ideally, but not something a user should rely on when making a change, especially for a bootable image which otherwise has no reason to care about the local timezone and which can use location to identify local time while the system remains set to UTC. The only reason I’ve needed to change it is to have graphs1090 render the axis with local time.

On a related note, can I expect any strange behaviour from graphs1090 as a result of setting a timezone which introduces non-UTC? For example does daylight savings switchover cause a problem, or do the graphs simply display the current local time, so sometimes it will miss an hour on the axis and other times it will have the same hour repeated on the axis? If so does that cause any problems with the compression logic when changing data for the longer term graphs? And so on.

Daylight saving is not an issue for rrd-graph nor for collectd.
collectd does it in UTC and rrd-graph then makes images with DST and handles that correctly.

Nice one, well I’ve added the extra step of setting the timezone with raspi-config to my build documentation and if any problems do pop up, in graphs or feeding, I’ll report them here.

Well, when I first posted, I was not aware exactly what logs you want, and I was waiting for you to respond.

By the time you responded and told me the debug commands wiki, I have already written fresh image.

I have now installed graphs on the fresh image, and ran the debug commands.

ubuntu@ubuntu:~$ sudo journalctl --no-pager -u collectd  

-- Logs begin at Wed 2020-04-01 17:23:43 UTC, end at Sun 2020-05-24 02:31:46 UTC. --
May 24 02:29:01 ubuntu systemd[1]: Condition check resulted in Statistics collection and monitoring daemon being skipped.
May 24 02:30:32 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "table" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "interface" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "df" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: plugin "disk" successfully loaded.
May 24 02:30:32 ubuntu collectd[3428]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:32 ubuntu collectd[3428]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:32 ubuntu collectd[3428]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:30:32 ubuntu collectd[3428]: Error: Parsing the config file failed!
May 24 02:30:32 ubuntu collectd[3428]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:30:32 ubuntu collectd[3428]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:30:32 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:30:32 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:30:32 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:30:42 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 1.
May 24 02:30:42 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:30:42 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "table" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "interface" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "df" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: plugin "disk" successfully loaded.
May 24 02:30:42 ubuntu collectd[3735]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:42 ubuntu collectd[3735]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:42 ubuntu collectd[3735]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:30:42 ubuntu collectd[3735]: Error: Parsing the config file failed!
May 24 02:30:42 ubuntu collectd[3735]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:30:42 ubuntu collectd[3735]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:30:42 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:30:42 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:30:42 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:30:52 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 2.
May 24 02:30:52 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:30:52 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "table" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "interface" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "df" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: plugin "disk" successfully loaded.
May 24 02:30:52 ubuntu collectd[4016]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:52 ubuntu collectd[4016]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:30:52 ubuntu collectd[4016]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:30:52 ubuntu collectd[4016]: Error: Parsing the config file failed!
May 24 02:30:52 ubuntu collectd[4016]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:30:52 ubuntu collectd[4016]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:30:52 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:30:52 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:30:52 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:31:03 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 3.
May 24 02:31:03 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:31:03 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:31:03 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:31:03 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:31:03 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:31:13 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 4.
May 24 02:31:13 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:31:13 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "table" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "interface" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "df" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: plugin "disk" successfully loaded.
May 24 02:31:13 ubuntu collectd[4728]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:13 ubuntu collectd[4728]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:13 ubuntu collectd[4728]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:31:13 ubuntu collectd[4728]: Error: Parsing the config file failed!
May 24 02:31:13 ubuntu collectd[4728]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:31:13 ubuntu collectd[4728]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:31:13 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:31:13 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:31:13 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:31:23 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 5.
May 24 02:31:23 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:31:23 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "table" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "interface" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "df" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: plugin "disk" successfully loaded.
May 24 02:31:23 ubuntu collectd[4982]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:23 ubuntu collectd[4982]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:23 ubuntu collectd[4982]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:31:23 ubuntu collectd[4982]: Error: Parsing the config file failed!
May 24 02:31:23 ubuntu collectd[4982]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:31:23 ubuntu collectd[4982]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:31:23 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:31:23 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:31:23 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:31:33 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 6.
May 24 02:31:33 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:31:33 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "syslog" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "rrdtool" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "table" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "interface" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "cpu" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "aggregation" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "match_regex" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "df" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: plugin "disk" successfully loaded.
May 24 02:31:33 ubuntu collectd[5264]: ERROR: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:33 ubuntu collectd[5264]: dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: undefined symbol: PyFloat_Type. The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
May 24 02:31:33 ubuntu collectd[5264]: plugin_load: Load plugin "python" failed with status 2.
May 24 02:31:33 ubuntu collectd[5264]: Error: Parsing the config file failed!
May 24 02:31:33 ubuntu collectd[5264]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a configuration callback.
May 24 02:31:33 ubuntu collectd[5264]: Plugin python failed to handle option ModulePath, return code: -1
May 24 02:31:33 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:31:33 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:31:33 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.
May 24 02:31:44 ubuntu systemd[1]: collectd.service: Scheduled restart job, restart counter is at 7.
May 24 02:31:44 ubuntu systemd[1]: Stopped Statistics collection and monitoring daemon.
May 24 02:31:44 ubuntu systemd[1]: Starting Statistics collection and monitoring daemon...
May 24 02:31:44 ubuntu systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
May 24 02:31:44 ubuntu systemd[1]: collectd.service: Failed with result 'exit-code'.
May 24 02:31:44 ubuntu systemd[1]: Failed to start Statistics collection and monitoring daemon.

 

ubuntu@ubuntu:~$ sudo /usr/share/graphs1090/graphs1090.sh  

6014 (process ID) old priority 0, new priority 19
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_aircraft-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_aircraft-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_aircraft-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_mlat-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_tisb-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_gps-recent.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-aircraft-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_aircraft-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-aircraft_message_rate-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_cpu-demod.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_cpu-reader.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_cpu-background.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-cpu-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_tracks-all.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_tracks-single_message.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-tracks-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_gps-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_mlat-recent.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-positions.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-local_rate-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-strong_signals.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_messages-positions.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-local_trailing_rate-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-max_range.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-max_range.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-minimum.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-quart1.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-quart3.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-median.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-range-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-signal.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-min_signal.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-quart1.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-quart3.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-median.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-peak_signal.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/dump1090-localhost-signal-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-idle.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-interrupt.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-nice.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-softirq.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-steal.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-system.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-user.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/aggregation-cpu-average/cpu-wait.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-cpu-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/df-root/df_complex-used.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/df-root/df_complex-reserved.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/df-root/df_complex-free.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-df_root-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost//disk_ops.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost//disk_ops.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-disk_io_iops-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost//disk_octets.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost//disk_octets.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-disk_io_octets-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/system_stats/memory-used.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/system_stats/memory-buffers.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/system_stats/memory-cached.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/system_stats/memory-free.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-memory-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost//if_octets.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost//if_octets.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-network_bandwidth-24h.png.tmp': No such file or directory
File /var/lib/collectd/rrd/localhost/table-localhost/gauge-cpu_temp.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/table-localhost/gauge-cpu_temp.rrd not found! Associated graph will be empty!
File /var/lib/collectd/rrd/localhost/table-localhost/gauge-cpu_temp.rrd not found! Associated graph will be empty!
ERROR: opening '/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-NaN.rrd': No such file or directory
mv: cannot stat '/run/graphs1090/system-localhost-temperature-24h.png.tmp': No such file or directory

Seems Ubuntu is distributing a broken version of collectd.
Too bad for them.

Maybe try this:

sudo apt install libpython3.8 libpython3.7

Probably won’t help though, debian was distributing a broken collectd version for a bit as well.

ubuntu@ubuntu:~$ sudo apt install libpython3.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libpython3.7
ubuntu@ubuntu:~$ sudo apt install libpython3.8
Reading package lists... Done
Building dependency tree
Reading state information... Done
libpython3.8 is already the newest version (3.8.2-1ubuntu1.1).
libpython3.8 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.

Oh well so this doesn’t do anything.

Pretty sure you’ll just have to wait until Ubuntu fixes collectd on that release.
You could probalby do some shenanigans, but if you won’t even run that system it doesn’t really matter.
(I’d do sth about it but it’s not a problem with my scripts but the underlying software)

I installed graphs1090 with this script. It works but my Pi (Piaware Image) reboots every few minutes. I change nothing else. Only installed graphs1090. So what to do now?

Hi guys,
did somebody already faced with such a problem:


But not all the graphs look similar e.g.:

Yesterday, I have seen also the same, I checked my Rpi and it was already running 32 days, so I decided to do a restart, then it happened again as you can see. Before I did the restart I have checked tar1090, but it was running normally, so it seems only graphs1090 somehow hangs.
But today I did nothing it was just started to show the graphs again.
Has anybody some idea what should I check if it happens again?
(Note: I did not perform any change in the Rpi settings, no updated was installed, nothing)

https://github.com/wiedehopf/graphs1090#deinstallation

Probably bad sd-card or insufficient power supply.

The increased amount of write could mean it’s a bad sd-card.
Also:
https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#graphs1090

Ok. Thank you. I will try in a few days with a new SD-Card and tell you if it is the case. Power Supply should be ok with 10W, 2.1A.

The increased amount of write could mean it’s a bad sd-card.

Thanks for your reply.
I do not think it is an SD card issue, because the system was just started 10 weeks ago, the high Disk IO starts at midnight because every day at 0:00 I generate the daily Heatmaps, okay, it just takes a couple of minutes, so I do not know why it is not dropping after, and when the problem was started around 13 o’clock there was just a couple of write peaks.


Also, the memory utilization is quite interesting, the cache is just disappeared and came back.
In case of CPU utilization, the IO part was disappeared.
Anyway, I will check also the SD card I have also no better idea.
Next time, I will use the debug commands to gather more information.