[18696] in Athena Bugs
fileserver denying linux afs client
daemon@ATHENA.MIT.EDU (Camilla R Fox)
Fri Jan 26 12:04:53 2001
Message-Id: <200101261704.MAA16504@HOTASS-4.MIT.EDU>
To: bugs@MIT.EDU, ops@MIT.EDU
Cc: bachani@MIT.EDU, allbery@andrew.cmu.edu, arolfe@MIT.EDU
Date: Fri, 26 Jan 2001 12:04:45 -0500
From: Camilla R Fox <cfox@MIT.EDU>
[This came up on -c help, hence the cc's]
[This isn't really a report for bugs, but I'm sending it here in case
other people with this problem are watching; I don't really have an idea
of the number of clients affected.]
prometheus seems to have blocked accesses from superuser.mit.edu; bachani,
who reported this to -c help had initially suspected cache corruption,
and rebooted the machine, clearing the cache. The problem persisted
across reboots, 'fs checks' quickly reported that the server was down,
and he experienced timouts accessing anything on prometheus.
When superuser.mit.edu was brought up on another IP address, the problem
no longer manifest itself.
There was the following in the FileLog on the server:
Tue Jan 23 05:25:46 2001 ProbeUuid failed for host 12ef03aa.7001
Tue Jan 23 17:31:54 2001 ProbeUuid failed for host 12ef03aa.7001
Wed Jan 24 09:18:03 2001 ProbeUuid failed for host 12ef03aa.7001
Fri Jan 26 04:21:21 2001 CB: WhoAreYou failed for 12ef03aa.7001, error -1
Fri Jan 26 06:46:42 2001 CB: RCallBackConnectBack (host.c) failed for host 12ef03aa.7001
bachani reports that he noticed problems a little before 4:28am.
Further discussion found that arolfe had heard a user describe a similar
problem, in the sipb office, and that allbery has seen this at CMU,
involving both linux and solaris clients.
I moved user.bachani to another fileserver; presumably the Sunday restart
will clear up this particular instance of the problem.
I'm assuming that this is the same problem that we heard reports of,
involving windows clients interacting with the new fileserver software.
-Camilla
