DS 6.9 - Client would randomly fail task with Timeout error after Reboot task
Last Updated May 07, 2013
When performing large task with Reboots and Scripts - you might randomly encounter an issue where task after the Reboot task might fail with the host respond timeout error.
Task Fails with Connection attempt failure.
In the Agent log we can see following error message:
"CTCPSocketIPC::Connect Failed to connect 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."
In the console following error would appear for the Task Status:
"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."
Following with status code 10060.
Currently under investigation.
Possibly timing issue, when server is trying to re-use the socket, which was not yet fully closed.
It's recommended to apply following TCP tweak on the Deployment Server machine to improve connectivity stability.
It can be done either manually - or by creating Run Script task - and execute it on Deployment server.
Contents of the task:
REM Tweak the TCP Parameters on Deployment Server.
http://technet.microsoft.com/en-us/library/cc938217.aspx (for TcpTimedWaitDelay) - Default value is 240 seconds, by decreasing it - we allow server to close connection faster, so sockets would be available to be re-used. Can be tweaked from 240 to 60 seconds. Depends on the job lenght and environment.