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

some issues calling a DNR script to deploy content to two servers

Richu

Hi All,
I have the below issue:
In my open deploy config file(Script1), I am deploying some files on success of which I am calling a DNR script (after transfer on success)which is again calling another script(say script2). Now Script2 is deploying the files to a replication farm with two servers. When I run script1, it gives an error: DNR Script is already running, execution rejected.
I then removed one server from the replication farm and run the script1, it was success.

Hope you got the flow?
PFA the related files.

Is there any way where in I can check the status of the script whether it is already running or not?
Any kind of help is appreciated.

Thanks,
Richa

Find more posts tagged with

Comments

Adam Stoller

I didn't look at the files that were attached - but let me ask a question for clarification purposes:

Is the deployment configuration file that is being used for the initial deployment also being used for the "nested" deployment?

Or - are there multiple instances of the initial deployment running at the same time, each using the same configuration for the "nested" deployment?

If so (in either case) - you simply need to make sure you pass a unique instance string for the nested deployment (e.g.:

iwodcmd start config -inst unique-string

) and that should do the trick.

If you are doing transactional deployments - you should probably look into the receiver-side queuing options too.

Richu

Thanks for your reply.

I tried the steps that you gave but no success. I am getting some error codes like 256, 512 in logs. I dont have any idea on these numbers.

In our case we have one initial deployment script which is calling another script.There are multiple instances of the second deployment running at the same time.

Is there any way wherein we can check whether any open deploy instance is running or not?
Is there any interwoven or perl command to check that?

Thanks,
Richa

Adam Stoller

Thanks for your reply.

I tried the steps that you gave but no success. I am getting some error codes like 256, 512 in logs. I dont have any idea on these numbers.

In our case we have one initial deployment script which is calling another script.There are multiple instances of the second deployment running at the same time.

Is there any way wherein we can check whether any open deploy instance is running or not?
Is there any interwoven or perl command to check that?

Thanks,
Richa

I don't really know what you're doing or what you're seeing - codes like 256 and 512 are indications that the exit status needs to be shifted by 8 (256 >> 8 = 1, 512 >> 8 = 2)

You can run commands like

iwodcmd serverstatus

to get a list of the running deployments on the base server, though whether that information will really help you I have no idea. My guess is that you are either executing something incorrectly or have something incorrectly configured - but that's as far as I'm willing to go for free.

DareDevil

The problem was not resolved even after using the instance with unique string 'iwodcmd start config -inst unique-string'' .Even the attribute 'pendSessions="yes" was added in listener properties tag in odrcvr.xml . While deploying the files to two servers , deployment happens to one server and deployment fails for other server.The below error was logged in deployment instance of failed server.

LIB: 2010-08-27 10:33:59 *** Proceed
LIB: 2010-08-27 10:33:59 *** fFailedCommitFromEngine 0
LIB: 2010-08-27 10:33:59 COMMITTING Transactional Deployment
LIB: (3) 2010-08-27 10:33:59 failed target name from receiver F:\SSS\publishedcontent\dcr\ssshome\Operations\Help Line\Manual_Operating_Procedures_Job_Aid_MH.xml
LIB: 2010-08-27 10:33:59 Receiver-ERROR: ERROR: commit-failed.
LIB: 2010-08-27 10:33:59 ERROR: Failed to deploy local_directory[.\SSSHome] of area[Y:\default\main\SSS\EDITION\ed_0037]
LIB: 2010-08-27 10:33:59 ERROR: Failed 1 of 2 local_directories

Is there any way to queue up the deployment instances in DNR?

Adam Stoller

The problem was not resolved even after using the instance with unique string 'iwodcmd start config -inst unique-string'' .Even the attribute 'pendSessions="yes" was added in listener properties tag in odrcvr.xml . While deploying the files to two servers , deployment happens to one server and deployment fails for other server.The below error was logged in deployment instance of failed server.

LIB: 2010-08-27 10:33:59 *** Proceed
LIB: 2010-08-27 10:33:59 *** fFailedCommitFromEngine 0
LIB: 2010-08-27 10:33:59 COMMITTING Transactional Deployment
LIB: (3) 2010-08-27 10:33:59 failed target name from receiver F:\SSS\publishedcontent\dcr\ssshome\Operations\Help Line\Manual_Operating_Procedures_Job_Aid_MH.xml
LIB: 2010-08-27 10:33:59 Receiver-ERROR: ERROR: commit-failed.
LIB: 2010-08-27 10:33:59 ERROR: Failed to deploy local_directory[.\SSSHome] of area[Y:\default\main\SSS\EDITION\ed_0037]
LIB: 2010-08-27 10:33:59 ERROR: Failed 1 of 2 local_directories

Is there any way to queue up the deployment instances in DNR?

You could attempt your own queuing mechanism in your DNR but I'm not convinced that is the issue.

to that server first before assuming that there's a queuing issue.

DareDevil

1. Yes , F:\ is a local drive in target machine
2.Od process owner has all the privileges.
3. The file has not been locked by other processes.

Everthing works fine , if odnodes containes a single sever.But right now in od nodes there are two servers. So deployment is successful in one server and fails in other server.

1f0d99fcb4e3b0d1636e818d7600ec11.rptdesign

Adam Stoller

1. Yes , F:\ is a local drive in target machine
2.Od process owner has all the privileges.
3. The file has not been locked by other processes.

Everthing works fine , if odnodes containes a single sever.But right now in od nodes there are two servers. So deployment is successful in one server and fails in other server.

I'm confused now - if deployments from base to receiver-A works, and deployments from base to receiver-B works - and you only have problems doing a fan-out deployment from base to both receiver-A and receiver-B - then there should be no queuing issue involved. The only way I would think that there would be a queuing issue is if multiple deployments to receiver-A and/or receiver-B are running at the same time.
If those deployments are non-transactional, it should not be an issue.
If those deployments are transactional, then you need to make sure you have receiver-side queuing enabled (not pendSessions with is source-side queuing)