DeployNRun not waiting for deployment to fully finish

I have the following defined in my OD config.

[html]

<script cmd="/opt/data/load_data.sh $deployName^" as="root"/>

[/html]
although the script does run, it is not waiting for the OD to actually finish.. it seems that the bea bulkloader that is being called from within the sh file is seeing .iwold files, which would indicate that OD has not actually "finished".. this is on Linux using od6.2 with the latest patches.

anyone else running into an issue where DNR does not seem to want to actually follow the "when" attribute?

Find more posts tagged with

Comments

Adam Stoller

I have the following defined in my OD config.

[html]

<script cmd="/opt/data/load_data.sh $deployName^" as="root"/>

[/html]
although the script does run, it is not waiting for the OD to actually finish.. it seems that the bea bulkloader that is being called from within the sh file is seeing .iwold files, which would indicate that OD has not actually "finished".. this is on Linux using od6.2 with the latest patches.

anyone else running into an issue where DNR does not seem to want to actually follow the "when" attribute?

You might want to try specifying an explicit triggerPoint attribute for the dnrDeployment directive - look in the manuals for more information about triggerPoint

Migrateduser

You might want to try specifying an explicit triggerPoint attribute for the dnrDeployment directive - look in the manuals for more information about triggerPoint

I tried that this AM, and it had no positive effect..

if I add triggerPoint ="transfer" its "during the transfer of content", and does me no good.

if I add triggerPoint ="disconnect" its does NOT run the DNR at all (no errors, but its like the DNR doesnt exist).

and if I leave triggerPoint out, its like its in set to "transfer" which is no good..

Migrateduser

also.. the DNR seems to say its set properly in the OD logs.. though it seems it does not "listen"

when triggerPoint is set to disconnect:
[html]deployment=.publish_prod5515publish_prod.portal.portalserver
file_list=/Interwoven/TeamSite/tmp/filelist.5493.5515.20080611-125201.txt
area=/iwmnt/default/main/Content/WORKAREA/production
local_directory=.
source_include_pattern=".*\.html$"
source_include_pattern=".*\.properties$"
svr_try_interval=30
do_deletes
svr_try_count=3
date_different
ignore_acls
remote_directory=/opt/content/Content
;
deploy_run_script=/opt/content/load_cm_data.sh
async=no
where=
as=root
when=server_after_disconnect on_success
;
;[/html]

when triggerpoint is set to "transfer":

[html]deployment=.publish_prod5599publish_prod.portal.portalserver
file_list=/Interwoven/TeamSite/tmp/filelist.5577.5599.20080611-130333.txt
area=/iwmnt/default/main/Content/WORKAREA/production
local_directory=.
source_include_pattern=".*\.html$"
source_include_pattern=".*\.properties$"
svr_try_interval=30
do_deletes
svr_try_count=3
date_different
ignore_acls
remote_directory=/opt/content/Content
;
deploy_run_script=/opt/content/load_cm_data.sh
async=no
where=
as=root
when=server_after_deploy on_success
;
;[/html]

Adam Stoller

I tried that this AM, and it had no positive effect..

if I add triggerPoint ="transfer" its "during the transfer of content", and does me no good.

if I add triggerPoint ="disconnect" its does NOT run the DNR at all (no errors, but its like the DNR doesnt exist).

and if I leave triggerPoint out, its like its in set to "transfer" which is no good..

Instead of "after" "disconnect" - try "before" "disconnect" and see if that works any better.

Migrateduser

Instead of "after" "disconnect" - try "before" "disconnect" and see if that works any better.

that seems to work better.. I am going to let it get used for a couple of days to see what kind of feedback I get.

Thanks!

Migrateduser

it seems there were 2 issues.. the cleanup was also not happening until after the DNR

setting the transientDirectory="/opt/tmp" (or some other tmp directory) in the odrcvr.xml listenerProperties keeps the junk file out of the root and prevents this from being an issue now as well..