Coda File System

Re: Errors on updateclnt

From: Jan Harkes <>
Date: Mon, 11 Mar 2002 13:26:27 -0500
On Mon, Mar 11, 2002 at 04:52:57PM -0000, Mohamed Alwakeel wrote:
> Im getting some errors on my scm and replicating server updateclnt logs, but
> no errors on client, and appears to be no errors on any other of the coda
> server logs like auth2 or srvlog on scm and 2nd server
> As in my earlier posts Im running patched up RH 7.2 with 2.4.17 kernel with
> .18 release of coda.

> 13:04:03 Fetch failed for 'db/' with No such file or directory
> 13:04:03 Fetch failed for 'db/dumplist' with No such file or directory

Ok, the file is the 'previous token', the original security
model was to change the auth2 token regularily as well as the client
tokens. But when we change the auth2 token, there might still be client
tokens out there that were signed with the old token. So the server
simply tries to decode the client token with both and

The dumplist is created whenever you use the Coda backup mechanism to
backup volumes. It is ok to touch both of these files to create empty
ones. The vice-setup script should probably do this, but doesn't the

> 13:04:03 Fopen failed for file /vice/srv/pid with No such file or directory

When any new files are fetched, the server is signalled to read the
updated information. We use the /vice/srv/pid file to find the processid
and send a signal. This was probably the first run before the server was
running, so the pid file didn't exist. No problem here.

Received on 2002-03-11 13:29:08