OD deployment failing

We have two workareas in US branch :-

//USCEDWS04/default/main/IM/PUBLIC_SITE/US/WORKAREA/dev_iwov/

//USCEDWS04/default/main/IM/PUBLIC_SITE/US/WORKAREA/content/

when we deploy from content WA to our staging server,it is successful and completed in a minute or so but when i try deploying from dev_iwov ,it goes on
for 3-4 hours and ultimately it is failing ,for one folder the following message goes on for many lines

"reason missing-in-src"

can we do selective deployment for just one particular folder as per reqs since i really dont need the folder to deploy which is showing above msg

looking forward for some guidance from experts

regards,
mav

Find more posts tagged with

Comments

Natasha

We have two workareas in US branch :-

//USCEDWS04/default/main/IM/PUBLIC_SITE/US/WORKAREA/dev_iwov/

//USCEDWS04/default/main/IM/PUBLIC_SITE/US/WORKAREA/content/

when we deploy from content WA to our staging server,it is successful and completed in a minute or so but when i try deploying from dev_iwov ,it goes on
for 3-4 hours and ultimately it is failing ,for one folder the following message goes on for many lines

"reason missing-in-src"

can we do selective deployment for just one particular folder as per reqs since i really dont need the folder to deploy which is showing above msg

looking forward for some guidance from experts

regards,
mav

If you need any help regarding the deployment failure, the please post your sender and receiver's logs.
For selective deployment, you can make use of includePath filters. Be careful if you have doDeletes on in your deployment.
Alternatively, you can have a filelist based deployment which will deploy whatever you have specified in filelist.

Thanks,
Natasha.

maverick83

thanks for your prompt reply ,i just read on include filter and dodelete options after ur reply ,can u pls confirm if what i conclude is correct :-
[php]

-
-
-

-
// newly added by me

// need to change it to "no"

[/php]

if i do like this then only content of x folder will go to target location and i think i need to change dodelete to "no" as per info given on page 120 on pdf

"If the filter exists only on the source side, OpenDeploy ignores those excluded
source-side files and cannot deploy them. If the doDeletes feature is enabled, those
excluded source-side files that are also present on the target-side will be deleted."

i am unable to attach log file due to size limitations

looking forward for some guidance from experts

regards,
mav

Natasha

You can probably run a simulated deployment in order to check what files will get deleted if you enable this option.
Whatever is given in the manuals is for excludeFilter so you will be better off testing it yourself and then make changes in the OD conf file.
Also, for the log file, you can just post the error strings which you are getting in sender and receiver logs.

Firenze

Can you show your deployment legs?
Do you have transactional deployments on?
Is there any overlap on the directories across legs?

maverick83

Hi

Thanks for your response ,i tried running the deployment with DoDelete="no" and it got completed but it didnt really update anything ,below given are some log
string on receiver side

[php]
LIB: (3) id=m162 2009-06-03 08:02:43 delete .\images\products\360view\printer_portable_PB2\360view_ptr_pbl_pb2a_22.jpg SKIPPED
LIB: (3) id=m162 2009-06-03 08:02:43 directive[reason missing-in-src]
LIB: (3) id=m162 2009-06-03 08:02:43 delete .\images\products\360view\printer_portable_PB2\360view_ptr_pbl_pb2a_23.jpg SKIPPED
LIB: (3) id=m162 2009-06-03 08:02:43 directive[reason missing-in-src]
LIB: (3) id=m162 2009-06-03 08:02:43 delete .\images\products\360view\printer_portable_PB2\360view_ptr_pbl_pb2a_24.jpg SKIPPED
LIB: (3) id=m162 2009-06-03 08:02:43 directive[reason missing-in-src]
LIB: (3) id=m162 2009-06-03 08:02:43 delete .\images\products\360view\printer_portable_PB2\360view_ptr_pbl_pb2a_25.jpg SKIPPED
LIB: (3) id=m162 2009-06-03 08:02:43 directive[reason missing-in-src]
LIB: (3) id=m162 2009-06-03 08:02:43 deletedir .\images\products\360view\printer_portable_PB2 SKIPPED
LIB: (3) id=m162 2009-06-03 08:02:43 directive[reason missing-in-src]
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 After PRECOMMIT res=0
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 exiting dotask
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 entering awaiting-commit
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 still waiting for 0
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 exiting awaiting-commit
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 entering commit
LIB: id=m162 2009-06-03 08:02:43 FailedCommit 0.
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Thread-505 After COMMIT res=0
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Is OD-DD Deployment null
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 MultiTier is = false
ENG: 2009-06-03 08:02:43 CDT GMT-05:00 Failed Commit false
LIB: id=m162 2009-06-03 08:02:43 FailedCommit 0.
LIB: (3) id=m162 2009-06-03 08:02:43 FailedCommitFlag = 0
LIB: (3) id=m162 2009-06-03 08:02:43 FailedCommitFromEngine = 0
LIB: id=m162 2009-06-03 08:02:43
Directories deployed : 0 Files deployed : 0 Links deployed : 0
Directories failed : 0 Files failed : 0 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 After COMMIT1 res=0
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 exiting commit
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 entering awaiting-cleanup
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 still waiting for 0
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 exiting awaiting-cleanup
ENG: 2009-06-03 08:03:08 CDT GMT-05:00 Thread-505 entering cleanup
LIB: id=m162 2009-06-03 08:03:08 FailedCommit 0.
LIB: (3) id=m162 2009-06-03 08:03:08 Commit-sweep: cleaning up iwnew/iwold backups
LIB: id=m162 2009-06-03 08:03:08 File Content transferred: 0 bytes
LIB: id=m162 2009-06-03 08:03:08 [Wed Jun 03 08:03:08 2009] Deployment COMPLETED

ENG: 2009-06-03 08:03:09 CDT GMT-05:00 Thread-505 After CLEANUP res=1
ENG: 2009-06-03 08:03:09 CDT GMT-05:00 Thread-505 exiting cleanup
ENG: 2009-06-03 08:03:09 CDT GMT-05:00 Thread-505 entering task-done
ENG: 2009-06-03 08:03:09 CDT GMT-05:00 Thread-505 still waiting for 0

[/php]

If i do the deployment with dodelete="yes" then it is failing after running for nearly 3 hours

yes,our deployment is transcational

yeh ,directories are of same strcuture ,dev_iwov files and folders date are bit below lower than content

if i try to do selective deployment using include within path specifications(more than one include) ,but both files are going to same target location ,can we specify different target location for different source files ,it seems its not possible ,is there some hack available ?

any pointers regarding this issue ?

regards.
mav

Firenze

1. Turn off transactional deployments to make sure deployment runs clean.
2. Can you show the list of deployment legs to see how many legs we are dealing with?
3. More on the directories, are the directories of the legs overllapping if so, this is likely the cause of the failure since the transaction is trying to commit directories and files that don't exist yet. So, you will need to use filters to handle this. However, sometimes the very first full deployment may need to be done with transaction="no" and then set it back to "yes" .
4. You can do source based target overrides in opendeploy although I don't know if that will solve your problem if it is caused by #3
5. other options may be to create more deployment legs to reduce the overlap.

Adam Stoller

1. Turn off transactional deployments to make sure deployment runs clean.
2. Can you show the list of deployment legs to see how many legs we are dealing with?
3. More on the directories, are the directories of the legs overllapping if so, this is likely the cause of the failure since the transaction is trying to commit directories and files that don't exist yet. So, you will need to use filters to handle this. However, sometimes the very first full deployment may need to be done with transaction="no" and then set it back to "yes" .
4. You can do source based target overrides in opendeploy although I don't know if that will solve your problem if it is caused by #3
5. other options may be to create more deployment legs to reduce the overlap.

Re: 3 - with the more recent versions of OD you can enable pathRegistryChecking on the receiver to have it take care of serializing the reception of multiple transactional deployments that are targeted to the same [base] directory area (read the manuals for more information, also search Support KBs as I recall there is an additional setting that is desired that isn't / wasn't documented well in the manuals)

Adam Stoller

Hi

Thanks for your response ,i tried running the deployment with DoDelete="no" and it got completed but it didnt really update anything ,below given are some log
string on receiver side
...

If i do the deployment with dodelete="yes" then it is failing after running for nearly 3 hours

yes,our deployment is transcational

It sounds like there is an issue with actually performing the deletions on the target server - either because of the aforementioned issue of having multiple transactional deployments attempt to modify the same target [base] directories - or because some process on the receiving side is preventing [some of] those files from getting deleted, and OpenDeploy keeps trying multiple times with space in between.

maverick83

Hi

I have noticed below mesasge in sender log even if deployment shows it is successful ,the receiver log shows similar msg as above ,

[php]
odcasts\webinars\2007-04-12\flash\ProductionInfo.xml [reason missing-in-src] --
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 exiting dotask
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 entering awaiting-rollback
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 still waiting for 0
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 exiting awaiting-rollback
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 entering rollback
LIB 00024: 2009-06-03 11:01:06 ERROR: Could not send phase start message.
LIB: 2009-06-03 11:01:06 Receiver-ERROR: .
LIB: 2009-06-03 11:01:06 ERROR: Failed to deploy local_directory[.] of area[Y:\default\main\IM\PUBLIC_SITE\US\WORKAREA\dev_iwov]
LIB: 2009-06-03 11:01:06 ERROR: Failed 1 of 1 local_directories
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 After ROLLBACK, res=-1
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 exiting rollback
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 entering awaiting-cleanup
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 still waiting for 0
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 previousPhaseStr:rollback
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 currentPhaseStr:awaiting-cleanup
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 exiting awaiting-cleanup
ENG: 2009-06-03 11:01:06 CDT GMT-05:00 Thread-385 entering cleanup
LIB 00019: 2009-06-03 11:01:07 ERROR: Could not read content size from remote.
LIB 00022: 2009-06-03 11:01:07 ERROR: Could not read server status, client OK.
LIB: 2009-06-03 11:01:07 [Wed Jun 03 11:01:07 2009] opendeploy 20090603.7352.2 NT AUTHORITY\SYSTEM COMPLETED Y:\default\main\IM\PUBLIC_SITE\US\WORKAREA\dev_iwov .IM~PUBLIC_SITE~US~deviwov~to~staging2.STAG-TS-DEPLOY.im-staging-s265024ch3sw03-web USCEDWS04 64.14.226.103
LIB: 2009-06-03 11:01:07 [Wed Jun 03 11:01:07 2009] 20090603.7352.2 STATS DEPLOYMENT Y:\default\main\IM\PUBLIC_SITE\US\WORKAREA\dev_iwov -- .IM~PUBLIC_SITE~US~deviwov~to~staging2.STAG-TS-DEPLOY.im-staging-s265024ch3sw03-web OK
LIB: 2009-06-03 11:01:07 File Content transferred: 0 bytes
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 After CLEANUP, res=1
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 exiting cleanup
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 entering task-failed
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 still waiting for 0
LIB: 2009-06-03 11:01:07 LOGFILE=[E:\Interwoven\OpenDeployNG\log\staging\src.IM~PUBLIC_SITE~US~deviwov~to~staging2.STAG-TS-DEPLOY.IM-Production-USCEDWS04-TeamSite.to.IM-Staging-S265024CH3SW03-Web.log]
LIB: 2009-06-03 11:01:07 Locale=[English_UnitedStates.MS1252@Binary]
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 PostDisConnect Dnr still waiting for 0
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 Deleting the internal config file = E:\Interwoven\OpenDeployNG\db\.IM~PUBLIC_SITE~US~deviwov~to~staging2.STAG-TS-DEPLOY.im-staging-s265024ch3sw03-web
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Published leg event depUuid=[d7ea5370-5044-11de-9b9a-8a582d4f682f] legLabel=[IM-Staging-S265024CH3SW03-Web.STAG-TS-DEPLOY] nextUuid=[null] nextDep=[null]
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 Job ID=m164 Deployment leg=IM-Staging-S265024CH3SW03-Web.STAG-TS-DEPLOY Elapsed Time=8119146 ms <<<
ENG: 2009-06-03 11:01:07 CDT GMT-05:00 Thread-385 End logfile [E:\Interwoven\OpenDeployNG\log\staging\src.IM~PUBLIC_SITE~US~deviwov~to~staging2.STAG-TS-DEPLOY.IM-Production-USCEDWS04-TeamSite.to.IM-Staging-S265024CH3SW03-Web.log]

[/php]

what exactly is meant by "deployment legs "? ,i am doing deployment from one WA to a staging server

i tried with transactional="no" ,it finished in 1 minute but didnt really changed anything ,any idea why certain directories are not getting updated and what exactly can be the issue ,thanks

regards,
mav

Adam Stoller

Hi

I have noticed below mesasge in sender log even if deployment shows it is successful ,the receiver log shows similar msg as above ,
...
what exactly is meant by "deployment legs "? ,i am doing deployment from one WA to a staging server

i tried with transactional="no" ,it finished in 1 minute but didnt really changed anything ,any idea why certain directories are not getting updated and what exactly can be the issue ,thanks

regards,
mav

I suggest you read the manuals and/or take training - things like "deployment legs" and "transactional" and how the latter affects success/failure distinctions is all pretty basic stuff in terms of OpenDeploy.

maverick83

the issue got solved ,thanks for all ur guidance

closing the thread

regards,
mav