kpropd deadlocking?

ghudson@MIT.EDU ghudson at MIT.EDU
Sat Oct 9 01:30:09 EDT 2010


> 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.



More information about the Kerberos mailing list