[distcc] 回复: Latest distcc on github, can not connect to distccd

chenyu yu.chen.surf at gmail.com
Mon Jul 6 17:53:41 CEST 2015


Hi Martin,
thanks for your reply, here's my result:

$ nc -v  192.168.1.3 3632
nc: connect to 192.168.1.3 port 3632 (tcp) failed: No route to host
I don't know why, is there any firewal blocking? So I also tried :
# service iptables stop
Redirecting to /bin/systemctl stop  iptables.service
# service ip6tables stop
Redirecting to /bin/systemctl stop  ip6tables.service
but the problem still exists.

Regards,
Yu


Try to connect with 

  nc -v  192.168.1.3 3632

On Sat, Jul 4, 2015 at 4:23 PM, chenyu <yu.chen.surf at gmail.com> wrote:
Hi, all
I've got two machine of linux,  A is fedora 21, B is ubuntu 14.04. After
make install distcc on these two machines, I set both A and B as distccd server,

A : ip=192.168.1.3
distccd --daemon --user nobody --allow 192.168.0.0/16 --listen=192.168.1.3
export DISTCC_POTENTIAL_HOSTS='192.168.1.3 192.168.1.2'
export DISTCC_HOSTS='192.168.1.3 192.168.1.2'

and  B:  ip=192.168.1.2
distccd --daemon --user nobody --allow 192.168.0.0/16 --listen=192.168.1.2
export DISTCC_POTENTIAL_HOSTS='192.168.1.2 192.168.1.3'
export DISTCC_HOSTS='192.168.1.2 192.168.1.3'

 it seems that, B can not connect to A,  here's the log on B with DISTCC_VERBOSE=1:

distcc[29402] (dcc_note_state) note state 2, file "exec_domain.c", host "192.168.1.3"
distcc[29402] (dcc_connect_by_addr) started connecting to 192.168.1.3:3632
distcc[29402] (dcc_select_for_write) select for write on fd5
distcc[29402] ERROR: nonblocking connect to 192.168.1.3:3632 failed: No route to host
distcc[29402] (dcc_unlock) release lock fd4
distcc[29402] (dcc_mark_timefile) mark /home/acpi/.distcc/lock/backoff_tcp_192.168.1.3_3632_0
distcc[29402] (dcc_unlock) release lock fd3
distcc[29402] Warning: failed to distribute kernel/exec_domain.c to 192.168.1.3, running locally instead
distcc[29402] (dcc_lock_host) /home/acpi/.distcc/lock/cpu_localhost_0 is busy
distcc[29402] (dcc_lock_host) /home/acpi/.distcc/lock/cpu_localhost_1 is busy


and the port of distcc on A is opened:
$ netstat -nlp | grep distcc
tcp        0      0 192.168.1.3:3632        0.0.0.0:*               LISTEN      5099/distccd

$ ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.449 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.335 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.390 ms

$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     1      0        0 eth2

Can anyone please give me some advice on why this happened.
Thanks

Yu
__
distcc mailing list            http://distcc.samba.org/
To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/distcc



-- 
Martin


More information about the distcc mailing list