Tentacles throwing exceptions

Using Octopus Deploy
Every 10 seconds my tentacles throw an exception: This seems to be SSL related?

2014-02-15 22:36:02.5320 ERROR Unhandled error when processing request from client
System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at Pipefish.Transport.SecureTcp.Server.SecureTcpServer.ExecuteRequest(TcpClient client) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Server\SecureTcpServer.cs:line 109

Hi Gavin,

It looks as though there’s another Octopus server (1.6?) trying to connect to the Tentacle. Is that possible?

We have an EXE that logs the incoming request’s origin, if that would help, (2.1 records this info in the error message :))


hmmm, cant imagine how… I will check