Open Deploy Failures

W2K Environment
Teamsite 5.5.2
Opendeploy 5.5.1

Does anybody have a good insight to troubleshooting Opendeploy failures. We have workflow that, once approved, simply fires off the opendeploy agent that sends the approved files out to production server (pretty standard stuff). However, a few times a week, those tasks get stuck in the Teamsite task queue with a status of 'Retry_Deployment'. I can't find any error messages in any of the opendeploy logs. The only message I can find is the teamsite iwevents.log file that basically states the task number and 'retry_deployment' for the status.

Is there a log file that shows why these deployments are failing? I can simply go to the task list and take ownership of the task and attempt to retry the deployment, which usually works. But, I have no explanation of why this is happening.

Find more posts tagged with

Comments

Bowker

Do you have trouble with the services just going away or hanging (not responding)? We had this trouble and found a JRE update fixed about 95% of those issues. We find now that if you abort a deployment it will kill (sometimes) one or two of the receivers. We have a process running on the box to restart it if the server dies or stops responding.

As to the logs for your issue, I'm assuimg you have looked at OpendeployNG/logs and don't see anything on either the receiver or server side.

Dan

Migrateduser

Usually the Opendeploy services don't stop or hang. Most of the time they will continue to run and we simply have to retry the deployments and they'll work. What we're confused about is why they failed in the first place. I would think that if a file might be locked or some other reason that the file can't be deployed, there would be an error message in some log file that would state the reason why.

I've looked in all of the teamsite logs as well as the opendeploy logs on both the sender and receiver.

Adam Stoller

Do you ever have workflows running your deployment script concurrently? If so - you are likely to run into problems with trying to run the same deployment before the first one has finished. To get around this, you need to use the '-inst' flag for iwodstart (check the manuals and/or '-h' output for details).

--fish
(Interwoven Senior Technical Consultant)