Hi - I wondered if anyone has seen this behaviour with the latest version of airspy_adsb?
airspy_adsb seemed to hang on my RasPi4 overnight. This was evident from graphs1090:
However when I ran systemctl status, it was not listed as failed:
jrg@raspi4:~ $ sudo systemctl status
[sudo] password for jrg:
● raspi4
State: running
Jobs: 0 queued
Failed: 0 units
Since: Thu 1970-01-01 10:00:02 AEST; 50 years 7 months ago
CGroup: /
├─user.slice
│ └─user-1001.slice
│ ├─session-c6.scope
│ │ ├─17845 sshd: jrg [priv]
│ │ ├─17901 sshd: jrg@pts/0
│ │ ├─17904 -bash
│ │ ├─27970 sudo systemctl status
│ │ ├─28054 systemctl status
│ │ └─28055 pager
│ └─user@1001.service
│ └─init.scope
│ ├─17881 /lib/systemd/systemd --user
│ └─17885 (sd-pam)
├─init.scope
│ └─1 /sbin/init splash
└─system.slice
├─collectd.service
│ └─523 /usr/sbin/collectd
├─timelapse1090.service
│ ├─ 473 /bin/bash /usr/local/share/timelapse1090/timelapse1090.sh
│ ├─ 481 /bin/bash /usr/local/share/timelapse1090/timelapse1090.sh
│ └─28036 sleep 10
├─graphs1090.service
│ ├─ 301 /bin/bash /usr/share/graphs1090/service-graphs1090.sh
│ ├─27975 /bin/bash /usr/share/graphs1090/graphs1090.sh 7d 0.7
│ └─28035 sleep 0.7
├─dbus.service
│ └─329 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
├─chrony.service
│ ├─822 /usr/sbin/chronyd -F -1
│ └─823 /usr/sbin/chronyd -F -1
├─ssh.service
│ └─687 /usr/sbin/sshd -D
├─airspy_adsb.service
│ └─353 /usr/local/bin/airspy_adsb -v -f 1 -t 300 -w 3 -e 9.4 -l 29999:beast -l 47806:asavr -c localhost:30004:beast -g 20 -m 20
├─tar1090.service
│ ├─ 491 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/dump1090-fa
│ ├─ 511 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/dump1090-fa
│ ├─ 875 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/dump1090-fa
│ ├─27953 sleep 8
│ └─28043 sleep 10
├─system-getty.slice
│ └─getty@tty1.service
│ └─560 /sbin/agetty -o -p -- \u --noclear tty1 linux
├─wpa_supplicant.service
│ └─334 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
├─tar1090-persist.service
│ ├─ 487 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090-persist /run/dump1090-fa
│ ├─ 490 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090-persist /run/dump1090-fa
│ ├─ 872 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090-persist /run/dump1090-fa
│ ├─27942 sleep 14
│ └─27964 sleep 10
├─lighttpd.service
│ └─637 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
├─systemd-logind.service
│ └─318 /lib/systemd/systemd-logind
├─polkit.service
│ └─11670 /usr/lib/policykit-1/polkitd --no-debug
├─cron.service
│ └─311 /usr/sbin/cron -f
├─systemd-udevd.service
│ └─148 /lib/systemd/systemd-udevd
├─rsyslog.service
│ └─338 /usr/sbin/rsyslogd -n -iNONE
├─systemd-journald.service
│ └─119 /lib/systemd/systemd-journald
├─dhcpcd.service
│ └─466 /sbin/dhcpcd -q -b
├─dump1090-fa.service
│ └─4666 /usr/bin/dump1090-fa --net-only --max-range 360 --fix --net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-ri-port 0 --net-ro-port 30002 -
├─piaware.service
│ ├─ 649 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
│ ├─1982 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,
│ └─4738 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat -38.296 --lon 144.391
└─pfclient.service
└─578 /usr/bin/pfclient -d -i /var/run/pfclient.pid -z /etc/pfclient-config.json -y /var/log/pfclient $
jrg@raspi4:~ $ sudo systemctl status airspy_adsb
● airspy_adsb.service - Airspy ADS-B receiver
Loaded: loaded (/etc/systemd/system/airspy_adsb.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 09:17:04 AEST; 4 days ago
Docs: https://discussions.flightaware.com/t/howto-airspy-mini-piaware-dump1090-fa-configuration/44343/2
Main PID: 353 (airspy_adsb)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/airspy_adsb.service
└─353 /usr/local/bin/airspy_adsb -v -f 1 -t 300 -w 3 -e 9.4 -l 29999:beast -l 47806:asavr -c localhost:30004:beast -g 20 -m 20
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 262144 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 262144 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 131072 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 131072 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 393216 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 262144 samples /!\
Aug 21 09:17:05 raspi4 airspy_adsb[353]: /!\ Lost 131072 samples /!\
Aug 21 09:17:08 raspi4 airspy_adsb[353]: Push client connected to localhost:30004 (beast)
Aug 23 04:44:02 raspi4 airspy_adsb[353]: Push client disconnected from localhost:30004 (beast)
Aug 23 04:44:15 raspi4 airspy_adsb[353]: Push client connected to localhost:30004 (beast)
As the graphs show, rebooting restored normal operations.
If this happens again, are there are other things I should check before rebooting? (I probably should have tried just restarting airspy_adsb, as some logs may have been lost in the reboot)
There is nothing in /var/log/messages or /var/log/syslog at the relevant time that gives any hint of a problem. The piaware log reports no messages received and no mlat data every five minutes, and restarts of dump1090 every hour or so.
My set up is a Raspi 4 fed from an Airspy Mini attached to a Uputronics SAW filter/Pre-amp - powered separately from the Pi via 50cm 24awg USB cables. The Pi is powered via POE through a RasPi POE hat. Latest version of Raspbian Buster, airspy_adsb v1.85
I have run Wiedehopf’s undervoltage script - that shows no problems.
Any thoughts on possible causes or diagnostics would be appreciated.
Thanks, John
