[32785] in Kerberos
Re: kpropd deadlocking?
daemon@ATHENA.MIT.EDU (ghudson@mit.edu)
Sat Oct 9 01:39:31 2010
Date: Sat, 9 Oct 2010 01:30:09 -0400 (EDT)
From: ghudson@mit.edu
Message-Id: <201010090530.o995U91c011483@outgoing.mit.edu>
To: Jack Neely <jjneely@ncsu.edu>
In-Reply-To: <20101008215518.GE7231@virge.linuxczar.net>
Cc: kerberos@mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
> The from_master.temp isn't complete, the kpropd child process is
> stuck on a read() syscall. The kprop client on the master is stuck
> on a write() syscall.
To me, this suggests a problem at the network layer. The sender
should only block on write() if it has stopped receiving ACKs from the
receiver. I would run a packet trace on the sender and receiver and
look for discrepancies.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos