[distcc] Server times out after a few files

[Patrick Hanna]

Turns out that some other machine on my network had the same ip. I
fixed that issue.

But I have another question. I built distcc for the mac (I've tried
several versions but I get the same behavior) and everything works
great for a while until distcc stops sending requests to all the hosts
and only sends to the first one in the list. The logs report that
distcc is starved. It looks like there are locks in ~/.distcc/locks
for all the other hosts. I know that the remote machines are fine
because if I stop the build and restart where it left off everything
is fine.

How does distcc get starved? If I change the order of hosts the
behavior doesn't change, it is always the first host in the list that
continues to work and all the other hosts stop receiving work.

Patrick

On Jan 3, 2008 6:19 PM, Martin Pool <mbp at sourcefrog.net> wrote:
> On 04/01/2008, Patrick Hanna <phanna at google.com> wrote:
> > I don't think this is a distccd problem at all. Running arping on my
> > remote host gives me the correct mac address for the first reply and
> > then a completely different address for the rest of the replies. Any
> > clue how that could ever happen?
>
> I'd only be guessing.  I would love to hear what the problem turns out to be.
>
> A few years ago distcc did expose Linux bugs (timer overflows iirc)
> that caused it to abruptly drop the connection.  But that just caused
> particular large files to fail, and not this strange behaviour.
>
> --
> Martin
>