Hello, Thomas Sesselmann schrieb: > I found the potential issue, i think. > The UUID for the client (cache manager) isn't calculated: > > 'cmdebug <client> -addr' shows: > UUID: 00000000-0000-0000-00-00-000000000000 > Host interfaces: > Capabilities: > Error Translation
to fast ... :-/
I read a changelog of a new OpenAFS package...
I have to install a new version of OpenAFS, haven't I?
--------------------------------------------------------------------------------
openafs (1.4.4.dfsg1-6) unstable; urgency=low
* Apply upstream patch for the OpenAFS file server to treat clients that
have an all-zero UUID as if they don't have UUID support, working
around bugs in various client versions that can cause multipleupstream
patch for the OpenAFS file server to treat clients that
have an all-zero UUID as if they don't have UUID support, working
around bugs in various client versions that can cause multiple hosts
to use all-zero UUIDs and conflict with each other. hosts
to use all-zero UUIDs and conflict with each other.
[...]
-- Russ Allbery <[EMAIL PROTECTED]> Thu, 02 Aug 2007 19:54:00 -0700
[...]
openafs (1.4.4.dfsg1-3) unstable; urgency=low
* Always generate a UUID on client startup even if for some reason we
don't think we have any network interfaces. Otherwise, the client
will use an all-zeroes UUID, which will collide with every other
client with the same problem.
[...]
--------------------------------------------------------------------------------
best regards
Thomas Sesselmann
--
Dipl.-Inf. Thomas Sesselmann __O
Kirchhoff-Institut für Physik _\-<,
Universität Heidelberg _(_)/(_)_
INF227 / D-69120 Heidelberg
Tel.: +49/6221/54-9132
E-Mail: [EMAIL PROTECTED]
gpg-key: 0x9392E54B or finger -l [EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
