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

Open Deploy Query

dip21

Hi All...

We are trying to deploy directory based deployments from two source directory from TeamSite into one target directory.
1. Docroot/COMMON
2. Docroot/QA

Those directories contains Same folder called castorFiles. But internally it contains diffrent files.
When we are deploying ,we are getting following error message in log file.

ERROR: Source directory doesn't exists /teamsite/iw-home/tmp/QA/castorFiles.iwnew LIB: 2008-12-18 04:23:26 ERROR: Failed copying dir(/teamsite/iw-home/tmp/QA/castorFiles.iwnew) to (/teamsite/iw-home/tmp/QA/castorFiles)

Hereby attached deployment config file.

Thanks in advance.

Find more posts tagged with

Comments

Adam Stoller

Hi All...

We are trying to deploy directory based deployments from two source directory from TeamSite into one target directory.
1. Docroot/COMMON
2. Docroot/QA

Those directories contains Same folder called castorFiles. But internally it contains diffrent files.
When we are deploying ,we are getting following error message in log file.

ERROR: Source directory doesn't exists /teamsite/iw-home/tmp/QA/castorFiles.iwnew LIB: 2008-12-18 04:23:26 ERROR: Failed copying dir(/teamsite/iw-home/tmp/QA/castorFiles.iwnew) to (/teamsite/iw-home/tmp/QA/castorFiles)

Hereby attached deployment config file.

Thanks in advance.

It seems possible that the problem is the fact that you are essentially doing concurrent transactional deployments and that one of the legs completes before the other and cleans up the temporary directory that the other leg is attempting to deploy into.

If the error you are currently seeing is easily repeatable - try changing transactional="yes" to "no" and see if the same problem still exists. If not, then what I suggest above is most likely the case - and then, assuming you're using [one of] the latest version of OD - you should configure the servers to do serialized transactional deployments and see if that resolves the problem when you make the deployment transactional again. (search the forums - I posted about concurrent transactional deployments before - including a reference to the manual and a KB article that provides the information for doing the serialization)

dip21

Hi Ghoti,

Thanks for your reply.
Could you please elaborate what do mean by serialized transactional deployments ?

Adam Stoller

Hi Ghoti,

Thanks for your reply.
Could you please elaborate what do mean by serialized transactional deployments ?

What do you think I mean by:

For which of those terms do you need elaboration?

dip21

Thanks for your reploy Ghoti...

I need info on how to enable serialized transactional deployments on server side.
We are using OD 6.0.2 version.

Thanks
Dip

ISCBorisB

Thanks for your reploy Ghoti...

I need info on how to enable serialized transactional deployments on server side.
We are using OD 6.0.2 version.

Thanks
Dip

The way I see it, you have couple options. The simplest and most reliable one is to configure two deployments and run them
sequentially. Problem is, you can not encapsulate that into single transaction. If you really (and I mean really) need one,
you can perhaps make two deployments into temp location that mimics your ultimate Target. On "Both good!" then you'll Deploy
to Target, etc...

Alternatively, you can try to re-configure your "QA_DEF" (that seems to be the troubled one) to a multiple sub-source pattern.
In this schema sub-Sources define their own Target Area and they are deployed serially. Not sure if it'll work in your particular
scenario, you'd have to play with it. Look at OpenDeploy Administration Guide for a sample, Chapter "Content Delivery
Methods", Paragraph "Examples and Recommendations", near the end of it.

Btw, IWOV introduced formal "Serializing Transactional Deployments" feature in OD 6.2.0 Patch 1, your OD version does not have it.

dip21

Thanks for your responces.

We tried deployment by enabling pathRegistryChecking at receiver side.
But we are getting following error message .
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Job ID=m7 Deployment=hfc/iw.consumer_lending.clxml.dev.app.QA_DEF.njd01intdss02
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 OpenDeploy Version is 6.1.1.0.0
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Owner started the deployment is iwui
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Internal config file is /teamsite/iw-home/OpenDeployNG/db/.odrcvr.20014
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 ** Simulate flag = false
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 ** Synchronous flag = true
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 exiting initial
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 entering setup
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Cipher used: RC4-SHA SSLv3 Enc=RC4(128)
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Path registry check (sec): checkinterval=30
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Attempt to register [/teamsite/iw-home/tmp/QA-tmp,0599a620-d67b-11dd-bee8-c751c1192b64]
ENG: 2008-12-30 08:06:45 CST GMT-06:00 Thread-92 Target path unavailable
ENG: 2008-12-30 08:06:45 CST GMT-06:00 Thread-92 Keep checking path registry
ENG: 2008-12-30 08:07:15 CST GMT-06:00 Thread-92 Target path unavailable
ENG: 2008-12-30 08:07:15 CST GMT-06:00 Thread-92 Keep checking path registry

How can we resolved this error.?

Adam Stoller

But we are getting following error message .

ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Job ID=m7   Deployment=hfc/iw.consumer_lending.clxml.dev.app.QA_DEF.njd01intdss02
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 OpenDeploy Version is 6.1.1.0.0
...
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Path registry check (sec): checkinterval=30
ENG: 2008-12-30 08:06:15 CST GMT-06:00 Thread-92 Attempt to register [/teamsite/iw-home/tmp/QA-tmp,0599a620-d67b-11dd-bee8-c751c1192b64]
ENG: 2008-12-30 08:06:45 CST GMT-06:00 Thread-92 Target path unavailable
ENG: 2008-12-30 08:06:45 CST GMT-06:00 Thread-92 Keep checking path registry
...

How can we resolved this error.?

I'm not sure - as I don't have a system to verify things on right now - 6.1 does appear to support the path registry checking feature - so that's good, but I'm unsure about that "Attempt to register" message - I'm assuming the second part of it is an encoded registry key or something - is the first part the actual target directory you are attempting to deploy into? That seems like an odd path to be using for your target path...