OpenDeploy Status Unknown. FAILED. Locating OpenDeploy service. Got OpenDeploy service >>>&

Hey Team,.

There has been errors coming during a workflow execution at some stages of OD. We revisited the odbase, odreceiver and odnodes cofig files, there has been no much substantial info available in the error logs also. can somebody provide thoughts to fix this issue?. I have also attached the workflow diagram.

Error is:-

OpenDeploy Status Unknown. FAILED. Locating OpenDeploy service. Got OpenDeploy service >>>>>-- Start deployment ReverseDeployment. iwodstart running in default synchronous mode. Need to wait for deployment to complete. ***ERROR - Starting deployment. Reason from server: DEPLOYMENT_NOT_QUEUED Details : Deployment ReverseDeployment is already running. Request to start it now cannot be done. Rejecting request. [GLOBAL\_balasb: 10/6/14 4:49:04 AM ]

Thanks and regards,

Adi

Find more posts tagged with

Comments

Adam Stoller

"DEPLOYMENT_NOT_QUEUED" means that a deployment was attempted to be initiated that is identical to a deployment already in progress (running or stuck) - most likely both were run without a -inst <unique-id> parameter.

Generally speaking, best practice for deployments initiated from a workflow is to use the jobid as the value for the -inst flag - there may be some situations where you truly don't want the same deployment process to be run multiple times concurrently - but I think those are rare, and usually dealt with better by using server configuration settings that, for example, serialize transactional deployments going to the same target area (you can read about that in the manuals - start with, I believe, pathRegistryChecking (or something like that - not looking at the manual right now)

You would need to determine all the parameters being used to kick off your deployments (sounds like there is no instance flag / parameter being provided) and/or why OD thinks that the deployment is already running and so not queuing it --or-- you can enable deployment queuing on your base server (though I think that's of dubious value).

adi_adi

Hi Adam,

There is a claim that this workflow was working good earlier and it seems it has stopped working recently. As I mentioned earlier we revisited the OD config files to understand if there is something to correct. I believe there has been a recent change which must have caused this issue. I understand you have tried to explain the reason for issue but I'm trying to get a solution still by correcting the same workflow. I have attached the workflow diagram, please take a look at it. Thanks for advising and providing your time.

ghoti wrote:
"DEPLOYMENT_NOT_QUEUED" means that a deployment was attempted to be initiated that is identical to a deployment already in progress (running or stuck) - most likely both were run without a -inst <unique-id> parameter.

Generally speaking, best practice for deployments initiated from a workflow is to use the jobid as the value for the -inst flag - there may be some situations where you truly don't want the same deployment process to be run multiple times concurrently - but I think those are rare, and usually dealt with better by using server configuration settings that, for example, serialize transactional deployments going to the same target area (you can read about that in the manuals - start with, I believe, pathRegistryChecking (or something like that - not looking at the manual right now)

You would need to determine all the parameters being used to kick off your deployments (sounds like there is no instance flag / parameter being provided) and/or why OD thinks that the deployment is already running and so not queuing it --or-- you can enable deployment queuing on your base server (though I think that's of dubious value).

Hi Adam,Thereis

Adam Stoller

There's nothing in the diagram that's going to explain why something that used to work stopped working. You'll have to dig through the logs and get a full understanding of what the actual deployment process is in order to debug (and hopefully fix) the situation.

adi_adi

Hi Adam,

I was in a process to check the logs as well as the workflow diagram. We involved the dev team who had build this workflow, its updated that the workflow is not fully functional. so this workflow will be going to the scope of dev team again for rebuilt process. ANyways thanks for your precious time in going through this.

I have seen a similar error with another workflow:- the error is
OpenDeploy Status Unknown. FAILED. Locating OpenDeploy service. Got OpenDeploy service >>>>>-- Start deployment WebDeploy. iwodstart running in default synchronous mode. Need to wait for deployment to complete. ***ERROR - Starting deployment. Reason from server: DEPLOY_CONFIG_FILE Details : Got null definitions hashmap.

Suppose if you have any insight on this, please advise. I have checked the error logs but there wa nothing much available for analysis.

Thanks and regards,

Adi

ghoti wrote:
There's nothing in the diagram that's going to explain why something that used to work stopped working. You'll have to dig through the logs and get a full understanding of what the actual deployment process is in order to debug (and hopefully fix) the situation.

adi_adi

Hi Adam,
I was in a process to check the logs as well as the workflow diagram. We involved the dev team who had build this workflow, its updated that the workflow is not fully functional. so this workflow will be going to the scope of dev team again for rebuilt process. ANyways thanks for your precious time in going through this.
I have seen a similar error with another workflow:- the error is OpenDeploy Status Unknown. FAILED. Locating OpenDeploy service. Got OpenDeploy service >>>>>-- Start deployment WebDeploy. iwodstart running in default synchronous mode. Need to wait for deployment to complete. ***ERROR - Starting deployment. Reason from server: DEPLOY_CONFIG_FILE Details : Got null definitions hashmap.

Suppose if you have any insight on this, please advise. I have checked the error logs but there wa nothing much available for analysis.

Thanks and regards,
Adi

OrdersLastCurrentNextMonth.rptdesign

Adam Stoller

"DEPLOY_CONFIG_FILE Details : Got null definitions hashmap" gerally means that the deployment configuration is expecting parameters to be passed in and one or more of those parameters are not being passed to it.

Again, you need to look at log files, the deployment configuration file in question, and the method in which the deployment is being kicked in.

If you look at the log files, you should be able to identify the deployment configuration and, depending on which log file you look at, the parameters being passed to it (possibly).

If you look at the deployment configuration file, you should be able to identify all the parameters that it is expecting (anything that begins with a '$')

Note that parameter names are case-sensitive ("FOO" and "foo" are not the same thing) - and they have to be spelled identically (typos won't match up)

Assuming you find the disconnect, then it's a question of whether it's something you can easily fix (e.g.: typos or forgotten parameters specified somewhere) or you have to dig into the method used to invoke the deployment to figure out why it isn't passing something you expect it to.

adi_adi

Adam,

Thanks a lot for your time. This workflow has been sent back to Dev for debug process. There are no other issues as such in the server.

Thanks and regards,

Adi