Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!oakhill!nddsun1!digital!digital.sps.mot.com!chen
From: chen@digital.sps.mot.com (Jinfu Chen)
Newsgroups: comp.sys.apollo
Subject: Re: Unable to update /etc/passwd or registry. Not owner
Keywords: domain registry passwd owner chsh
Message-ID: <5071124e.3593b@digital.sps.mot.com>
Date: 18 Mar 91 17:59:26 GMT
References: <rtb.668960287@cernapo.cern.ch> <1991Mar18.042411.16778@agate.berkeley.edu>
Sender: news@digital.sps.mot.com
Organization: Motorola, LICD, SPS, Mesa, AZ
Lines: 36
Nntp-Posting-Host: logic

In article <1991Mar18.042411.16778@agate.berkeley.edu> dpassage@tornado.Berkeley.EDU (David G. Paschich) writes:
>In article <rtb.668960287@cernapo.cern.ch> rtb@cernapo.cern.ch (Rainer Tobbicke) writes:
>>I have got a problem trying to change my login shell with chsh
>>(I'm running BSD): it says
>>chsh: Unable to update /etc/passwd or registry. Not owner
>>
>The problem appeared with OS 10.3.  It was previously discussed here, and
>the only suggestion we got was to make sure that glbd is running on the same
>node as the master registry, whereas the Apollo docs only say to run it
>somewhere on the ring.  The problem isn't consistent; we've been telling our
>users to try it again later or on a different node.  It seems to occur
>somehere around 50% of the time.

We reported this problem to Apollo (ticket # at020256) a while back. If my
memory is right, it has something to do with incompatibility of
registry database in SR10.2 and SR10.3. User whose password is in SR10.2
format will have trouble changing it under SR10.3 and will get a message
about "not authorized" if using /com/chpass, or "not owner" if using
/bin/passwd. The only way to fix it is to have root login on the node that
runs rgyd master (either via DM or via telnet, not via CRP!), then change it
for the user. After this, the user will be able to use chpass or passwd.

There're several other things you could check:

o	is the master glbd running and communicating with its replica (use
	/etc/ncs/drm_admin)?
o	if upgrading from 10.1, have you replace all 10.1 nodes that run rgyd with 
	the 10.2/10.3 version of rgyd (it can be used on 10.1 node)?
o	kill all other rgyd replica and just use the master rgyd until the problem
	is solved. I know this will be a real royal pain for large network.
o	Order a copy of "Administering the Domain/OS Registry", order no
	015363-A00.

P.S. I was told by the person helping me in the hotline that Apollo will send
a notice to user regarding this registry incompatibility problem. Apparantly,
either I miss the notice, or ...