Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Cannot get distcc/pump to work [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Thu Dec 20, 2012 2:21 am    Post subject: Cannot get distcc/pump to work [SOLVED] Reply with quote

I have two machines on a GigaLAN both running distccd.
1) Workstation (Intel i7-3770K) with 8 logical CPUs.
2) Laptop (Intel C2D) with 2 logical CPUs.

Again, both are running distccd. Example:
Code:

% ps aux | grep distccd
nobody   26922  0.0  0.0  19636   916 ?        SNs  21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26923  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26926  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26927  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26928  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26942  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26943  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26944  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26945  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26946  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log
nobody   26947  0.0  0.0  19636   164 ?        SN   21:22   0:00 /usr/bin/distccd --no-detach --daemon --allow 192.168.0.0/24 --log-level warning --log-file /tmp/distccd-x86_64.log


On my workstation:
Code:
% cat /etc/distcc/hosts
localhost/9,cpp,lzo
192.168.0.102/3,cpp,lzo


On my laptop:
Code:
% cat /etc/distcc/hosts
localhost/3,cpp,lzo
192.168.0.101/9,cpp,lzo


Just the workstation
Here is just the workstation
Code:
% make -j8 bzImage  496.11s user 25.67s system 712% cpu 1:13.26 total


Trying to use pump/distcc
On the laptop...
Code:
% eval pump --startup


On the workstation...
Code:
% eval pump --startup

Code:
% pump make -j12 bzImage CC=distcc
__________Using distcc-pump from /usr/bin
__________Using 2 distcc servers in pump mode
make[1]: Nothing to be done for `all'.
  HOSTCC  scripts/basic/fixdep
  CHK     include/generated/uapi/linux/version.h
...
  CC      arch/x86/xen/setup.o
  CC      arch/x86/realmode/rm/video-vga.o
  CC      arch/x86/mm/fault.o
  CC      arch/x86/realmode/rm/video-vesa.o
distcc[25252] ERROR: compile arch/x86/realmode/rm/video-vesa.c on 192.168.0.102/3,cpp,lzo failed
distcc[25252] (dcc_build_somewhere) Warning: remote compilation of 'arch/x86/realmode/rm/video-vesa.c' failed, retrying locally
distcc[25214] ERROR: compile arch/x86/realmode/rm/video-vga.c on 192.168.0.102/3,cpp,lzo failed
distcc[25214] (dcc_build_somewhere) Warning: remote compilation of 'arch/x86/realmode/rm/video-vga.c' failed, retrying locally
distcc[25252] Warning: failed to distribute arch/x86/realmode/rm/video-vesa.c to 192.168.0.102/3,cpp,lzo, running locally instead
distcc[25214] Warning: failed to distribute arch/x86/realmode/rm/video-vga.c to 192.168.0.102/3,cpp,lzo, running locally instead
  CC      mm/mempool.o
distcc[25252] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'arch/x86/realmode/rm/video-vesa.c' failed, retried locally and got a different result.
distcc[25252] (dcc_note_discrepancy) Warning: now using plain distcc, possibly due to inconsistent file system changes during build
  CC      kernel/panic.o
distcc[25214] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'arch/x86/realmode/rm/video-vga.c' failed, retried locally and got a different result.
  CC      arch/x86/realmode/rm/video-bios.o
  CC      arch/x86/xen/multicalls.o
  PASYMS  arch/x86/realmode/rm/pasyms.h
  LDS     arch/x86/realmode/rm/realmode.lds
  LD      arch/x86/realmode/rm/realmode.elf
  RELOCS  arch/x86/realmode/rm/realmode.relocs
  OBJCOPY arch/x86/realmode/rm/realmode.bin
  AS      arch/x86/realmode/rmpiggy.o
...
  OBJCOPY arch/x86/boot/setup.bin
  BUILD   arch/x86/boot/bzImage
Setup is 17036 bytes (padded to 17408 bytes).
System is 3429 kB
CRC fa62427
Kernel: arch/x86/boot/bzImage is ready  (#10)
__________Warning: 3 pump-mode compilation(s) failed on server, but succeeded locally.
__________Distcc-pump was demoted to plain mode.  See the Distcc Discrepancy Symptoms section in the include_server(1) man page.
__________Shutting down distcc-pump include server
pump make -j12 bzImage CC=distcc  373.40s user 18.70s system 455% cpu 1:26.10 total


Love to figure out what's going wrong.


Last edited by graysky on Sun Dec 23, 2012 12:37 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Thu Dec 20, 2012 5:24 pm    Post subject: Reply with quote

graysky,

Code:
% cat /etc/distcc/hosts
localhost/9,cpp,lzo
192.168.0.102/3,cpp,lzo   


A few things.
First, don't put localhost first in the list or jobs are not distributed to helpers until localhost is full.
Secondly, I think the hosts file needs to be a single line.

You can actually omit localhost - it will be used when distribution fails anyway
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Thu Dec 20, 2012 9:36 pm    Post subject: Reply with quote

I tried making a single line but got the same results. Also tried omitting localhost. Per the man page of distcc, it parses the hosts file which can be multiple lines. You can check by `distcc --list-hosts` - other ideas?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Thu Dec 20, 2012 11:28 pm    Post subject: Reply with quote

graysky,

Post the /etc/conf.d/distccd file from one of the helpers
Check that distccd is running on the helpers
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Fri Dec 21, 2012 12:23 am    Post subject: Reply with quote

NeddySeagoon wrote:
Post the /etc/conf.d/distccd file from one of the helpers
Check that distccd is running on the helpers


From my laptop although I use the identical one on the workstation as well:
Code:
% cat /etc/conf.d/distccd
DISTCC_ARGS="--allow 192.168.0.0/24 --log-file /tmp/distccd.log"


Distccd is absolutely running on both boxes as is:
Code:
% eval `pump --startup`
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Fri Dec 21, 2012 1:51 pm    Post subject: Reply with quote

graysky,

Dies it work for emerge?

Put distcc in your FEATURES, then run
Code:
pump emerge glibc -1
as a test.

What is your MAKEOPTS= on each system?
On the laptop, you probably need -j10 or so to keep both systems busy.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Fri Dec 21, 2012 3:21 pm    Post subject: Reply with quote

Been going crazy over this and wiped out my gentoo partitions; currently have Arch on both boxes and cannot get pump to function correctly there either. Regular distcc works fine though as it did under Gentoo. Has to be something I am overlooking. Eventually, I'd like to use this at the office where we running RHEL servers. My laptop would be the master compiler there, but the RHEL servers do run distcc v3.1 so in theory this should all work.

Any other suggestions or ideas are welcomed.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sat Dec 22, 2012 11:07 am    Post subject: Reply with quote

@NeddySeagoon - Does pump work for you? Can you post your key config files?
Back to top
View user's profile Send private message
franzf
Advocate
Advocate


Joined: 29 Mar 2005
Posts: 4187
Location: Irgendwo im Nirgendwo

PostPosted: Sat Dec 22, 2012 11:22 am    Post subject: Reply with quote

pump for me seemed to work, but then I got weird issues making packages just fail. It was due to the server using it's own headers rather then the ones "pumped" by the client. The server simply had another version installed, which was incompatible to what the client needed (I THINK the error was due to inlined code leading to linker error, but I am not sure anymore).

Now I am simply going with the classic way, leaving preprocessing to the client.
_________________
"der mac dennoch wesen geil"
Wolfram von Eschenbach, Parzival (Buch 1, Z. 7).
Ein frühes Statement gegen Windows.

My overlay
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Sat Dec 22, 2012 8:51 pm    Post subject: Reply with quote

graysky,

pump works for me - mostly. For certain errors, it gets demoted to plain mode.

On my Pi ... where I run
Code:
pump emerge ...

I have
Code:
/etc/distcc/hosts
with one line, 192.168.100.20/8,lzo,cpp
That allows the Pi to send 8 jobs in pump mode to my AMD64 helper.

Code:
CFLAGS="-O2 -march=armv6j -mfpu=vfp -mfloat-abi=hard"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j8"
FEATURES="-collision-protect sandbox buildpkg noman noinfo nodoc distcc"



On the helper, I have distccd in the default runlevel
Code:
# /etc/conf.d/distccd: config file for /etc/init.d/distccd

DISTCCD_OPTS=""

# this is the distccd executable
DISTCCD_EXEC="/usr/bin/distccd"

# this is where distccd will store its pid file
DISTCCD_PIDFILE="/var/run/distccd/distccd.pid"

# set this option to run distccd with extra parameters
# Default port is 3632.  For most people the default is okay.
DISTCCD_OPTS="${DISTCCD_OPTS} --port 3632"

# Logging
# You can change some logging options here:
# --log-file FILE
# --log-level LEVEL  [critical,error,warning, notice, info, debug]
#
# Leaving --log-file blank will log to syslog
# example: --log-file /dev/null --log-level warning
# example: --log-level critical

DISTCCD_OPTS="${DISTCCD_OPTS} --log-level critical"

# SECURITY NOTICE:
# It is HIGHLY recomended that you use the --listen option
# for increased security. You can specify an IP to permit connections
# from or a CIDR mask
# --listen accepts only a single IP
# --allow is now mandatory as of distcc-2.18.
# example:  --allow 192.168.0.0/24
# example:  --allow 192.168.0.5 --allow 192.168.0.150
# example:  --listen 192.168.0.2
#DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.0.0/24"
#DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.2"

DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.100.0/24"

# set this for niceness
# Default is 15
DISTCCD_OPTS="${DISTCCD_OPTS} -N 15"

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sat Dec 22, 2012 9:05 pm    Post subject: Reply with quote

Thanks for info. Tell me: what does /etc/distcc/hosts look like on your helper? Also, do you ever run `eval pump --startup` on either machine?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Sat Dec 22, 2012 9:17 pm    Post subject: Reply with quote

graysky,

/etc/distcc/hosts on the helper is just the default
Code:
 # --- /etc/distcc/hosts -----------------------
# See the "Hosts Specification" section of
# "man distcc" for the format of this file.
#
# By default, just test that it works in loopback mode.
127.0.0.1
since it is never consulted

On the Pi
Code:
Pi_USB ~ # eval pump --startup
export INCLUDE_SERVER_PID='1074'
export INCLUDE_SERVER_DIR='/tmp/distcc-pump.drasMh'
export INCLUDE_SERVER_PORT='/tmp/distcc-pump.drasMh/socket'
export PATH='/usr/lib/distcc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/armv6j-hardfloat-linux-gnueabi/gcc-bin/4.7.2'


On the helper,
Code:
$ eval pump --startup
/usr/bin/pump: error: pump mode requested, but distcc hosts list does not contain any hosts with ',cpp' option
which is reasonable, as distcc is not set up to distribute builds from there.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sat Dec 22, 2012 9:28 pm    Post subject: Reply with quote

OK, thanks. I am at a total loss to explain my inability to run in pump mode... just so I'm clear, to start at compile on your Pi box, you do or do not run the following first:

Code:
% eval `pump --startup`
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 33919
Location: 56N 3W

PostPosted: Sat Dec 22, 2012 9:32 pm    Post subject: Reply with quote

graysky,

Only set up distcc to distribute work from one system.
Then it clear which is which, so the danger of getting config files mixed up is reduced.

You should be able to make distcc/pump mode work on localhost as the only helper. Its not really useful but may help for testing.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sat Dec 22, 2012 9:50 pm    Post subject: Reply with quote

NeddySeagoon wrote:
You should be able to make distcc/pump mode work on localhost as the only helper. Its not really useful but may help for testing.


Good idea.

Workstation
Code:
%cat /etc/distcc/hosts
localhost/8,lzo,cpp


Code:
% pump --startup         
export INCLUDE_SERVER_PID='20585'
export INCLUDE_SERVER_DIR='/tmp/distcc-pump.7bU7fB'
export INCLUDE_SERVER_PORT='/tmp/distcc-pump.7bU7fB/socket'
export PATH='/usr/lib/distcc/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/facade/bin'


Code:
% pump make -j30 CC=distcc
__________Using distcc-pump from /usr/bin
__________Using 1 distcc server in pump mode
make[1]: Nothing to be done for `all'.
  HOSTCC  scripts/basic/fixdep
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/conmakehash
  HOSTCC  scripts/bin2c
  HOSTCC  scripts/sortextable
...
...
  ZOFFSET arch/x86/boot/zoffset.h
  OBJCOPY arch/x86/boot/vmlinux.bin
  AS      arch/x86/boot/header.o
  LD      arch/x86/boot/setup.elf
  OBJCOPY arch/x86/boot/setup.bin
  BUILD   arch/x86/boot/bzImage
Setup is 15932 bytes (padded to 16384 bytes).
System is 2878 kB
CRC 8b9ad74b
Kernel: arch/x86/boot/bzImage is ready  (#27)
__________Shutting down distcc-pump include server
pump make -j30 CC=distcc  493.21s user 24.08s system 597% cpu 1:26.59 total


So it seems to have worked on the localhost.

Now to add in the helper.

I stop pump:
Code:
% pump --shutdown


NOW.. I add a 2nd line to /etc/distcc/hosts
Code:
localhost/8,lzo,cpp
192.168.0.106/4,lzo,cpp


/usr/bin/distcc sees both in the file:
Code:
% distcc --show-hosts
localhost/8,lzo,cpp
192.168.0.106/4,lzo,cpp


I start up pump:
Code:
% pump --startup         
export INCLUDE_SERVER_PID='1597'
export INCLUDE_SERVER_DIR='/tmp/distcc-pump.wwQrPS'
export INCLUDE_SERVER_PORT='/tmp/distcc-pump.wwQrPS/socket'
export PATH='/usr/lib/distcc/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/facade/bin


Now my old friends the errors are back:
Code:
% pump make -j30 CC=distcc
__________Using distcc-pump from /usr/bin
__________Using 2 distcc servers in pump mode
...
...
distcc[5625] ERROR: compile init/main.c on 192.168.0.106/4,lzo,cpp failed
distcc[5625] (dcc_build_somewhere) Warning: remote compilation of 'init/main.c' failed, retrying locally
distcc[5625] Warning: failed to distribute init/main.c to 192.168.0.106/4,lzo,cpp, running locally instead
  AS      arch/x86/realmode/rm/reboot.o
distcc[5627] ERROR: compile init/do_mounts.c on 192.168.0.106/4,lzo,cpp failed
distcc[5627] (dcc_build_somewhere) Warning: remote compilation of 'init/do_mounts.c' failed, retrying locally
distcc[5627] Warning: failed to distribute init/do_mounts.c to 192.168.0.106/4,lzo,cpp, running locally instead
  AS [M]  arch/x86/crypto/ghash-clmulni-intel_asm.o
distcc[5628] ERROR: compile init/do_mounts_initrd.c on 192.168.0.106/4,lzo,cpp failed
distcc[5628] (dcc_build_somewhere) Warning: remote compilation of 'init/do_mounts_initrd.c' failed, retrying locally
distcc[5628] Warning: failed to distribute init/do_mounts_initrd.c to 192.168.0.106/4,lzo,cpp, running locally instead
distcc[5630] ERROR: compile init/initramfs.c on 192.168.0.106/4,lzo,cpp failed
distcc[5630] (dcc_build_somewhere) Warning: remote compilation of 'init/initramfs.c' failed, retrying locally
distcc[5630] Warning: failed to distribute init/initramfs.c to 192.168.0.106/4,lzo,cpp, running locally instead
  CC [M]  arch/x86/crypto/ghash-clmulni-intel_glue.o
distcc[5625] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'init/main.c' failed, retried locally and got a different result.
distcc[5625] (dcc_please_send_email_after_investigation) Warning: file 'include/generated/bounds.h', a dependency of init/main.c, changed during the build
distcc[5625] (dcc_note_discrepancy) Warning: now using plain distcc, possibly due to inconsistent file system changes during build
distcc[5628] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'init/do_mounts_initrd.c' failed, retried locally and got a different result.
distcc[5628] (dcc_please_send_email_after_investigation) Warning: file 'include/generated/bounds.h', a dependency of init/do_mounts_initrd.c, changed during the build
  CC      arch/x86/kernel/dumpstack_64.o
  CC      arch/x86/kernel/time.o
  CC      arch/x86/kernel/ioport.o
distcc[5627] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'init/do_mounts.c' failed, retried locally and got a different result.
distcc[5627] (dcc_please_send_email_after_investigation) Warning: file 'include/generated/bounds.h', a dependency of init/do_mounts.c, changed during the build
distcc[5630] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'init/initramfs.c' failed, retried locally and got a different result.
distcc[5630] (dcc_please_send_email_after_investigation) Warning: file 'include/generated/bounds.h', a dependency of init/initramfs.c, changed during the build
...
...
__________Warning: 4 pump-mode compilation(s) failed on server, but succeeded locally.
__________Distcc-pump was demoted to plain mode.  See the Distcc Discrepancy Symptoms section in the include_server(1) man page.
__________Shutting down distcc-pump include server
pump make -j30 CC=distcc  356.25s user 17.83s system 501% cpu 1:14.56 total
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sat Dec 22, 2012 10:03 pm    Post subject: Reply with quote

INTERESTING: If I change the hosts file to define the IP address of my localhost it fails:

Code:
% cat /etc/distcc/hosts
192.168.0.101/8,lzo,cpp


Code:
% pump make -j30 CC=distcc 
__________Using distcc-pump from /usr/bin
__________Using 1 distcc server in pump mode
make[1]: Nothing to be done for `all'.
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
make[1]: Nothing to be done for `relocs'.
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  CC      init/version.o
distcc[17860] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
  CC      arch/x86/realmode/init.o
distcc[17913] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
  CC [M]  arch/x86/crypto/ablk_helper.o
distcc[17938] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
  AS [M]  arch/x86/crypto/aes-x86_64-asm_64.o
  CC      arch/x86/ia32/nosyscall.o
distcc[17952] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
  CC      arch/x86/ia32/audit.o
...
...
Kernel: arch/x86/boot/bzImage is ready  (#31)
  LD [M]  arch/x86/crypto/ablk_helper.ko
__________Warning: 4 pump-mode compilation(s) failed on server, but succeeded locally.
__________Distcc-pump was demoted to plain mode.  See the Distcc Discrepancy Symptoms section in the include_server(1) man page.
__________Shutting down distcc-pump include server
pump make -j30 CC=distcc  295.98s user 14.32s system 318% cpu 1:37.35 total


EDIT: This is true whether I use the IP address of the localmachine or if I use the host name of the local machine :/
Back to top
View user's profile Send private message
graysky
Tux's lil' helper
Tux's lil' helper


Joined: 25 Nov 2006
Posts: 117
Location: above the flames and the ashes

PostPosted: Sun Dec 23, 2012 12:38 pm    Post subject: Reply with quote

Turns out there wasn't anything wrong with my setup. I was trying to compile the linux kernel which is known not to compile with pump mode. :oops:

http://code.google.com/p/distcc/issues/detail?id=54

Thanks to all who replied.
Back to top
View user's profile Send private message
Killerchronic
Tux's lil' helper
Tux's lil' helper


Joined: 24 Apr 2007
Posts: 91
Location: UK

PostPosted: Wed Jan 15, 2014 3:27 am    Post subject: Reply with quote

I've been playing with this alot lately as i'm using a OP windows machine running VMWare gentoo to get distcc running properly, colinux was a no go as im on 64bit, cyqwin i spent a bit with but i really don't know the system at all and i know gentoo inside out pretty much. (or should we say alot more than cygwin or even windows :P). Anyway i got this all working without this info, but some of the things posted here are not easy to find. I figured most out for myself, the gentoo wiki's seems to change day by day (and by that i mean there seems to be 100 of them with no info all trying to backup the one that was lost), the best was lost a few years ago. Nothing has come close since. And its a wiki, users add, not just devs, so if the content is not coming even from users, well, there isn't enough users...

This is one of the things thats beginning to bug me, documentation does not exist, bug reports exist, people saying its fixed, but not saying why or how. I love gentoo for its complexity, USE etc, customisable down to the finite detail, but at the same time it seems lately the others having an issue and finding a fix is less than less. I really hope this isn't the install base becoming smaller but at the same time i've gone to virtualisation now, gentoo is fast and becoming the secondary OS because things "just work" on debian and the extreme custom useflags and compiling source for one specific OS is just not needed with the way things are run and even binairies compiled these days.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum