1 |
On Tue, 05 Jun 2007 06:15:25 -0400 |
2 |
PaulNM <gentoo@×××××××××.com> wrote: |
3 |
|
4 |
> Hi all, |
5 |
> |
6 |
> Distcc seems to not be working properly on one or all of my 3 |
7 |
> systems. I have : |
8 |
> Galactica 192.168.1.22 Pentium 2 (Problem system) |
9 |
> Robotech 192.168.1.40 Pentium 3 |
10 |
> Optimus 192.168.1.80 AMD64 AthlonX2 (crossdev setup) |
11 |
> |
12 |
> All are Gentoo with distcc installed and configured. Optimus is |
13 |
> solely a helper system to the other two as far as distcc is |
14 |
> concerned. If I emerge something on Robotech, both Robotech and |
15 |
> Optimus are used, but Galactica seems to be ignored with no error |
16 |
> messages. When I try on Galactica, I get numerous |
17 |
> "distcc[910] (dcc_writex) ERROR: failed to write: Connection reset by |
18 |
> peer distcc[910] Warning: failed to distribute ckkv.c to 192.168.1.22, |
19 |
> running locally instead" |
20 |
> messages, also listing the other two ip's 40 and 80. |
21 |
> |
22 |
> "cat /etc/distcc/hosts" on all three results in "192.168.1.80 |
23 |
> 192.168.1.40 192.168.1.22". They all have |
24 |
> "sys-devel/distcc-2.18.3-r10" and "/etc/conf.d/distccd" modified the |
25 |
> same way : DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.1.40 |
26 |
> 192.168.1.80 192.168.1.22" |
27 |
> Distccd was restarted after any config changes. |
28 |
> |
29 |
> All three have i686-pc-linux-gnu toolsets/chosts, and as far as I can |
30 |
> tell should work. No firewalls are in place for testing, distccd port |
31 |
> is open on all three (confirmed with nmap), and I'm out of ideas on |
32 |
> where to look for problems. |
33 |
> |
34 |
> Any help or suggestions would be appreciated. |
35 |
> |
36 |
> PaulNM |
37 |
The example I see in etc/conf.d/distccd lists each allowed ip address |
38 |
after its own --allow argument. Furthermore, you might consider |
39 |
whether you'd rather allow anyone on your local subnet to connect -- |
40 |
for example if you add new hosts -- and specify in cidr notation |
41 |
something like "--allow 192.168.1.0/24" |
42 |
|
43 |
As it is now, i think only Robotech will be allowed to distribute code |
44 |
on any host. I would think galactica would be included in that list, |
45 |
but for some reason it doesn't seem to want to accept the connections. |
46 |
|
47 |
I wonder, do you have MAKEOPTS set high enough on your systems to |
48 |
compile on more than 2 computers at once? D |
49 |
|
50 |
id you use distcc-config? |
51 |
|
52 |
Have you set the configs to accept the number of jobs you want each |
53 |
computer to accept maximum? This should be low for the pII and much |
54 |
higher for the X2. |
55 |
|
56 |
Finally, I wanted you to entertain the notion that if robotech's |
57 |
make.conf (wait, are these names from Transformers?) is set to compile |
58 |
for a PIII, with sse instructions and such, the PII may not be able to |
59 |
do it, or if it can, might be required to build a crossdev toolchain |
60 |
too. FWIW, pIIs on my network are no longer allowed to 'help' the |
61 |
faster computers compile because they generally tend to slow them down |
62 |
rather than speed them up. |
63 |
|
64 |
Good luck!! |
65 |
-- |
66 |
gentoo-user@g.o mailing list |