RPi piaware stopped feeding to Feeder Page, local page OK

FlightAware ADS-B Flight Tracking
1

Hi Friends,
My RPi PiAware feed to the feeder page stopped working two days ago. Everything else seems OK including the live PiAware web interface here on my local network (though FA’s feeder page’s local link is wrong).

Here is my piaware.out dump:

04/21/2016 21:27:26 ****************************************************
04/21/2016 21:27:26 piaware version 2.1-5 is running, process ID 2186
04/21/2016 21:27:26 your system info is: Linux piaware 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux
04/21/2016 21:27:26 Connecting to FlightAware adept server at piaware.flightaware.com/1200
04/21/2016 21:27:26 Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: no such device or address (No address associated with hostname)
04/21/2016 21:27:26 reconnecting in 108 seconds…
04/21/2016 21:27:26 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
04/21/2016 21:27:26 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 42.002 --lon -73.082
04/21/2016 21:27:26 Started faup1090 (pid 2338) to connect to dump1090
04/21/2016 21:27:27 piaware received a message from dump1090!
04/21/2016 21:28:07 7 msgs recv’d from dump1090; 0 msgs sent to FlightAware
04/21/2016 21:29:14 Connecting to FlightAware adept server at piaware.flightaware.com/1200
04/21/2016 21:29:14 Connection with adept server at piaware.flightaware.com/1200 established
04/21/2016 21:29:15 FlightAware server SSL certificate validated
04/21/2016 21:29:15 encrypted session established with FlightAware
04/21/2016 21:29:15 autoUpdate is not set in adept config, looking further…
04/21/2016 21:29:15 autoUpdate in /etc/piaware is enabled, allowing update
04/21/2016 21:29:15 manualUpdate is not set in adept config, looking further…
04/21/2016 21:29:15 manualUpdate in /etc/piaware is enabled, allowing update
04/21/2016 21:29:15 multilateration support enabled (use piaware-config to disable)
04/21/2016 21:29:15 logged in to FlightAware as user halifax
04/21/2016 21:30:09 piaware has successfully sent several msgs to FlightAware!
04/21/2016 21:32:56 60 msgs recv’d from dump1090 (53 in last 5m); 32 msgs sent to FlightAware
04/21/2016 21:37:56 112 msgs recv’d from dump1090 (52 in last 5m); 84 msgs sent to FlightAware
04/21/2016 21:42:56 166 msgs recv’d from dump1090 (54 in last 5m); 138 msgs sent to FlightAware

Service interruption started on 4/18.
Any help appreciated.

Kind regards!

2

piaware-status output:

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

3

You have 2 receiving stations on your flightaware page.

http://flightaware.com/adsb/stats/user/halifax#stats-13963
status stopped

http://flightaware.com/adsb/stats/user/halifax#stats-22196
status running fine

Hope this helps.

4

Thank you!

Any idea why? I see 13963 - my long-time station number. Now a new one 22196 is running as well. Any way I can kill the inactive one?

Kind regards!
Harry

5

Did you use other hardware such as changing a raspberry pi for a spare unit but using the same sd card or changing wifi dongle ?
A hardware change is the most likely reason as the swap would instigate a change in mac address of your feeder station hence FA automatically creating another station/site code.
Many users have multiple raspberry pi / single baord computers running from the same geographical location.
You can dis-associate the feeder station you wish to get rid of.
There are facilities to do this in the control panel section of the particular site feeder page under the site name banner.
Look for the control panel optional settings area which include auto updating of piaware software.
At the bottom of this section is a setting :

“Dissociate Feeder Site”

If you have difficulty in removing the unwanted feed or it keeps re appearing after disassociation has been completed by you , I would suggest sending an email to FA stating your problem.