TLS alert:close notify keeps happening


#1

This has been happening repeatedly over the past half hour:

03/11/2016 21:55:18 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 21:55:18 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 21:56:09 FlightAware server SSL certificate validated
03/11/2016 21:56:09 encrypted session established with FlightAware
03/11/2016 21:56:09 no eth0 device, using 00:0f:60:01:28:72 from device 'wlan2’
03/11/2016 21:56:09 autoUpdate in adept config is disabled, disallowing update
03/11/2016 21:56:09 manualUpdate in adept config is enabled, allowing update
03/11/2016 21:56:09 multilateration support enabled (use piaware-config to disable)
03/11/2016 21:56:09 Login attempt with adept server at piaware.flightaware.com/1200 timed out
03/11/2016 21:56:09 TLS alert: close notify
03/11/2016 21:56:09 reconnecting in 108 seconds…

I was testing my upgraded minibian Jessie (done a couple of hours ago) and thought that was the problem. But I restarted with my previous version and am getting the same error message.

Any thoughts?

Richard


No data-feed
#2

I am currently running into the same issue.
03/11/2016 22:13:36 autoUpdate in adept config is enabled, allowing update
03/11/2016 22:13:36 manualUpdate in adept config is enabled, allowing update
03/11/2016 22:13:36 multilateration support enabled (use piaware-config to disable)
03/11/2016 22:13:36 Login attempt with adept server at 70.42.6.197/1200 timed out
03/11/2016 22:13:36 TLS alert: close notify
03/11/2016 22:13:36 reconnecting in 63 seconds…
03/11/2016 22:14:39 Connecting to FlightAware adept server at 70.42.6.198/1200
03/11/2016 22:14:39 Connection with adept server at 70.42.6.198/1200 established
03/11/2016 22:14:39 TLS handshake with adept server at 70.42.6.198/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:14:39 reconnecting in 100 seconds…
03/11/2016 22:14:54 1022 msgs recv’d from dump1090-mutab (944 in last 5m); 0 msgs sent to FlightAware
03/11/2016 22:16:19 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:16:19 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:16:19 TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:16:19 reconnecting in 87 seconds…

Edit: Which leads me to believe this is a flightaware or piaware OS issue. TLS is an encryption protocol, so there is probably a certificate or other security issue going on.


#3

I am seeing this as well over two different connections…


#4

[2016-03-11 23:29 CET] autoUpdate is not set in adept config, looking further…
[2016-03-11 23:29 CET] autoUpdate in /etc/piaware is enabled, allowing update
[2016-03-11 23:29 CET] manualUpdate is not set in adept config, looking further…
[2016-03-11 23:29 CET] manualUpdate in /etc/piaware is enabled, allowing update
[2016-03-11 23:29 CET] multilateration support enabled (use piaware-config to disable)

:frowning: :frowning: :frowning: :frowning:


#5

I am seeing these errors as well.

One system:
03/11/2016 22:32:04 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:32:04 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:32:04 TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:32:04 reconnecting in 101 seconds…
03/11/2016 22:33:45 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:33:45 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:34:36 FlightAware server SSL certificate validated
03/11/2016 22:34:36 encrypted session established with FlightAware
03/11/2016 22:34:36 autoUpdate in adept config is disabled, disallowing update
03/11/2016 22:34:36 manualUpdate in adept config is disabled, disallowing update
03/11/2016 22:34:36 multilateration support enabled (use piaware-config to disable)
03/11/2016 22:34:36 Login attempt with adept server at piaware.flightaware.com/1200 timed out
03/11/2016 22:34:36 TLS alert: close notify
03/11/2016 22:34:36 reconnecting in 105 seconds…

The other system:
03/11/2016 22:40:31 TLS alert: close notify
03/11/2016 22:40:31 reconnecting in 104 seconds…
03/11/2016 22:42:08 194520 msgs recv’d from dump1090-mutab (1951 in last 5m); 168261 msgs sent to FlightAware
03/11/2016 22:42:15 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:42:15 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:43:01 FlightAware server SSL certificate validated
03/11/2016 22:43:01 encrypted session established with FlightAware
03/11/2016 22:43:01 autoUpdate in adept config is disabled, disallowing update
03/11/2016 22:43:01 manualUpdate in adept config is disabled, disallowing update
03/11/2016 22:43:01 multilateration support enabled (use piaware-config to disable)
03/11/2016 22:43:01 Login attempt with adept server at piaware.flightaware.com/1200 timed out
03/11/2016 22:43:01 TLS alert: close notify
03/11/2016 22:43:01 reconnecting in 109 seconds…
03/11/2016 22:44:50 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:44:50 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:45:39 FlightAware server SSL certificate validated
03/11/2016 22:45:39 encrypted session established with FlightAware
03/11/2016 22:45:39 autoUpdate in adept config is disabled, disallowing update
03/11/2016 22:45:39 manualUpdate in adept config is disabled, disallowing update
03/11/2016 22:45:39 multilateration support enabled (use piaware-config to disable)
03/11/2016 22:45:39 Login attempt with adept server at piaware.flightaware.com/1200 timed out
03/11/2016 22:45:39 TLS alert: close notify
03/11/2016 22:45:39 reconnecting in 105 seconds…
03/11/2016 22:47:08 196764 msgs recv’d from dump1090-mutab (2244 in last 5m); 168261 msgs sent to FlightAware
03/11/2016 22:47:24 Connecting to FlightAware adept server at 70.42.6.197/1200
03/11/2016 22:47:24 Connection with adept server at 70.42.6.197/1200 established
03/11/2016 22:47:24 TLS handshake with adept server at 70.42.6.197/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:47:24 reconnecting in 99 seconds…
03/11/2016 22:49:03 Connecting to FlightAware adept server at 70.42.6.198/1200
03/11/2016 22:49:03 Connection with adept server at 70.42.6.198/1200 established
03/11/2016 22:49:03 TLS handshake with adept server at 70.42.6.198/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:49:03 reconnecting in 83 seconds…
03/11/2016 22:50:26 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:50:26 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:50:26 TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:50:26 reconnecting in 87 seconds…


#6

Same Issue Here, started about an hour ago… :frowning:

[2016-03-11 14:30 MST] 357539 msgs recv’d from dump1090-mutabi (390 in last 5m); 357414 msgs sent to FlightAware
[2016-03-11 14:34 MST] autoUpdate is not configured in /etc/piaware or by piaware-config
[2016-03-11 14:34 MST] manualUpdate in adept config is disabled, disallowing update
[2016-03-11 14:34 MST] multilateration support enabled (use piaware-config to disable)

[2016-03-11 15:35 MST] autoUpdate is not configured in /etc/piaware or by piaware-config
[2016-03-11 15:35 MST] manualUpdate in adept config is disabled, disallowing update
[2016-03-11 15:35 MST] multilateration support enabled (use piaware-config to disable)


#7

Same issue here.

03/11/2016 22:43:47 Connection to adept server at piaware.flightaware.com/1200 failed: connection reset by peer
03/11/2016 22:43:47 reconnecting in 89 seconds…
03/11/2016 22:44:09 piaware received a message from dump1090-mutab!
03/11/2016 22:44:17 20 msgs recv’d from dump1090-mutab; 0 msgs sent to FlightAware
03/11/2016 22:45:16 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:45:16 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:45:16 TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:45:16 reconnecting in 76 seconds…


#8

Plus one with the same issue…Problems on server side?


#9

Same here after a reboot about an hour ago. All seems normal except the fact that cannot complete TLS handshake. Have rebooted several times…

Tail of /tmp/piaware.out:
03/11/2016 22:38:59 Login attempt with adept server at 70.42.6.198/1200 timed out
03/11/2016 22:38:59 TLS alert: close notify
03/11/2016 22:38:59 reconnecting in 111 seconds…
03/11/2016 22:40:50 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/11/2016 22:40:51 Connection with adept server at piaware.flightaware.com/1200 established
03/11/2016 22:40:51 TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: connection reset by peer
03/11/2016 22:40:51 reconnecting in 65 seconds…

edit: added output of sudo piaware-status below

pi@pa-port-orange-fl-1 ~ sudo piaware-status 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 NOT connected to FlightAware. dump1090 is producing data on port 30005. pi@pa-port-orange-fl-1 ~


#10

If you check the stats page of ANY user, their MLAT stats have tanked over the last 90 minutes. There are clearly server issues.


#11

We’re currently investigating this. We should have it identified soon.


#12

One of my RPIs shows decreased MLAT traffic. The other actually shows increased traffic.


#13

Should be coming back up now, database issues on one of the endpoints.


#14

up an working again for me @ 13 minutes past the hour


#15

Yep, all good here. Thanks guys!


#16

looks to be back.


#17

Could this be happening again?
I just stated getting Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Name or service not known
Since yesterday.
I swapped my SDcard to a new pi hardware, new dongle, checked for updates, et al.

Nothing I can do can get MLAT working…


#18

You (or your ISP) have a DNS problem.