Failed to exchange Hello messages - No Error

Hello:

I can’t say that I’m seeing any problems - woohoo - but I’m seeing a lot of these messages in the log for one of my devices:

2020-03-25 15:17:28 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:17:28 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: EOF
2020-03-25 15:17:49 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:19:00 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:19:00 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:19:00 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:20:31 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:20:51 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:23:34 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:23:34 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:23:56 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR
2020-03-25 15:25:06 Failed to exchange Hello messages with OC54F7U-*******-*******-*******-*******-*******-*******-******* at [::]:22000-194.xx.yyy.zzz:13358/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR

As I say, it’s not causing me a problem (and another device in the cluster isn’t showing the same error for this device) - but thought you might want to know incase it’s indicative of something bigger…

Thanks.

NO_ERROR, eh? I’m guessing this is some sort of weirdness in the error handling in the QUIC package… :confused:

NO_ERROR I think it’s just a “graceful” shutdown.

There is no graceful way to terminate connections in TCP. If a connection stops working, there must be some error, and you always end up with “connection reset by peer”/“EOF”, which you never know if it’s graceful or not.

Quic keeps the same semantics, that every connection always ends with an error, yet in this case indicates it was a graceful shutdown.

Why it’s doing it repeatedly in a short period of time, I don’t know.