No, I do not have that file. It looks like the later python code would create it. I think it is failing the try: and setting ptime=0 with the except:
If I change ptime=1 as below the .rrd file gets created and the blue “Airspy” show up as a name on the graph.
well paste the entire command line
PID=$(systemctl show -p MainPID airspy_adsb | cut -f 2 -d=); cat /proc/$PID/task/$(ls /proc/$PID/task | awk NR==3)/stat | cut -d ' ' -f 14,15 && getconf CLK_TCK
check if it gives you the expected output.
Add
print(out)
in the first line of the try block with the same indentation as the code in the try block.
You should get some output in the journalctl log for collectd.
The entire command line gives:
collectd only seems to “print” the value of “out” on stopping the service.
Yeah i’m not sure why what wouldn’t work.
Remove the except: ptime=0 and try:
move the indent one to the left for the previous try block:
out, clk_tck = out.split('\n', 1)
out = [(int(i)*1000)/int(clk_tck) for i in out.split(' ')]
ptime = sum(out)
utime = out[0]
stime = out[1]
Now it should give you an exception in the collectd log.
Try adding the text=True, line a couple of lines above where you where changing stuff (Popen call)
shell=True,
text=True,
)
I think that’s a python3 vs python2 difference.
Those aren’t compatible but newer collectd versions use python3 so … i’ve managed for this limited usecase to make the code run with both python versions.
But i’ve never tested for the airspy case.
Edit: I’m fairly certain this is the issue and have pushed a fix to github.
1 Like
That was it. Thank you very much for the assistance. Python is new to me…
Cheers
Thanks for “Removing 978 graphs + data” they reappeared after database restore but script made it much easier to fix
At first I was like where is the graphs for the 978uat? How can I easily get those functions back?
I love how the graphs tell a story.
At around 11:20 this morning, I lowered my mast which has my receiver on top.
For a few minutes, the aerial was almost horizontal and then as I tiled the hexbeam up, the ADS-B aerial went back to being vertical but it was only about 8ft off the ground. It was like that for an hour or so when I tilted it back to almost horizontal for about fifteen minutes before raising it back up again.
Each phase is clearly visible.
Thank you @Wiedehopf for these tools you’ve given us.
6 Likes
Can I add visualization for another 1090 receiver (based on it’s IP)?
graph1090 does not offer any facilities for that.
You’d have to rewrite quite a bit of the code.
1 Like
Any idea about that little drop in the first graph? All other graphs (except ADS-B Maxima which shows the same gap) are intact, the device was running all the time.
Not important, just curious because i haven’t seen it before
Curious.
Anything in the collectd logs?
sudo journalctl -u collectd -e
Maybe but unfortunately i needed to reboot the device two hours later and the logs are stored in RAM 
Sorry, will check it once the gap comes up again.
1 Like
If you spin up a virtual machine of Debian and install Graphs1090 on it using the included install.sh script, you can modify the collectd configuration to look at a remote IP and consume the JSON information over HTTP. I just did exactly this- I leave my PiAware receiver alone and have a VM running things like FlightAirMap and now Graphs1090 on it connecting remotely to the PiAware.
Obviously the system graphs showing CPU, Memory, Hard Drive, Network, etc are all from my VM, rather than the remote PiAware.
There’s no support for this though, make the modifications at your own risk. Worst case, just restart from scratch. That said, I don’t see a way to setup Multiple 1090 receivers on the same instance of Graph1090 easily as @wiedehopf mentioned.
1 Like
Hello @wiedehopf,
Out of curiosity I ran the command you suggested to @foxhunter and found the following output.
-- Logs begin at Sun 2021-03-21 09:47:33 AEDT, end at Tue 2021-03-23 15:26:32 AEDT. --
Mar 21 09:47:38 raspi4 systemd[1]: Starting Statistics collection and monitoring daemon...
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "syslog" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "rrdtool" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "table" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "interface" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "cpu" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "aggregation" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "match_regex" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "df" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "disk" successfully loaded.
Mar 21 09:47:39 raspi4 collectd[760]: plugin_load: plugin "python" successfully loaded.
Mar 21 09:47:40 raspi4 collectd[760]: Systemd detected, trying to signal readyness.
Mar 21 09:47:40 raspi4 systemd[1]: Started Statistics collection and monitoring daemon.
Mar 21 09:47:40 raspi4 collectd[760]: Initialization complete, entering read-loop.
Mar 21 23:42:01 raspi4 collectd[760]: Exiting normally.
Mar 21 23:42:01 raspi4 collectd[760]: collectd: Stopping 5 read threads.
Mar 21 23:42:01 raspi4 systemd[1]: Stopping Statistics collection and monitoring daemon...
Mar 21 23:42:01 raspi4 collectd[760]: collectd: Stopping 1 write threads.
Mar 21 23:42:01 raspi4 collectd[760]: rrdtool plugin: Shutting down the queue thread.
Mar 21 23:42:02 raspi4 systemd[1]: collectd.service: Succeeded.
Mar 21 23:42:02 raspi4 systemd[1]: Stopped Statistics collection and monitoring daemon.
Mar 21 23:42:02 raspi4 systemd[1]: Starting Statistics collection and monitoring daemon...
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "syslog" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "rrdtool" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "table" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "interface" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "cpu" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "aggregation" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "match_regex" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "df" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "disk" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: plugin_load: plugin "python" successfully loaded.
Mar 21 23:42:03 raspi4 collectd[9287]: Systemd detected, trying to signal readyness.
Mar 21 23:42:03 raspi4 systemd[1]: Started Statistics collection and monitoring daemon.
Mar 21 23:42:03 raspi4 collectd[9287]: Initialization complete, entering read-loop.
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted_0.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted_0.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted_1.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-local_accepted_1.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-strong_signals.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-strong_signals.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted_0.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted_0.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted_1.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-remote_accepted_1.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_messages-positions.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_messages-positions.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_tracks-all.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_tracks-all.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_tracks-single_message.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_tracks-single_message.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_cpu-background.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_cpu-background.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_cpu-demod.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_cpu-demod.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 21 23:42:03 raspi4 collectd[9287]: rrdtool plugin: rrd_update_r (/run/collectd/localhost/dump1090-localhost/dump1090_cpu-reader.rrd) failed: /run/collectd/localhost/dump1090-localhost/dump1090_cpu-reader.rrd: illegal attempt to update using time 1616330498 when last update time is 1616330498 (minimum one second step)
Mar 22 23:42:01 raspi4 collectd[9287]: Exiting normally.
Mar 22 23:42:01 raspi4 collectd[9287]: collectd: Stopping 5 read threads.
Mar 22 23:42:01 raspi4 systemd[1]: Stopping Statistics collection and monitoring daemon...
Mar 22 23:42:01 raspi4 collectd[9287]: collectd: Stopping 1 write threads.
Mar 22 23:42:01 raspi4 collectd[9287]: rrdtool plugin: Shutting down the queue thread.
Mar 22 23:42:03 raspi4 systemd[1]: collectd.service: Succeeded.
Mar 22 23:42:03 raspi4 systemd[1]: Stopped Statistics collection and monitoring daemon.
Mar 22 23:42:03 raspi4 systemd[1]: Starting Statistics collection and monitoring daemon...
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "syslog" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "rrdtool" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "table" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "interface" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "cpu" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "aggregation" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "match_regex" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "df" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "disk" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: plugin_load: plugin "python" successfully loaded.
Mar 22 23:42:03 raspi4 collectd[21573]: Systemd detected, trying to signal readyness.
Mar 22 23:42:03 raspi4 systemd[1]: Started Statistics collection and monitoring daemon.
Mar 22 23:42:03 raspi4 collectd[21573]: Initialization complete, entering read-loop.
Do the “rrdtool plugin…failed” messages at 23:42:03 on March 21 signify a problem or can I safely ignore them? I had updated to the then current version of graphs1090 just before a reboot where the log begins.
graphs1090 seems to have been running normally. I’m just curious about the messages.
The only thing I’ve noticed is the excursions in the adsb Messages/Aircraft/Second trace either side of periods with zero adsb messages being received. (This may be normal and I just haven’t paid attention to it before.)
The error message is a bit hard to read but you can understand it.
Can’t update more than once a second … so no normal message for restarts.
It was normal i believe i’ve added a fix for it, try and update.
Thanks, will do - weather here might be good for a period without aircraft tonight. If so will let you know the results.