Help: Feeder Checking In Data Not

[v1images]

Just changed internet ISP and have moved both of my feeders over to the new SSID. First feeder moved over no problem, 2nd one is not having as much joy.

When checking 192.168.0.XX:8080 for the 2nd feeder flights are displayed, however when checking feeder status on the Flight Aware website it is showing the following:

Data Feed: Today - about 3 hours ago
Feeder Check-in: Live - 3 minutes ago

I then do $ sudo piaware-status and get the following:

dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection timed out’
dump1090 is NOT producing data on port 30005.

Any suggestions on what I could do to isolate the issue and resolve or should I just restart a new SD image?

Thanks in advance for any help with this problem.

[crkbday]

@v1images

Any suggestions on what I could do to isolate the issue and resolve or should I just restart a new SD image?

Check the end of the piaware log

tail -20 /tmp/piaware.out

Type

nc localhost 30003

Do you get any output? Also,

sudo netstat -ntap | grep 30005

Lemme know what you see.

[v1images]

@crkbday

@v1images

Any suggestions on what I could do to isolate the issue and resolve or should I just restart a new SD image?

Check the end of the piaware log

tail -20 /tmp/piaware.out

04/11/2016 08:35:48 FlightAware server SSL certificate validated
04/11/2016 08:35:48 encrypted session established with FlightAware
04/11/2016 08:35:49 autoUpdate in adept config is enabled, allowing update
04/11/2016 08:35:49 manualUpdate in adept config is enabled, allowing update
04/11/2016 08:35:49 multilateration support enabled (use piaware-config to disable)
04/11/2016 08:35:49 logged in to FlightAware as user v1images
04/11/2016 08:35:50 multilateration support enabled (use piaware-config to disable)
04/11/2016 08:35:50 multilateration data requested, enabling mlat client
04/11/2016 08:35:50 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --udp-transport 70.42.6.198:5720:3206089347
04/11/2016 08:35:52 mlat(3038): fa-mlat-client 0.2.4 starting up
04/11/2016 08:35:52 mlat(3038): Using UDP transport to 70.42.6.198:5720
04/11/2016 08:36:18 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
04/11/2016 08:37:55 lost connection to dump1090 via faup1090
04/11/2016 08:37:55 reconnecting to dump1090
04/11/2016 08:37:55 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
04/11/2016 08:37:55 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 53.470 --lon -1.345
04/11/2016 08:37:55 Started faup1090 (pid 4881) to connect to dump1090
04/11/2016 08:38:00 mlat(3038): Connection to localhost:30005 lost: [Errno 110] Connection timed out
04/11/2016 08:38:00 mlat(3038): Reconnecting in 30.0 seconds
04/11/2016 08:38:01 mlat(3038): Beast-format results connection with localhost:30104: [Errno 110] Connection timed out*

Type

nc localhost 30003

Do you get any output?

Nothing

Also,

sudo netstat -ntap | grep 30005

Lemme know what you see.

tcp 0 0 0.0.0.0:30005 0.0.0.0: LISTEN 2367/dump1090
tcp 0 1 192.168.0.20:60827 127.0.0.1:30005 SYN_SENT 8593/faup1090
tcp 0 1 192.168.0.20:60819 127.0.0.1:30005 SYN_SENT 3038/fa-mlat-client*

[obj]

You’ve broken localhost somehow (or your firewall)