DNR child2 user failed to initgroups because it OD

What does that error mean?

"DNR child2 user failed to initgroups because it OD was not super-user"

This is deploying from a windows box to a linux box. Both running 6.02

I do not recall seeing this error before, and the dnr does run successfully. I have the as=oduser, and that is the user that is running OD.

<deployment transactional="no">
<execDeploymentTask useDefinition="MYDEFINITIONNAME">
<deployNRun>
<dnrDeployment location="target" when="after" triggerPoint="transfer" state="always" >
<script cmd="/usr/bin/perl /Interwoven/OpenDeployNG/od_solution/cache_refresh.ipl" async="no" where="//Interwoven/OpenDeployNG/conf" as="oduser" />
</dnrDeployment >
</deployNRun >
</execDeploymentTask >
</deployment>

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Find more posts tagged with

Comments

Adam Stoller

Is it "oduser" or "_iwod_user_" - If you're running as non-root I believe it needs to be the latter (at least for permissionRules - not sure about DNR 'as')

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

DavidMusser

Actually Fish it's the name of the user who is running the reciever. Also the user who the script on the reciever should run as.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Adam Stoller

Have you tried leaving off the 'as' attribute altogether?

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

DavidMusser

Yup, deployment failed. Even tried to say as root, but that gave an unable to set GID.

The DNR does run, but I just don't remember seeing this error, so I wanted to see what it means or if anyone else had seen it.

Or if there was a way to pass in oduser Smiley Surprised

dgroup or something in the as argument.

Thanks.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

catorarn

Hello, I am at a customer site in Spain who have a full RH4 ES installation with a base of OD611 and 2 receivers of OD602. They also have this strange message popping up in the od.log files for the 2 receivers:

SVR: 2007-12-11 17:52:01 CET GMT+01:00 Using Reporting log file: /log/OpenDeployNG/ejibm31_eventReporting.log
SVR: 2007-12-11 17:52:01 CET GMT+01:00 Start logging to OpenDeploy server log.
LIB: (2) 2007-12-11 17:52:02 Bound to interface(ejibm31ges) port (20014)
OpenDeploy server and its RMI registry started.
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user
DNR child2 user failed to initgroups because it OD was not super-user

We have analysed with ps - ef on both receivers if there were any scripts running. They have the following possible DNRs but not none of these are running in the server even though this message keeps appearing:
[html]

<script cmd="/bin/ksh /bin/sleep 5" as="r01j" where="/bin" async="no" />

<script cmd="/bin/ksh /aplic/r01j/scripts/r01jIndexer.sh -envName=pro -pathPrefix= -where=sr
c -contentOid=$contentOid -documentVPath=$documentVPath"
as="r01j" where="/aplic/r01j/scripts" async="no" />

<script cmd="/bin/ksh /opt/autonomy/shellscripts/gendata.sh -d /aplic/r32/html/$dest_reposit
ory_relative_path"
as="web" where="/opt/autonomy/shellscripts" async="no" />

[/html]

We have tried stopping the base and 2 receiver OpenDeploy processes with a (custom) OD boot script which sets the user running iwod60 as the user web. This user is a administrator user on the linux machine, just like root.
We restarted in this sequence: base iwod60 stop, rcvr1 iwod60 stop, rcvr2 iwod60 stop, iwodadmin stop, iwaccess stop. base iwod60 start, rcvr1 iwod60 start, rcvr2 iwod60 start, base iwodadmin start, base iwaccess start.

The messages keep coming up. There are 2 deployments set up in the schedule, but this one is not running at all, nor set to start.

This morning the schedDB caused a javaLangOutOfMemory condition and the customer renamed the schedDB.db out of the way as per a registered bug. The system recovered after that.

My question is if you have discovered what exactly causes this error to occur.

I hope you still remember after all this time.

regards,

catorarn

Adam Stoller

[...]
SVR: 2007-12-11 17:52:01 CET GMT+01:00 Using Reporting log file: /log/OpenDeployNG/ejibm31_eventReporting.log
SVR: 2007-12-11 17:52:01 CET GMT+01:00 Start logging to OpenDeploy server log.
LIB: (2) 2007-12-11 17:52:02 Bound to interface(ejibm31ges) port (20014)
OpenDeploy server and its RMI registry started.
DNR child2 user failed to initgroups because it OD was not super-user
[...]

<deployNRun>            
  <!-- BEFORE-SOURCE: sleep  -->
  <dnrDeployment location="source" when="before" >
    <script cmd="/bin/ksh /bin/sleep 5"  as="r01j" where="/bin" async="no" />
  </dnrDeployment>
  <!-- BEFORE-SOURCE: Indexador del buscador -->
  <dnrDeployment location="source" when="before" state="always">                                     
    <script cmd="/bin/ksh /aplic/r01j/scripts/r01jIndexer.sh -envName=pro -pathPrefix= -where=sr
                 c -contentOid=$contentOid -documentVPath=$documentVPath"
as="r01j" where="/aplic/r01j/scripts" async="no" />                             

  </dnrDeployment>
  <!-- AFTER-TARGET: gendata.sh - Generar stubs idx para todos los ficheros -->                       

  <dnrDeployment location="target" when="after" state="success">
    <script cmd="/bin/ksh /opt/autonomy/shellscripts/gendata.sh -d /aplic/r32/html/$dest_reposit
                 ory_relative_path"
as="web" where="/opt/autonomy/shellscripts" async="no" />
  </dnrDeployment>                                                                
</deployNRun>

We have tried stopping the base and 2 receiver OpenDeploy processes with a (custom) OD boot script which sets the user running iwod60 as the user web. This user is a administrator user on the linux machine, just like root.

This looks like a case of OD being run as non-root, or thinking that it is running as non-root, and therefore complaining about the 'as' clause in the above excerpt and/or 'group' and 'owner' settings in the permissionRules element.

But that's just a guess.