ERROR on Tentacle every 10 sec (v 2.0.8.977)

Hi,

Running on Win2012 standard server (x64)

The deploy sees to work, but I get ERRORS in the Eventlog.

From the log file on the Tentacle:
2014-01-02 14:45:53.2481 TRACE Accepted TCP client 10.45.1.170:62479
2014-01-02 14:45:53.2481 ERROR Unhandled error when processing request from client
System.IO.IOException: The handshake failed due to an unexpected packet format.
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

The Tentacle have default installation ( listening )

The site on IIS are at the moment running a dummy SSL cet, for testing purposes.

So I get an SSL error in the browser when browsing both the site and the Tentacle endpoint.

Hi - in Tentacle Manager, under Communications, there should be a block of text describing how the Tentacle is connected to the Octopus server. It looks like you have multiple connections configured, the listening one and a (broken) polling one. Removing the polling connection details from Tentacle.config, and restarting the Tentacle Windows service should rectify this.

Regards,
Nick

Hi,
I’m not able to find any connection details in the Tentacle.config

Attaching, schreenshot from the Tentacle manager and the Tentacle.config (slightly modified)

I have tried to completely remove both the v1.6 and v2.0 tentacles (also cleaned up inside registry). Removed the Octopus working directory.

But the error is still comming every 10 sec when I have reinstalled the Tentacle v2.0

Tentacle.config (1 KB)

Thank you for that. I think I misinterpreted your initial description - the problem is something connecting inbound to the Tentacle. There may be additional information in the Tentacle log files (under e.g. C:\Octopus\Logs) and/or the Octopus log files (same location on the Octopus Server). If you’re able to email them to me (nblumhardt at our domain) I can take a look.

If you set up another Octopus server that may be connecting to the same Tentacles, this would be a possible cause (or, if you have an Octopus 1.6 server trying to connect to the Tentacles on the same port).

HTH!

Yes we had the same issue, it was caused by still having 1.6 versions of the tentacles/server installed

Hi,

I forgot the still active 1.6 server.

I removed the 1.6 installation and I’m no longer getting the errors.

Thanks.