Server problems?


#1

Looks like the server is having issues.
My data is being sent fine, but it looks like data isnt processed
My graphs and number of planes seen is hardly getting updated with new planes.

I double checked it with other feeders which show the same so its not only me.
Als my map of my feeders shows many planes so im pretty sure its not on my side


#2

Might have been a hickup though,… seems like its functioning normally again.

Went wrong around 8 am CET and back to normal around 10:30am CET


#3

Mine stopped uploading data at 0818 and is still not uploading to Flightaware.


#4

Same here also in the UK around the same time.
Piaware running but “my adsb” screen not updated for 2 hours, dump1090 running and i can see local graphic map/aircraft from dump1090 in "my adsb " screen when i click on link .

piaware-status

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.

Seems okay at my end…but not at FA end.


#5

Noticed all piaware units in my area not having sent data for 4 hours.

DST?


#6

from /tmp/piaware.out:



03/08/2015 13:26:39 unrecognized message type 'log' from server, ignoring...
03/08/2015 13:26:39 unrecognized message type 'log' from server, ignoring...
03/08/2015 13:26:39 logged in to FlightAware as user komplize
03/08/2015 13:26:39 unrecognized message type 'login' from server, ignoring...
03/08/2015 13:26:48 reconnecting after 60s...



#7

There are a bunch of feeders in my area that appear to be off line. My stats dropped very low for two hours but came back on their own.

LitterBug


#8

When i run piaware -debug
I get messages

“from server (can’t read “row(type)”: no such element in array), (can’t read “row(type)”: no such element in array

also

03/08/2015 14:02:08 FlightAware server SSL certificate validated
03/08/2015 14:02:08 encrypted session established with FlightAware
03/08/2015 14:02:08 autoUpdate in adept config is enabled, allowing update
03/08/2015 14:02:08 manualUpdate in adept config is enabled, allowing update
03/08/2015 14:02:08 unrecognized message type ‘log’ from server, ignoring…
03/08/2015 14:02:08 unrecognized message type ‘log’ from server, ignoring…
03/08/2015 14:02:08 that’s too many, i’m disconnecting and reconnecting…


#9

Same for me in Texas. I am re-booting the RasPI now ‘just for good measure’, but expect the outage is on the FA side.
I’m gonna blame the time change (DST) in the US just because…

UPDATE: After the re-boot the RaspPI is feeding again.


#10

Mine is similar although I’m running dump1090-mutability:

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

I just wanted to make sure it wasn’t dump1090-mutab causing any problems.


#11

I’m having problems here, too. Seems to be on the server side. I wonder if the switch to daylight saving time this morning has something to do with it?

03/08/2015 14:22:03 reconnecting after 60s…
03/08/2015 14:22:52 2720 msgs recv’d from dump1090 (146 in last 5m); 198 msgs sent to FlightAware
03/08/2015 14:23:03 connecting to FlightAware 70.42.6.203/1200
03/08/2015 14:23:03 got ‘couldn’t open socket: connection refused’ to adept server at 70.42.6.203/1200, will try again soon…
03/08/2015 14:24:36 connecting to FlightAware eyes.flightaware.com/1200
03/08/2015 14:24:36 got ‘couldn’t open socket: connection refused’ to adept server at eyes.flightaware.com/1200, will try again soon…
03/08/2015 14:25:45 connecting to FlightAware 70.42.6.203/1200
03/08/2015 14:25:45 got ‘couldn’t open socket: connection refused’ to adept server at 70.42.6.203/1200, will try again soon…
03/08/2015 14:27:18 connecting to FlightAware eyes.flightaware.com/1200
03/08/2015 14:27:18 got ‘couldn’t open socket: connection refused’ to adept server at eyes.flightaware.com/1200, will try again soon…

Damon


#12

I had a problem too for a few hours here in India. I rebooted my FF box and then saw the stats pick up.


#13

Seems to have come alive again.
But flight list my station has contributed data to are missing.


#14

Seems the outage didn’t affect everyone. One of my feeds was affected and one was not. Others in my area were affected and some were not.

Marty


#15

Looks like they may have sent a “restart” out (not reboot). The feeds that were not sending are now. One that was fine is now silent starting the same time frame the others came back. Checked my processes and they have not restarted since Feb 23.

LitterBug


#16

Hi,
Anyone know what the above fault could be, “flights” menu in “my adsb” page is blank , but aircraft and message data stats increasing now, station showing as live so outage restored but still the flight list prob persists.

Thanks in advance.

Mike

flightaware.com/user/Radiostationx


#17

looked at some other local radar sites , they have no flight lists/tracklogs either.


#18

Hi everyone,

We had a server-side problem in processing ADS-B from some sites, it’s fixed now.


#19

Thanks mduell,
Everything is back to normal now.
Cheers. :smiley: