Two stations running Piaware 3.6.3 quit reporting several days ago and I am just now trying to figure out what to do. Piaware is receiving and displays aircraft on the map on the local network. Running piaware-status shows all is well except there is no connection to FlightAware. After rebooting and power cycling there still is no connection to FlightAware. My 1090 ADS-B and 978UAT stations have been down several days now. How can I do to get these two stations to reconnect to FlightAware?
piaware-status dump:
pi@piaware1090:~$ sudo piaware-status
PiAware master process (piaware) is running with pid 23635.
PiAware ADS-B client (faup1090) is running with pid 23653.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 531.
dump1090-fa (pid 531) is listening for connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is 59640abc-d579-4f36-a7da-13b78163bbb1 (from /var/cache/piaware/feeder_id)
The output is: âNo journal files were found.â
Another oddity is that under Configure, I see the following error: âSorry, the log appears to be empty at the moment. Please try again later.â Commands in the Configure window appear to do nothing.
No problem, missed the sudo as well. Note that I truncated the output below, as it continued for several screens with the âMay 12 22:nn:nn piaware1090 piaware[532]: Connection attempt with adept server at 70.42.6.198/1200 timed outâ message repeatedly. - Tom
Output from journalctl command:
â Logs begin at Sun 2019-05-12 22:22:11 UTC, end at Tue 2019-05-14 18:51:01 UTC. â
May 12 22:22:19 piaware1090 systemd[1]: Starting FlightAware ADS-B uploaderâŚ
May 12 22:22:19 piaware1090 systemd[1]: Started FlightAware ADS-B uploader.
May 12 22:22:22 piaware1090 piaware[532]: creating pidfile /run/piaware/piaware.pid
May 12 22:22:22 piaware1090 piaware[532]: ****************************************************
May 12 22:22:22 piaware1090 piaware[532]: piaware version 3.6.3 is running, process ID 532
May 12 22:22:22 piaware1090 piaware[532]: your system info is: Linux piaware1090 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux
May 12 22:22:24 piaware1090 piaware[532]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
May 12 22:22:24 piaware1090 piaware[532]: Connection to adept server at piaware.flightaware.com/1200 failed: couldnât open socket: Name or service not known
May 12 22:22:24 piaware1090 piaware[532]: reconnecting in 57 secondsâŚ
May 12 22:22:26 piaware1090 sudo[599]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /bin/netstat --program --tcp --wide --all --numeric
May 12 22:22:26 piaware1090 sudo[601]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
May 12 22:22:26 piaware1090 sudo[601]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 12 22:22:26 piaware1090 sudo[601]: pam_unix(sudo:session): session closed for user root
May 12 22:22:26 piaware1090 piaware[532]: ADS-B data program âdump1090-faâ is listening on port 30005, so far so good
May 12 22:22:26 piaware1090 piaware[532]: Started faup1090 (pid 610) to connect to dump1090-fa
May 12 22:22:26 piaware1090 piaware[532]: piaware received a message from dump1090-fa!
May 12 22:22:57 piaware1090 piaware[532]: 426 msgs recvâd from dump1090-fa; 0 msgs sent to FlightAware
May 12 22:23:21 piaware1090 piaware[532]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
May 12 22:23:21 piaware1090 piaware[532]: Connection to adept server at piaware.flightaware.com/1200 failed: connection refused
May 12 22:23:21 piaware1090 piaware[532]: reconnecting in 62 secondsâŚ
May 12 22:24:23 piaware1090 piaware[532]: Connecting to FlightAware adept server at 70.42.6.224/1200
May 12 22:24:53 piaware1090 piaware[532]: Connection attempt with adept server at 70.42.6.224/1200 timed out
May 12 22:24:53 piaware1090 piaware[532]: reconnecting in 51 secondsâŚ
May 12 22:25:44 piaware1090 piaware[532]: Connecting to FlightAware adept server at 70.42.6.198/1200
May 12 22:26:14 piaware1090 piaware[532]: Connection attempt with adept server at 70.42.6.198/1200 timed out
May 12 22:26:14 piaware1090 piaware[532]: reconnecting in 50 secondsâŚ
InterestingâŚ
gives me a âcommand not foundâ from the raspian console
When run from my Mac, traceroute fails after the 12th hop through 64 attempts:
A captive portal means you need to visit a website and enter a password or something to get Internet.
Does your router feature something like that?
Did you have static IP addresses configured by chance?
With a new router that might create problems if the new subnet is different.
(for example router might be 192.168.2.1 while the old router was 192.168.1.1)
The Internet is working for all connected devices other than the FlightAware Raspberry Piâs. The old router both used the 192.168.1.1 subnet, as does the new router.
I will check the Raspberry Piâs for fixed IP configs shortly.
âA captive portal means you need to visit a website and enter a password or something to get Internet.
Does your router feature something like that?â
The PiAware 3.6.3 status screen still shows ânot connected to FlightAwareâ after modifying /etc/dhcpcd.conf to reflect the new router, gateway and DNS address 192.168.1.254, then rebooting the pi. The static ip assignment has been running fine since October 2016.
Are other changes needed in dhcpcd.conf or elsewhere?
The router shows actual DNS addresses of 68.94.156.9 and 68.94.157.9. Should this be listed or 192.168.1.254 as shown above in the dhcpcd.conf partial listing?
