DNR: as clause contains invalid user name?

Hi,

I am trying to execute a shell script on Solaris before an OpenDeploy deployment. I created the following deploy and run configuration:

<execDeploymentTask useDefinition="TEST_DEPLOYMENT" downRev="" >
<deployNRun >
<dnrDeployment location="source" when="before" state="always" mask="" >
<script cmd="/tmp/test.sh" as="root" async="no" >
</script>
</dnrDeployment>
</deployNRun>
</execDeploymentTask>

Even though I specified as="root" I get the error message "as clause contains invalid user name = ò¯òpò¯òy".

Here is the log file:

...
deploy_run_script=/tmp/test.sh
async=no
where=
as=root
when=client_before_deploy on_success on_failure
;
...
ERROR: DNR Execution failed. as clause contains invalid user name = ò¯òpò¯òy
ERROR: client_before_deploy DNR script failed.
ERROR: Failed to begin transaction.

Any help would be appreciated.

Thanks.

Ralph

Find more posts tagged with

Comments

gwen1

Is OpenDeploy running as root on your server? If not, it may not have permissions to specify root as the user.

Gwen

rbuelling

Gwen,
Thanks for the quick response. Yes, OpenDeploy is running as root.

Also: I tried running it without an "as" clause as well, but I got the same error message.

Any other ideas?

Thanks.

Ralph

Michael

HI Ralph

I haven't seen this before so I can't really provide any good ideas, but here are some things you could try:
- restart OpenDeploy
- try putting a user other than root in your "as" clause
- check that you don't have any weirdness with the permission on your script file -- does it have ordinary execute permissions? is it owned by root?
- check if it actually does execute the script -- regardless of what it is saying in the logging - perhaps by creating a log file?
- do you get this with all scripts running from OpenDeploy or just this one?

If problems persist you probably should get IWOV support on the case.

Hope this helps.

Cheers, Michael

Adam Stoller

Could you *attach* the deployment configuration file to this thread?
I'm wondering if you have some high-order-bit characters within your configuration file that is somehow confusing things?

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

Migrateduser

This sounds familiar and I believe was corrected at some point. Are you using OD 5.6 with latest SP and patch?

Perhaps Tech Support can shed more light on the problem cause and resolution.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

rbuelling

Thanks for all the feedback.

I ran additional tests with different user IDs, different shell scripts and different permissions on the script file. All these tests produced the same error message.

However, this is an OD 5.5.1 server. I am in the process of trying the same thing on our OD 5.6 test server. I will let you know if we have the same problems there.

Thanks again.

Ralph

Capture.PNG

arinm209

Did anybody get a solution to this problem?