Octopus Deploy tentacle : Unhandled error when handling request from client

Legacy Uncategorised
1

Hello,

We are seeing those errors recurrently, about once per hour. I edited the IP adresses manually (for confindentiality purposes) :

2016-11-16 01:24:31.2478 62 INFO listen://[::]:10933/ 62 Accepted TCP client: [::ffff:111.111.111.111]:50918
2016-11-16 01:24:31.2478 32 INFO listen://[::]:10933/ 32 Performing TLS server handshake
2016-11-16 01:24:46.2478 32 INFO listen://[::]:10933/ 32 Secure connection established, client is not yet authenticated, client connected with Tls12
2016-11-16 01:24:46.2478 32 INFO listen://[::]:10933/ 32 Client at [::ffff:111.111.111.111]:50918 authenticated as 8D2D044555C4B233E92356D58FB1B00B8C5A1339
2016-11-16 01:34:54.9209 32 INFO listen://[::]:10933/ 32 Unhandled error when handling request from client: [::ffff:111.111.111.111]:50918
System.IO.IOException: Impossible de lire les données de la connexion de transport : Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. —> System.Net.Sockets.SocketException: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu
à System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
à System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
— Fin de la trace de la pile d’exception interne —
à System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
à System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
à System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
à System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
à System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
à System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count)
à System.IO.StreamReader.ReadBuffer()
à System.IO.StreamReader.ReadLine()
à Halibut.Transport.Protocol.MessageExchangeStream.ReadLine() dans Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\Protocol\MessageExchangeStream.cs:ligne 93
à Halibut.Transport.Protocol.MessageExchangeStream.ExpectNextOrEnd() dans Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\Protocol\MessageExchangeStream.cs:ligne 67
à Halibut.Transport.Protocol.MessageExchangeProtocol.ProcessClientRequests(Func`2 incomingRequestProcessor) dans Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\Protocol\MessageExchangeProtocol.cs:ligne 110
à Halibut.Transport.SecureListener.ExecuteRequest(TcpClient client) dans Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureListener.cs:ligne 140

We’re using Octopus server 3.4.4, and we tried tentacle versions 3.4.4 and 3.4.13, with the very same behaviour.

Is this a known issue ? is it solved in later versions, if so, in which one ?

The tentacle installation is nothing fancy, just the basic “next next finish” installation.

Thanks,

Adrien

2

Hi Adrien,

Thanks for getting in touch. I assume the Tentacle is set up in “listening” mode, so the Octopus server is connecting to it?

It looks like the Octopus server connects at 01:24:46, but then something breaks the connection. Tentacle is “reading” the connection, waiting for Octopus to send something, but it never comes. At 01:34.54 (10 minutes later), Tentacle gives up, and closes the connection.

Inside Octopus, on the Environments page, you can go to the machine and go to the Connectivity tab. That will show the Octopus version of the logs - I’d guess there might be something there about the time out too. If you can share those with me it might give us a better idea.

Depending on the network between the Octopus and Tentacle, there could be a firewall or router in the way that doesn’t like to keep connections open for too long without a lot of traffic flowing over them, so it’s terminating the connections early.

That said, as long as Octopus/Tentacle is generally working (you can deploy applications, etc.), you can ignore this message.

Paul Stovell