Hi,
I know this topic has been discussed before, but the conclusion was that
it is caused by NAT.
This is impossible in my case, as openafs servers are firewalled from
the outside world.
The fileserver has 3 ethernet interfaces:
1: connected to the clients, two IP addresses one active (other in th
Well, that didn't take long, it already blew up again, in exactly the
same fashion, with the same two culprit volumes.
--
Ryan C. Underwood,
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
On Sun, Mar 20, 2011 at 09:57:22PM -0500, Andrew Deason wrote:
>
> Oh, hmm, this starts too late. I guess you don't have the BosLog before
> this?
Nope, wish it rotated more old logs out but haven't looked into this.
> > 03/20/2011 16:36:17 The volume header file /vicepa/V0536871274.vol is not
On Sun, 20 Mar 2011 20:59:43 -0500
"Ryan C. Underwood" wrote:
> Not much interesting in BosLog.old:
> Sun Mar 20 04:00:29 2011: Core limits now -1 -1
Oh, hmm, this starts too late. I guess you don't have the BosLog before
this?
> 03/20/2011 16:34:31 CHECKING CLONED VOLUME 536871274.
> 03/20/201
On Sun, Mar 20, 2011 at 07:42:12PM -0500, Andrew Deason wrote:
>
> What's in SalsrvLog and SalsrvLog.old? It should have a bunch of stuff
> on the salvages here. Also, BosLog for this time period would be good
> for completeness.
Not much interesting in BosLog.old:
Sun Mar 20 04:00:29 2011: Core
Quoting Jason Edgecombe :
Is this enforcing a policy decision or just preventing technical
problems caused by multiple logins?
For my site it is strictly to prevent technical problems.
I'm wondering because we us gnome on RHEL5 with AFS home directories
and multiple logins on different mac
On Sun, 20 Mar 2011 16:50:16 -0500
"Ryan C. Underwood" wrote:
> Shortly after the weekly scheduled fileserver restart, things blew up
> in a big way. My RW root.cell was inaccessible in the end. No kernel
> messages indicating filesystem or disk problems underneath. I
> force-fscked the vice p
Shortly after the weekly scheduled fileserver restart, things blew up in
a big way. My RW root.cell was inaccessible in the end. No kernel
messages indicating filesystem or disk problems underneath. I force-fscked
the vice partition (ext4) and no problems were found. Any speculation
on what in
On 03/20/2011 08:19 AM, Coy Hile wrote:
On Sat, Mar 19, 2011 at 1:23 PM, Jaap Winius wrote:
Quoting Dirk Heinrichs:
... Is it possible to prevent users from logging in more than once ...
No, you can't. ...
Couldn't you potentially write a PAM module to do exactly that? At
the top of the se
On Sat, Mar 19, 2011 at 1:23 PM, Jaap Winius wrote:
> Quoting Dirk Heinrichs :
>
>>> ... Is it possible to prevent users from logging in more than once ...
>>
>> No, you can't. ...
Couldn't you potentially write a PAM module to do exactly that? At
the top of the session stack, have it store the
10 matches
Mail list logo