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; } } }

callback (1) : OpenDeploy Status Unknown. FAILED.

SethHickel

Well this is odd. When users use a specific template to create content and push to production the file(s) actually get deployed but the job shows incomplete and having errors in the Workflow tab of TeamSite. I can look at the job in the OD UI and it shows completed.

od.log does not show anything.

Tue Mar 9 19:41:23 2010 - OpenDeploy Status Unknown. FAILED.
Tue Mar 9 19:41:23 2010 - odStatus = Completed with error
Tue Mar 9 19:41:23 2010 - callback (1) : OpenDeploy Status Unknown. FAILED.

1. Any ideas about why this might be occuring?
2. Where are the OD return codes documented?

Interwoven TeamSite 6.7.1.0
Build Number: 60750

OD Version: 6.1.1.0.0 Build 64682

Find more posts tagged with

Comments

nipper

OK, rereading the bug it is using the -inst flag,

are you running two deployments by chance ?

ISCBorisB

are you running two deployments by chance ?

From the Log:
Reason from server: DEPLOYMENT_QUEUED
Details : - There is already a deployment 'LowesComNGProductionFileListDeployAB305959 ' running.
Request to start it now cannot be done. Queuing deployment to run later.

SethHickel

We do kick off multiple deployments. We create an XML file along with the generated file and submit them from the same workflow but different calls to OD.

Ran iwodserverstatus on the TS server to look for a hung deployment. There was not one (this was today). It showed OD server as alive and zero deployments currently active. I DID NOT run this yesterday when the issue was reported to me.

Users report that this is not occuring now. No rhyme or reason to that except that we stopped all TeamSite and OpenDeploy services last night as part of our nightly iw-store backup.

Still wondering where the return codes from OD are documented.

SethHickel

ISCBorisB - are you suggesting that the callback (1) is a symptom of queuing deployments?

Since the job(s) finish successfully - meaning that the OD UI shows complete and the files are on the servers - why would we be getting this callback code? Is the situation that we are hitting some time-out from OD or our workflow and getting that code while the queue is getting executed?

This is a new thing and apparently sporadic - but - it freaks the business out because the TeamSite deployment tab show the task failed.

nipper

The only thing I can think of is that the original job hung and someone tried to restart, that error is from the restart.

Run iwodcmd start -h

I get this for OD 7.1

exit code:
0 - succeeded
1 - starting of the deployment failed
2 - deployment ran and returned a failed status
9 - deployment completed with errors

ISCBorisB

ISCBorisB - are you suggesting that the callback (1) is a symptom of queuing deployments?

Since the job(s) finish successfully - meaning that the OD UI shows complete and the files are on the servers - why would we be getting this callback code? Is the situation that we are hitting some time-out from OD or our workflow and getting that code while the queue is getting executed?

This is a new thing and apparently sporadic - but - it freaks the business out because the TeamSite deployment tab show the task failed.

No, I'm not suggesting that callback (1) is caused by or is a symptom of queuing deployments. I do not have
enough information for such conclusion. It was simply a "Yes, sure" answer to Andy's question.

If I have to guess, what you are seeing is the "False Negative". It *looks* like the WF's External (or perhaps CGI)
Task that executes Open Deploy can not properly assess certain RC and/or Stdout and defaults to "callback 1" which
presumably reports an error etc...

Take a look at what this Task is doing and especially what/how it analyzes the result of "iwodcmd start" execution.
Log out these results and callback code and see what does not jive there.