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

Issue with DNR execution

Premshan

Hi,

I see the below error during a DNR execution.
DNR Execution failed. as clause contains invalid user name = Premshan

Does anybody know why am I facing the issue ?

Thanks,
Premshan

Find more posts tagged with

Comments

ISCBorisB

Hi,

I see the below error during a DNR execution.
DNR Execution failed. as clause contains invalid user name = Premshan

Does anybody know why am I facing the issue ?

Thanks,
Premshan

This is probably some error notification generated by your own custom DNR Code or perhaps corresponding
WF Components that execute the Deployment in question. Unless you provide relevant information, we have
no way of knowing what and why you (ie, your code/components) are doing.

Premshan

I have a Worfklow Model which among other tasks also has a Deployment task.

The Deployment task deploys content to target servers, by first deploying the actual files and the filelist to an intermediate server from the TeamSite content store and then executing a DNR on the intermediate server to deploy the content to the actual target servers. (We are not using routed/multi-tiered deployments)

The DNR in the deployment definition looks like this... script cmd="/apps/od-home/OpenDeployNG/bin/iwodstart simple_deploy_prod -k filelist=$filelist

When I instantiate the workflow model everything seems to be working fine till the DNR execution part. During the DNR execution below is the error that I see in the micro logs

ERROR: DNR Execution failed. as clause contains invalid user name = Premshan

Let me know if you need more details.

Rick Poulin

Does your DNR specify a 'runas' user that is invalid? If not, post that portion of your OD config file.

Premshan

Here is how the DNR part looks like

<script cmd="/apps/od-home/OpenDeployNG/bin/iwodstart simple_deploy_prod -k filelist=

$filelist"
where="/apps/od-home" async="no"/>

Premshan

Sorry here it is attached.

Adam Stoller

(Please read this before making any more posts)

You have a DNR command invoking another deployment (without any wrapper to check success or failure).

My guess is that the second deployment is failing due to impersonation issues - but you might be able to fix it if you change the command from:

/apps_01/od-home/OpenDeployNG/bin/iwodstart simple_deploy_prod ...

to:

/apps_01/od-home/OpenDeployNG/bin/iwodcmd start simple_deploy_prod ...

Beyond that, you'd have to check settings in the

deploy.cfg

and

odbase.xml

Premshan

Thank you, Ghoti.

So I made the change for the dnr to invoke iwodcmd instead of iwodstart and I still see the same issue.

Also I got myself added to the od-admin role in the intermediate server but still the issue persists.

All the workflows that are instantiated using wft's where we do similar DNR executions are working fine, its just the jobs instantiated using wfm's which seem to be having this problem.

I will look into the deploy.cfg and odbase.xml and raise a support ticket too.

nipper

When I instantiate the workflow model everything seems to be working fine till the DNR execution part. During the DNR execution below is the error that I see in the micro logs

ERROR: DNR Execution failed. as clause contains invalid user name = Premshan

Let me know if you need more details.

So this runs on the OD receiver, is Premshan a valid use on the receiver ?

Premshan

When I execute the command od-home/bin/iwodauthorize -r list od-admin

I do see my name as belonging to the od-admin role on the intermediate server where the DNR fails to execute

nipper

When I execute the command od-home/bin/iwodauthorize -r list od-admin

I do see my name as belonging to the od-admin role on the intermediate server where the DNR fails to execute

That may not matter, the server *might* need to kick off a process in your name, so if you do not have the permission to log on locally, try to change it. Otherwise make it run as root

Adam Stoller

So I made the change for the dnr to invoke iwodcmd instead of iwodstart and I still see the same issue.

Also I got myself added to the od-admin role in the intermediate server but still the issue persists.

All the workflows that are instantiated using wft's where we do similar DNR executions are working fine, its just the jobs instantiated using wfm's which seem to be having this problem.

If you're using the DeployTask in WFM, then the initial deployment is being run through web services and not via the CLT.

There was nowhere near sufficient information in your original post or the snippet of the configuration file that you attached, to know that the second deployment is being run on an intermediate Base Server acting as a hub.

Things that might help to know:

Premshan

Here are the answers to your questions,

Do you have strictAuthentication enabled in any of the server's odbase.xml or odrcvr.xml files? The attribute is not defined on either the odbase or the odrcvr.xml's listenerProperties element and hence defaults to no I guess.
Do you have cltProxyAuthCheck enabled in any of the Base Server's deploy.cfg files? Yes enabled on all the Base servers
Is your account an OS account or an LDAP account? OS account
Can you attach the relevant micro logs from both the originating Base Server (src.*) and the intermediary Base Server (rcv.* and src.*)? Unfortunately I will not be able to attach all of the micro logs. I have only attached a part of he receiver micro log which has the error message.

nipper

Again, I ask, do you have permission to log on the intermediate server ? The error you post implies you do not.

Premshan

Sorry Nipper,

You are right, the intermediate server does not have a UNIX profile under my name.

So now I think to fix the issue the Owner of the Deployment Task has to be changed to that of a generic user with user profiles on both the source and intermediate servers instead of $IW_USER I guess.

nipper

Wrong.

You need to change the DNR invocation to run as a specific user, who can log in on the intermediate server as well as has OD Admin rights. Root would work

Premshan

Okay so that fixed it.

I think the confusion was because the UNIX user id associated with the iwglobal group on the TeamSite server is different from the one on the hub server.

And since the OWNER of the deployment task defaults to $IW_USER, I was having the issue with the DNR not executing.

I changed the deployment task OWNER to a generic id with od-admin roles on both the the TeamSite and the hub server and now the issue is fixed.

Thanks to nipper, ghoti, Boris and rpoulin for all your help and time.