Can’t get Piaware to work after re-image with version 7.1
(FR24 feeder running fine)
pi@piaware:~ $ piaware-status
PiAware master process (piaware) is not running.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 423.
dump1090-fa (pid 423) is listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is xxx
From logs:
Jan 12 19:03:34 piaware piaware[441]: creating pidfile /run/piaware/piaware.pid
Jan 12 19:03:34 piaware piaware[441]: ****************************************************
Jan 12 19:03:34 piaware piaware[441]: piaware version 7.1 is running, process ID 441
Jan 12 19:03:34 piaware piaware[441]: your system info is: Linux piaware 5.10.63-v7+ #1488 SMP Thu Nov 18 16:14:44 GMT 2021 armv7l GNU/Linux
Jan 12 19:03:35 piaware piaware[441]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 12 19:03:35 piaware piaware[441]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Jan 12 19:03:35 piaware piaware[441]: reconnecting in 5 seconds...
Jan 12 19:03:41 piaware piaware[441]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jan 12 19:03:41 piaware piaware[441]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
Jan 12 19:03:41 piaware piaware[441]: Started faup1090 (pid 585) to connect to dump1090-fa
Jan 12 19:03:41 piaware piaware[441]: UAT support disabled by local configuration setting: uat-receiver-type
Jan 12 19:03:41 piaware piaware[441]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 12 19:03:41 piaware piaware[441]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Jan 12 19:03:41 piaware piaware[441]: reconnecting in 6 seconds...
Jan 12 19:03:43 piaware piaware[441]: piaware received a message from dump1090-fa!
Jan 12 19:03:47 piaware piaware[441]: Connecting to FlightAware adept server at 206.253.80.200/1200
Jan 12 19:04:02 piaware piaware[441]: Connection attempt with adept server at 206.253.80.200/1200 timed out
Jan 12 19:04:02 piaware piaware[441]: reconnecting in 5 seconds...
Jan 12 19:04:07 piaware piaware[441]: Connecting to FlightAware adept server at 206.253.84.198/1200
Jan 12 19:04:07 piaware piaware[441]: Connection with adept server at 206.253.84.198/1200 established
Jan 12 19:04:07 piaware piaware[441]: TLS handshake with adept server at 206.253.84.198/1200 completed
Jan 12 19:04:07 piaware piaware[441]: FlightAware server certificate validated
Jan 12 19:04:07 piaware piaware[441]: encrypted session established with FlightAware
Jan 12 19:04:08 piaware piaware[441]: logged in to FlightAware as user guest
Jan 12 19:04:08 piaware piaware[441]: my feeder ID is 0f6f13df-983b-4a5d-bda0-95e9c41c001c
Jan 12 19:04:11 piaware piaware[441]: 15 msgs recv'd from dump1090-fa; 0 msgs sent to FlightAware
Jan 12 19:04:26 piaware piaware[441]: piaware has successfully sent several msgs to FlightAware!
Jan 31 18:09:21 piaware piaware[441]: timed out waiting for alive message from FlightAware, reconnecting...
Jan 31 18:09:21 piaware piaware[441]: reconnecting in 5 seconds...
Jan 31 18:09:21 piaware piaware[441]: no new messages received in 1638276 seconds, it might just be that there haven't been any aircraft nearby but I'm going to try to restart everything, just in case...
Jan 31 18:09:22 piaware piaware[441]: faup1090 exited with SIG SIGHUP