Tentacle logging exception

The tentacle on one of the machines is throwing an exception:
2016-11-11 13:00:45.0407 6 INFO listen://[::]:10933/ 6 Unhandled error when handling request from client: [::ffff:10.10.108.198]:58947
System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamReader.ReadBuffer()
at System.IO.StreamReader.ReadLine()
at Halibut.Transport.Protocol.MessageExchangeStream.ReadLine()
at Halibut.Transport.Protocol.MessageExchangeStream.ExpectNextOrEnd()
at Halibut.Transport.Protocol.MessageExchangeProtocol.ProcessClientRequests(Func2 incomingRequestProcessor) at Halibut.Transport.Protocol.MessageExchangeProtocol.ExchangeAsServer(Func2 incomingRequestProcessor, Func2 pendingRequests) at Halibut.Transport.SecureListener.ExecuteRequest(TcpClient client) System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.IO.StreamReader.ReadBuffer() at System.IO.StreamReader.ReadLine() at Halibut.Transport.Protocol.MessageExchangeStream.ReadLine() at Halibut.Transport.Protocol.MessageExchangeStream.ExpectNextOrEnd() at Halibut.Transport.Protocol.MessageExchangeProtocol.ProcessClientRequests(Func2 incomingRequestProcessor)
at Halibut.Transport.Protocol.MessageExchangeProtocol.ExchangeAsServer(Func2 incomingRequestProcessor, Func2 pendingRequests)
at Halibut.Transport.SecureListener.ExecuteRequest(TcpClient client)

The reason we were looking at this tentacle is that it keeps going off line.

Hi Leslie,

Thanks for getting in touch! This error shows when, as you have correctly determined, a tentacle goes offline but has an open connection to the Octopus server. It however is not the cause of a Tentacle going offline just the outcome.

If you would like help trying to figure out why the Tentacle is going offline the Tentacle logs would be of help. These are found in C:\Octopus\Logs on standard installations.
If the service is stopping, then any message from the event viewer may also help. Could you also let me know what version of Octopus/Tentacle you are using.

Thanks!
Vanessa

Attached is the log file. The tentacle version is 3.5.1 as is the server

OctopusTentacle.txt (8 KB)

Hi Leslie,
Thanks for sending through the logs as requested. Unfortunately, the errors provided are all pretty generic so we are having a hard time working out what could be going wrong.
You say that the Tentacles keep going offline, is this just through the day that you notice they are flagged as offline or do deployments suddenly fail? Could you perhaps provide more Tentacle logs that might shed some light on what it was doing before this failiure. It would also be greatly appreciated if you could shoot through some of the Server logs as well (this is usually found in C:\Octopus\Logs)
Any and all information that relates to this issue would help us greatly to trying to diagnose the cause.
I’m sorry that at the moment it feels like we are missing a key peice of the puzzle.
Thanks in advance,
Rob