Deployments wont finish getting packages

Our deployments in 2.0 are now timing out at over 14 hours, etc… I’m not sure how many successful deployments we’ve had since the 2.0 upgrade. We may have to roll back to 1.6 if we cant get this resolved.

Nothing is different, same machine involved, now 2.09 -

100s of Megabytes of the same error in the log: (these are from a tentacle still running 1.6 that we havent upgraded yet)

2014-01-23 00:00:14.5368 FATAL
Pipefish.PipefishException: The response from the remote host was not a valid SSL/TLS handshake. This can happen when a different service than expected is listening on the remote port. Visiting http://172.31.11.38:10933/handshake in a web browser may assist with identifying the listening service. —> 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.StartSendBlob(Byte[] incoming, Int32 count, 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.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 59
— End of inner exception stack trace —
at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 105
at Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
2014-01-23 00:00:14.5368 ERROR Failed to discover SQUID for CSI EUAT US x64
Pipefish.Errors.PipefishCommunicationException: The handshake failed due to an unexpected packet format.
at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at Octopus.Server.Communications.Handshaking.PassiveTentacleSquidFinder.d__f.MoveNext() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleSquidFinder.cs:line 98
Pipefish.PipefishException: The response from the remote host was not a valid SSL/TLS handshake. This can happen when a different service than expected is listening on the remote port. Visiting http://172.31.11.38:10933/handshake in a web browser may assist with identifying the listening service. —> 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.StartSendBlob(Byte[] incoming, Int32 count, 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.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 59
— End of inner exception stack trace —
at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 105
at Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
2014-01-23 00:00:14.5837 ERROR Error in PassiveTentacleHandshaker-8Sk-j81aRyvO@SQ-US-HQ-OCTS-02-546BED59 while receiving 019db1c2-912d-40cb-84be-3f502a9471fc
Pipefish.PipefishException: The response from the remote host was not a valid SSL/TLS handshake. This can happen when a different service than expected is listening on the remote port. Visiting http://172.31.11.28:10933/handshake in a web browser may assist with identifying the listening service. —> 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.StartSendBlob(Byte[] incoming, Int32 count, 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.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 59
— End of inner exception stack trace —
at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 105
at Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
2014-01-23 00:00:14.5837 FATAL

That error may be unrelated, but this is what I’m seeing on the dashboard:

Hi Gavin,

The 1.6 machines will need to be removed from the 2.0 Octopus server unless you’re ready to upgrade them. Octopus deploys to all machines in an environment, so having machines in the environment running the old Tentacle will cause these failures.

Have you looked at installing the 2.0 Tentacle agent side-by-side with the 1.6 agent, but using a different port? There’s some information in the upgrade guide I believe: http://docs.octopusdeploy.com/display/OD/Upgrading+from+Octopus+1.6

Hope this helps, let me know if not :slight_smile:

Cheers,
Nick

No, I t didn’t really help… I removed the tentacles. Deployments are still taking 7-12 hours… Going to have to revert to 1.6.

New features are great, but for whatever reason package uploading/downloading has taken a significant performance downgrade in this version…

Was able to stay on 2.0… Had to clean out the tentacles, certificates and all to get them to work right…

Thanks for the follow-up. Not sure what was blocking things up - glad it is resolved.

Cheers,
Nick