Hi all,
my PiAware stopped sending messages last saturday, but I don’t know why.
sudo piaware-status
PiAware master process (piaware) is running with pid 30585.
PiAware ADS-B client (faup1090) is running with pid 30621.
PiAware mlat client (fa-mlat-client) is running with pid 30632.
Local ADS-B receiver (dump1090-mutabi) is running with pid 29331.
dump1090-muta (pid 29331) is listening for connections on port 30005.
**faup1090 is NOT connected to the ADS-B receiver.**
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Logs:
Feb 11 09:40:25 raspberrypi piaware[30585]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.225:5863:789142788
Feb 11 09:40:26 raspberrypi piaware[30585]: piaware has successfully sent several msgs to FlightAware!
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): fa-mlat-client 0.2.10 starting up
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): Using UDP transport to 70.42.6.225 port 5863
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): Listening for Beast-format results connection on port 30105
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): Listening for Extended Basestation-format results connection on port 30106
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): Input connected to localhost:30005
Feb 11 09:40:26 raspberrypi piaware[30585]: mlat-client(30632): Input format changed to BEAST, 12MHz clock
Feb 11 09:40:27 raspberrypi piaware[30585]: mlat-client(30632): Beast-format results connection with 127.0.0.1:30104: connection established
dump1090 is running and serving others well:
sudo netstat -ntap | grep 30005
tcp 0 0 127.0.0.1:30005 0.0.0.0:* LISTEN 29331/dump1090-muta
tcp 0 0 127.0.0.1:36948 127.0.0.1:30005 ESTABLISHED 29355/socat
tcp 0 0 127.0.0.1:37666 127.0.0.1:30005 ESTABLISHED 30632/fa-mlat-clien
tcp 0 0 127.0.0.1:36938 127.0.0.1:30005 ESTABLISHED 19554/pfclient
tcp 0 0 127.0.0.1:30005 127.0.0.1:36948 ESTABLISHED 29331/dump1090-muta
tcp 0 0 127.0.0.1:30005 127.0.0.1:36938 ESTABLISHED 29331/dump1090-muta
tcp 0 0 127.0.0.1:36944 127.0.0.1:30005 ESTABLISHED 4111/fr24feed
tcp 12 0 127.0.0.1:30005 127.0.0.1:37666 ESTABLISHED 29331/dump1090-muta
tcp 0 0 10.0.1.10:53816 167.114.60.74:30005 ESTABLISHED 29355/socat
tcp 1503789 0 127.0.0.1:36940 127.0.0.1:30005 ESTABLISHED 26658/mono
tcp 9 0 127.0.0.1:30005 127.0.0.1:36944 ESTABLISHED 29331/dump1090-muta
I restarted the PiAware process, checked for the newest version, but the boxes keep showing red.
sudo piaware-config
allow-auto-updates yes # value set at /etc/piaware.conf:10
allow-manual-updates yes # value set at /etc/piaware.conf:9
feeder-id # value set at /etc/piaware.conf:11
flightaware-password <hidden> # value set at /etc/piaware.conf:8
flightaware-user <hidden> # value set at /etc/piaware.conf:7
Can’t see anything obviously wrong in the log to be honest.
There might be some routing / internet problem though.
Edit: Actually the log should look something like this:
Feb 11 10:05:49 pi piaware[2046]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Feb 11 10:05:49 pi piaware[2046]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 50 --lon 10
Feb 11 10:05:49 pi piaware[2046]: Started faup1090 (pid 2092) to connect to dump1090-fa
Feb 11 10:05:49 pi piaware[2046]: multilateration data requested
Feb 11 10:05:49 pi sudo[2095]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Feb 11 10:05:49 pi sudo[2095]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 11 10:05:49 pi sudo[2095]: pam_unix(sudo:session): session closed for user root
Feb 11 10:05:49 pi piaware[2046]: piaware received a message from dump1090-fa!
Feb 11 10:05:50 pi piaware[2046]: piaware has successfully sent several msgs to FlightAware!
Feb 11 10:06:21 pi piaware[2046]: 368 msgs recv'd from dump1090-fa; 368 msgs sent to FlightAware
Feb 11 10:11:21 pi piaware[2046]: 2198 msgs recv'd from dump1090-fa (1830 in last 5m); 2198 msgs sent to FlightAware
Feb 11 10:16:21 pi piaware[2046]: 4090 msgs recv'd from dump1090-fa (1892 in last 5m); 4090 msgs sent to FlightAware
Feb 11 10:21:21 pi piaware[2046]: 6194 msgs recv'd from dump1090-fa (2104 in last 5m); 6194 msgs sent to FlightAware
you might also want to remove GPS coordinates from the log if you care
(sorry i never think of that beforehand)
I’m not sure why faup seems to get disconnected but piaware is not reconnecting it.
Very strange.
I think dump1090-muta may have gotten confused, not even the whole pi.
Whatever, glad it works now.
(Just rebooting was just the last resort after i didn’t know what was going on!)
There is another set of lat/lon in the gist, so maybe just remove it
