[distcc] Problem with distcc doing remote compiles locally

[Victor Norman]

I am having a problem right now with my distcc not being able to run compiles in which it chooses a distccd that happens to be on the same machine.  Whenever the local machine is chosen, the distcc verbose output shows:


distcc[7434] (dcc_connect_by_addr) started connecting to 10.90.2.68:3632
distcc[7434] ERROR: failed to connect to 10.90.2.68:3632: File exists

or, after manually having deleted the lock/state directory before starting the compile:

distcc[10729] (dcc_connect_by_addr) started connecting to 10.90.2.68:3632
distcc[10729] ERROR: failed to connect to 10.90.2.68:3632: No such file or directory


Note: the machine's IP address is 10.90.2.68, and, to re-iterate, I'm running the compile
on this machine, and have the distccd's running on this machine (as well
as a bunch of other machines).

In the distccd's log file I see this:

distccd[7985] (dcc_check_client) connection from 10.90.2.68:42673
distccd[7985] (dcc_readx) ERROR: unexpected eof on fd5
distccd[7985] (dcc_r_token_int) ERROR: read failed while waiting for token "DIST"
distccd[7985] (dcc_r_request_header) ERROR: client did not provide distcc magic fairy dust


Any ideas on what is happening here?  I was noticing that 
dcc_connect_by_addr() does not do a close() on the fd ever.  Is this
a problem?

Thanks.

Vic



		
---------------------------------
Brings words and photos together (easily) with
 PhotoMail  - it's free and works with Yahoo! Mail.
-------------- next part --------------
HTML attachment scrubbed and removed