Was there any successful resolution to this problem? I'm seeing what appears
to be the same symptoms on my second server (Redhat6.2, Coda-5.3.8 built
with krb5 support).
- kauth2/auth2 refuses to run, giving the "base PDB record does not exist."
error
- codasrv dies immediately after loading entire data space into memory
- updateclnt appears to be running fine, but VLDB and VRDB aren't being
replicated
- I am using kerberos for auth - is there anything special I need to do for
a replicated server?
TIA for any help resolving this, it's driving me crazy...
Stephan B. Koledin
The Motley Fool
Systems DORC
[EMAIL PROTECTED]
http://www.fool.com
> -----Original Message-----
> From: Piotr K. Isajew [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 16, 2000 4:15 PM
> To: Jan Harkes
> Cc: [EMAIL PROTECTED]
> Subject: Re: Server replication problems
>
>
> On Wed, Aug 16, 2000 at 12:06:41PM -0400, Jan Harkes wrote:
> > On Wed, Aug 16, 2000 at 09:54:31AM +0200, Piotr K. Isajew wrote:
> > > Hi,
> > >
> > > I tried to set up a second server for my coda cell, but
> there are problems
> > > starting up auth2 and codasrv.
> > >
> > > Here are log entries for those demons:
> > > AuthLog:
> > > Starting Auth Server......
> > > base PDB record does not exist. start over.
> >
> > It looks like the update client/server are not working
> properly. Check
> > if the updateclnt on the second server is running and that
> /vice/db/scm
> "ps ax" looks ok.
> > is the correct name of the first (SCM) server.
> # cat scm
> pki
>
> - looks ok
> >
> > If that seems to be ok, could you try to create the
> following link on
> > the scm and restart the updateclnt on the second server?
> >
> > $ ln -s . /vice/db/db
> Done
>
> # updatesrv
> # updateclnt -h pki
> # auth2 -r -chk
> Starting Auth Server......
> base PDB record does not exist. start over.
> # ps ax
> PID TT STAT TIME COMMAND
> 235 ?? Is 0:02.41 rpc2portmap
> 31400 ?? Is 0:00.04 updatesrv
> 31402 ?? Is 0:00.06 updateclnt -h pki
> [... nothing more related to coda server ...]
>
> # ls -l /vice/db
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 ROOTVOLUME
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 auth2.lock
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 auth2.pw
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 auth2.tk
> lrwxr-xr-x 1 root wheel 1 Aug 16 21:59 db -> .
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 files
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 prot_index.db
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 prot_users.db
> -rw-r--r-- 1 root wheel 4 Aug 11 15:35 scm
> -rw-r--r-- 1 root wheel 9 Aug 11 16:11 servers
> -rw------- 1 root wheel 7 Aug 11 15:36 update.tk
> -rw-r--r-- 1 root wheel 53 Aug 11 16:11 vicetab
> -rw-r--r-- 1 root wheel 0 Aug 10 21:42 volutil.tk
>
>
> Looks like VLDB and VRDB are not replicated (but why?). Does anyone
> has any idea?
>
> Piotr
> >
> > The /vice/db directory on the second server should get
> populated with
> > files like VLDB, VRDB, prot_index.db, and prot_users.db.
> >
> > Jan
> >
> >
>
