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

OpenDeploy issue

Prerna

Hi All,
We are getting the following error while deploying the content to our Servers:
Remote-ERROR: remote-dir-not-ok
ERROR: prepare-failed.
Receiver-ERROR: ERROR: [/pgAdata/iams71] is not an allowed deployment path.

The target path on our servers is "/content/iams71" and not "/pgAdata/iams71", against which the complaint is made.
And "/content/iams71" does exists on our server with all required permissions.

So don't know from where OD is picking "/pgAdata/iams71" and trying to deploy there.

Teamsite version : 6.7.1
OD version : 6.0

Any help in this matter will be highly appreciated.

Thanks in advance.
Prerna

Find more posts tagged with

Comments

Faizi

Hi All,
We are getting the following error while deploying the content to our Servers:
Remote-ERROR: remote-dir-not-ok
ERROR: prepare-failed.
Receiver-ERROR: ERROR: [/pgAdata/iams71] is not an allowed deployment path.

The target path on our servers is "/content/iams71" and not "/pgAdata/iams71", against which the complaint is made.
And "/content/iams71" does exists on our server with all required permissions.

So don't know from where OD is picking "/pgAdata/iams71" and trying to deploy there.

Teamsite version : 6.7.1
OD version : 6.0

Any help in this matter will be highly appreciated.

Thanks in advance.
Prerna

What are the allowed directories in odbase.xml file?
And what is targetFilesystem path given in deployment configuration file that is passed in deploy task?
Check these two, might be there is "pgAdata/iams71" path defined in deployment configuration file which not in defined in allowed directories in odbase or odreceiver.

Prerna

Thanks for your response, Faizi.
But no where in our OD configuration files(odbase,odrcvr,config file for deployment) we have given "/pgAdata/iams71" as target path.

And this is the real big confusion from where this is being picked up.

Faizi

Thanks for your response, Faizi.
But no where in our OD configuration files(odbase,odrcvr,config file for deployment) we have given "/pgAdata/iams71" as target path.

And this is the real big confusion from where this is being picked up.

Ok, you can try to change the config file for deployment and try to deploy, now what is the output. Might be possible a different config file being used.

Prerna

ok.. i just rechecked my odrcvr.xml to find i have two path names in my "allowedDirectories" tag:
1. "/content"
2. "/pgBdata"

So as we can see we have 2 allowed paths on the target server.

But the question is that why is it trying to deploy the content to "/pgBdata" when i specified the target path as "/content" in my iwodstart???

Faizi

ok.. i just rechecked my odrcvr.xml to find i have two path names in my "allowedDirectories" tag:
1. "/content"
2. "/pgBdata"

So as we can see we have 2 allowed paths on the target server.

But the question is that why is it trying to deploy the content to "/pgBdata" when i specified the target path as "/content" in my iwodstart???

While running clt "iwodstart" you will be passing a deployment config file name.

Usage: iwodstart depName [-async] [-inst instName] [-k "key=value"]+
        [-sim] [-V (normal | verbose)] [-odinst odInstName] [-uuid]

Now check the deploy config file (passed as depName), what is the path give in targetFilesystem tag.

jagadesh

Hi,
Please provide the Target OS Details.
If Target is solaris then check /content/iams71 is link file or not.

Some times link file points to another directory.

Adam Stoller

Hi,
Please provide the Target OS Details.
If Target is solaris then check /content/iams71 is link file or not.

Some times link file points to another directory.

That would be my guess too - since OD does check links for target paths and evaluates them before determining if the path is vald - so if /content/iams71 is a link to /pgAdata - and you have /content and /pgBdata listed as allowed - then the deployment will fail because /content is really /pgAdata and that is not an allowed path.