After upgrading to version 2.6, we seem to get this connectivity error 40% of the time during deployments.
Operation: Acquire package [PackageName] failed with error: Operation: Upload package to https://192.168.3.9:10933/ failed with error: One or more items in the current operation failed.
Fatal 09:48:45
The step failed
Exception:
The remote host aborted the connection. This can happen when the remote server does not trust the certificate that we provided.
Pipefish.PipefishException: The remote host aborted the connection. This can happen when the remote server does not trust the certificate that we provided. —> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at Octopus.Shared.FileTransfer.FileSender.b__5(Stream stream) in y:\work\refs\heads\release\source\Octopus.Shared\FileTransfer\FileSender.cs:line 110
at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request, Action1 response) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 83 --- End of inner exception stack trace --- at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request, Action
1 response) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 114
at Pipefish.Transport.SecureTcp.Streaming.Client.StreamClient.Send(Action`1 streamWriter, Int64 contentLength) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\Streaming\Client\StreamSender.cs:line 60
at Octopus.Shared.FileTransfer.FileSender.Receive(SendStreamRequest message) in y:\work\refs\heads\release\source\Octopus.Shared\FileTransfer\FileSender.cs:line 122
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in y:\work\3cbe05672d69a231\source\Pipefish\Actor.cs:line 113
Octopus.Server version 2.6.0.778
If we click retry, sometimes it just works. We hadn’t run into this before the upgrade and it doesn’t seem to be affected by the ‘Polling’ versus ‘Listening’ configuration.
This is dramatically effecting our build-deploy cycle and causing build-failures left and right. Any help will be greatly appreciated.