nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployment hangs in running status

adamvan

When i run a deployment that has one of the target nodes offline, the deployment will hang in stay in a "running" status. Has anyone ran into the problem? and came up with a solution? We are running OpenDeploy 6.0.1 on W2k3

Thanks

Edited by adamvan on 06/27/05 12:01 PM (server time).

Find more posts tagged with

Comments

Adam Stoller

I believe the connection is being retried several times with a pause in between - and then, if it still has failed to connect it will [finally] indicate an error, which will get propogated back up the tree.

I believe there are some configurable parameters that can be used to specify either the number of times it tries to connect or the amount of time to wait before trying to reconnect (or both) and a quorum value to specify the number of successful legs required in order to achieve "success" for the deployment as a whole. All of this information should be available in one of the OD manuals (though it's possible some of this came in 6.0.2 so, if you're using 6.0.1 you may still have some issues).

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

adamvan

thanks for the reply,

I have found the settings within the deployment to set the number of retries and delay in between each. within the logs i see the following error when it tries to deploy to a server that is offline.

ENG: 2005-06-27 15:21:52 EDT GMT-04:00 Thread-26 ***ERROR - Job ID=m5Deployment=Gold_Besthings
Base: Exceeded all 3 retries to get a connection with the target OpenDeploy host.
Failed creating socket.

The deployment has been running for 22 hours at that point and still has not completed with errors. It is still in running mode, and the mode for the server that is offline still says setting up. Sometimes it will go past setting up and said failed, but the deploy itself still says in running mode.

Adam

Adam Stoller

If you haven't already done so - this sounds like it should be a support case. They'll need your various log files, config files, etc. and will probably have to understand your network architecture sufficiently to have a hope of reproducing the problem. Once they can reproduce the problem it becomes significantly easier for engineering to debug and then evenutally provide a fix for the problem.
I'm not saying this will happen overnight - but the sooner you get the ball rolling with support - the sooner you have a chance of getting a fix for the problem.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com