I have one of the deployments scripts failing with exit code.
This is the environment I have
11:56:25 Verbose | Octopus Server version: 3.3.15+
11:56:25 Info | Executing script on 'DCCHSRDVORA02'
11:56:41 Verbose | Octopus Deploy: Calamari version 3.3.13+
11:56:41 Verbose | Name Value
11:56:41 Verbose | ---- -----
11:56:41 Verbose | PSVersion 4.0
11:56:41 Verbose | WSManStackVersion 3.0
11:56:41 Verbose | SerializationVersion 1.1.0.1
11:56:41 Verbose | CLRVersion 4.0.30319.42000
11:56:41 Verbose | BuildVersion 6.3.9600.17400
11:56:41 Verbose | PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
11:56:41 Verbose | PSRemotingProtocolVersion 2.2
The script does some software installation tasks and then fails with
11:57:10 Fatal | The remote script failed with exit code 4809
The installation log does not reveal any error. The OctopusTentacle.txt does not show errors at the time of the deployment.
Earlier on I had this error, but it went away when I updated to 3.3.15:
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.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
Do you have any idea what could be causing this error?
I tried Michaels tipp from http://help.octopusdeploy.com/discussions/problems/43011-error-during-acquire-packages with the Halibut.TcpClientPooledConnectionTimeout, but it did not fix the problem.
Kind Regards
Torsten