Any known PiAware Issues?

FlightAware ADS-B Flight Tracking
1

Are there any known feeding issues? My PiAware status is showing:

dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is listening for connections on port 10001.
faup1090 is connected to port 30005
piaware is connected to port 10001.
piaware is NOT connected to FlightAware.
dump1090 is producing data on port 30005.
dump1090 is producing data on port 10001.

I am feeding PlaneFinder with no issues and my local Python script to feed my own database is also running properly. The PiAware logs only show the last time it properly was feeding some 3 hours ago.

I have rebooted several times, but still get the not connected to FlightAware message in the PiAware status.

Marty

2

Are your FA userid and password correct?

3

Yes, nothing has changed regarding that.

Marty

4

I had to reinstall PiAware to get it to reconnect to FlightAware.

Marty

5

I’ve had no issues with either of my RPi feeders lately.

6

This email is a friendly notification that your PiAware ‘xx:xx:xx:xx:xx:xx’ is not currently sending live flight data to FlightAware. Your receiver last connected to FlightAware on 27-Aug-2015 01:08PM. This may represent a problem in your setup that may need your attention. Feel free to contact us with any questions about how to setup PiAware to share with FlightAware or the benefits of sharing with FlightAware.


08/27/2015 20:08:20 NOTICE adept server is shutting down.  reason: server exiting due to SIGTERM signal
08/27/2015 20:08:22 lost connection to FlightAware, reconnecting...
08/27/2015 20:08:22 reconnecting after 60s...
08/27/2015 20:09:22 connecting to FlightAware eyes.flightaware.com/1200
08/27/2015 20:09:22 got 'couldn't open socket: connection refused' to adept server at eyes.flightaware.com/1200, will try again soon...
[snip]
08/28/2015 18:03:01 connecting to FlightAware eyes.flightaware.com/1200
08/28/2015 18:03:01 got 'couldn't open socket: connection refused' to adept server at eyes.flightaware.com/1200, will try again soon...
08/28/2015 18:04:10 connecting to FlightAware 70.42.6.203/1200
08/28/2015 18:04:10 got 'couldn't open socket: connection refused' to adept server at 70.42.6.203/1200, will try again soon...

Tried connecting to eyes.flightaware.com:1200 from 3 hosts around the internet, checked the IP against ns1.flightaware.com, etc.

7

My Android feeder is down and it shows it’s receiving and connected. I rebooted, checked for updates and still shows down.

8

If your piaware is trying to connect to eyes by name, it is out of date and you should update it. (eyes is being taken out of use)

9

Thanks for the heads-up. I’ve got mine working again. (changed eyes to piaware)

[EDIT: And from the looks of my logs, seems like eyes is back up and responding again anyways as of a few hours ago]