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

General DNR question

blacke

Hi,

I am new to OD and have been trying to deploy a script and run it after the transfer on the target, but it always fails, so I tried to create two execDeployment tasks, one to deploy the scripts, then the second to run the script before transfering files, and then transfer the files, and run a second script. It looks like the 'when' and 'triggerPoint' means after both execDeployment tasks have completed. Is this the case? Do I really have to have two seperate deployments I need to run to do something like this?

Thanks in advance,
Eric

Find more posts tagged with

Comments

Migrateduser

No, you shouldn't need to. Please post your config file and maybe one of us could lend some advice.

By the way, is your deployment failing or is the DNR failing?

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9

IuK_Cockpit.mashconfig.txt

blacke

Here's my config. The deployment fails. So it should be ok to deploy the same file after it is deployed(not doing that here in this config, but I was and it was always failing).

Thanks,
Eric

<?xml version="1.0" encoding="ISO-8859-1" ?>
<deploymentConfiguration >
<localNode host="bsitw03s" timeout="300" blockMaxWaitTime="1800" blockCheckInterval="30" />
<replicationFarmSet >
<replicationFarm name="pirs_reports" quorum="" >
<nodeRef useNode="bsitw03s" />
</replicationFarm>
</replicationFarmSet>

<definition name="scripts" >
<source >
<iwStore name="" >
<remoteDiff area="/iwmnt/default/main/Content/PIRS/WORKAREA/work/scripts" name="scripts" >
<pathSpecification >
<path name="." />
</pathSpecification>
</remoteDiff>
</iwStore>
</source>
<target useReplicationFarm="" >
<filters >
<excludePath subPath="en_US/Repositories" />
</filters>
<comparisonRules dateDifferent="no" revert="no" ignoreAcls="yes" ignoreModes="no"
ignoreUser="no" ignoreGroup="no" checksumCompare="no" />
<transferRules doDeletes="no" dontDo="no" preserveAcls="no" followLinks="no"
svrTryCount="" svrTryInterval="" svrTryDisableOverwrite="no"
rmReadOnly="no" compression="no" compressionLevel=""
applySourceFileTime="yes" checksumVerify="no" byteIncremental="no" />
<permissionRules amask="" omask="" directory="775" file="775" group="" user="" changeAccess="" setAccess="" />
<targetFilesystem area="/usr1/opendeploy/OpenDeployNG/tmp/nas/pirs_reports/scripts" />
<replicationFarmLink >
<internal name="pirs_reports" />
</replicationFarmLink>
</target>
</definition>

<definition name="accounts" >
<source >
<iwStore name="" >
<remoteDiff area="/iwmnt/default/main/Content/PIRS/WORKAREA/work/accounts/zipped" name="sorted" >
<pathSpecification >
<path name="." />
</pathSpecification>
</remoteDiff>
</iwStore>
</source>
<target useReplicationFarm="" >
<filters >
<excludePath subPath="en_US/Repositories" />
</filters>
<comparisonRules dateDifferent="no" revert="no" ignoreAcls="yes" ignoreModes="no"
ignoreUser="no" ignoreGroup="no" checksumCompare="no" />
<transferRules doDeletes="no" dontDo="no" preserveAcls="no" followLinks="no"
svrTryCount="" svrTryInterval="" svrTryDisableOverwrite="no"
rmReadOnly="no" compression="no" compressionLevel=""
applySourceFileTime="yes" checksumVerify="no" byteIncremental="no" />
<permissionRules amask="" omask="" directory="775" file="775" group="" user="" changeAccess="" setAccess="" />
<targetFilesystem area="/usr1/opendeploy/OpenDeployNG/tmp/nas/pirs_reports/accounts_zipped" />
<replicationFarmLink >
<internal name="pirs_reports" />
</replicationFarmLink>
</target>
</definition>

<definition name="provider" >
<source >
<iwStore name="" >
<remoteDiff area="/iwmnt/default/main/Content/PIRS/WORKAREA/work/provider/zipped" name="sorted" >
<pathSpecification >
<path name="." />
</pathSpecification>
</remoteDiff>
</iwStore>
</source>
<target useReplicationFarm="" >
<filters >
<excludePath subPath="en_US/Repositories" />
</filters>
<comparisonRules dateDifferent="no" revert="no" ignoreAcls="yes" ignoreModes="no"
ignoreUser="no" ignoreGroup="no" checksumCompare="no" />
<transferRules doDeletes="no" dontDo="no" preserveAcls="no" followLinks="no"
svrTryCount="" svrTryInterval="" svrTryDisableOverwrite="no"
rmReadOnly="no" compression="no" compressionLevel=""
applySourceFileTime="yes" checksumVerify="no" byteIncremental="no" />
<permissionRules amask="" omask="" directory="775" file="775" group="" user="" changeAccess="" setAccess="" />
<targetFilesystem area="/usr1/opendeploy/OpenDeployNG/tmp/nas/pirs_reports/provider_zipped" />
<replicationFarmLink >
<internal name="pirs_reports" />
</replicationFarmLink>
</target>
</definition>

<deployment transactional="yes" >

<execDeploymentTask useDefinition="scripts" />

<execDeploymentTask useDefinition="accounts" >
<deployNRun >
<dnrDeployment location="target" when="after" triggerPoint="connect" state="success">
<script cmd="/usr/bin/bash /usr1/opendeploy/OpenDeployNG/tmp/nas/pirs_reports/scripts/accounts_initial_clean.sh >> /tmp/IRS_reports_script.log" as="" where="" async="no" />
</dnrDeployment>
</deployNRun>

<deployNRun >
<dnrDeployment location="target" when="after" triggerPoint="transfer" state="success">
<script cmd="/usr/bin/bash /usr1/opendeploy/OpenDeployNG/tmp/nas/pirs_reports/scripts/accounts_install_and_clean.sh >> /mp/PIRS_reports_account.log" as="" where="" async="no" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>

</deployment>
</deploymentConfiguration>

blacke

Sorry, this was a question:
So it should be ok to deploy the same file after it is deployed(not doing that here in this config, but I was and it was always failing)?

Eric

blacke

Well, I got it working by changing the 'after connect' to 'after transfer', but I have to test it more to make sure it is reliable.

Thanks.

Migrateduser

I haven't had a chance to look at it too closely but you have a typo in your second DNR (and your third but it's commented out, anyway) /mp as opposed to /tmp.

Anyway, I also noticed you're using the "connect" triggerPoint. Is there a specific reason you're using this? I wonder if you might have more luck using "transfer" with "success", etc.

Dave

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9

Herman

When I run a natch file and echo some message to OD,
Let OD system log these messages in the deployment log file.
Any function OD supports?

jkm

I am not able to understand what do you mean by natch file , echo message to OD log file ..
Are you talking about DNR script ?
How are you logging messages by urself to OD log ?
Version and platform of OD + TS

please provide more info ...

cheers!!

Adam Stoller

I believe "natch" is "batch" where the finger just happened to miss the 'b' and hit the 'n' to its right ;-)

I think it's safe to assume that DNR scripts are what is being talked about based on the subject if nothing else.

To answer the question though, I believe the only thing that OD currently logs from DNR scripts is a failure message if the string that was echo'd contains the XML snippet to indicate a failed [custom-defined] process - I don't believe it captures any other output from DNR scripts and logs them (though I do think I recall there being a feature request regarding something like this)

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

Herman

Yes and sorry for my miss,
I am talking about Batch File and DNR.
I use win2003 and OD 6.0.2 SP1.
I can echo response code='-2' to let OD know this is fail,
but I want to log what happen let this deploy fail,
any function cna i use to response some message to OD system to log in the deploy log file?

Adam Stoller

I think the only thing you can do is have your batch script (or whatever you use for writing the DNR script) log information to its own logfile - and whomever is administering / maintaining the system needs to know this so that they'll know where to look if something fails (or where to check if things succeeded?)

Beyond that - you can contact Support to file (or get added to?) a feature request for the ability to pass back information through the OD logs (in-memory and/or written-out) from DNR scripts.

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

jkm

DNR is behaving in a cryptic manner for me.

I am calling four DNR scripts in .
First DNR calls datadeploy to populate the database entries.
Second takes a database dump
third run a parser on set of files
fourth zip up the content tar for deployment on other environments.

In datadeploy sometimes it prints the OD deployment messages on command line and some times it doesnt. ( Message from OD when we run iwodcmd via command line). Why is this happening? I can redirect these message using log redirection but I want to know why its behaving differently by itself.

DNR scripts runs in the order they are defined but seems to be my fourth dnr runs before the content deployment and its not able to find deployed files to zip and fails Smiley Sad

I am using async="no". Any pointers why is this happening?

Adam Stoller

DNR is behaving in a cryptic manner for me.

I am calling four DNR scripts in .
First DNR calls datadeploy to populate the database entries.
Second takes a database dump
third run a parser on set of files
fourth zip up the content tar for deployment on other environments.

In datadeploy sometimes it prints the OD deployment messages on command line and some times it doesnt. ( Message from OD when we run iwodcmd via command line). Why is this happening? I can redirect these message using log redirection but I want to know why its behaving differently by itself.

DNR scripts runs in the order they are defined but seems to be my fourth dnr runs before the content deployment and its not able to find deployed files to zip and fails
I am using async="no". Any pointers why is this happening?

Please [re-]post the deployment config file - and also explain why you need four scripts insteaad of one script that performs four functions.

My guess is that you're seeing STDERR output on the command line from some of these scripts - but that's just a guess.

jkm

Hi Adams,
Thanks for your reply. I need four different DNR scripts because all the four tasks needs to be executed with different user id and from different locations for example datadeploy needs to be called as iwod user id and dump of database runs with oracle user id and content dump runs with support user id.

In first DNR datadeply is getting completed without any errors. So I dont think these are STDERR error messages.

Any other clues why its happening. I will post my config file in sometime

jkm

Here is the OD Config file.

Adam Stoller

I understand (now) why you need the four DNRs.
You may need to use the triggerpoint attributed for the DNRs to force the 4th one to run when you want it to run.

No idea about the messages being sent to the console, sorry.