Answering the following questions is a big help:
1.
distcc --version
distcc 3.2rc1 x86_64-redhat-linux-gnu
(protocols 1, 2 and 3) (default port 3632)
built Aug 20 2014 17:26:26
2.
uname -a
Linux builder2 3.18.5-201.fc21.x86_64 #1 SMP Mon Feb 2 21:00:58 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
compiler is irrelivant, but here it is.
gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux
3. Run disccd without being spammed with warnings in system log
4.
distccd is being launched via systemd with an environment file in which
DISTCC_TCP_CORK=0 is set. This is verified by the following
sudo cat /proc/1186/environ
LANG=en_US.UTF-8PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/binHOME=/LOGN
AME=nobodyUSER=nobodySHELL=/sbin/nologinOPTIONS=--verbose --nice 5 --jobs 5
--allow 10.8.0.0/16DISTCC_TCP_CORK=0
5. If you have an example of a compiler invocation that failed, quote it, in
full e.g.:
Jan 30 11:57:36 builder2 distccd[18142]: (dcc_inetd_server) failed to get peer name: Socket operation on non-socket
Jan 30 11:57:36 builder2 distccd[18142]: (tcp_cork_sock) Warning:
setsockopt(corked=1) failed: Socket operation on non-socket
Jan 30 11:57:37 builder2 distccd[18123]: (tcp_cork_sock) Warning:
setsockopt(corked=0) failed: Socket operation on non-socket
Jan 30 11:57:37 builder2 distccd[18123]: (dcc_job_summary) client: NOTSOCKET
COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4282ms
/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin/arm-linux-gnu
eabihf-g++ SOURCE-FILE.cpp
Jan 30 11:57:37 builder2 sshd[18122]: Received disconnect from 10.8.116.198:
11: disconnected by user
6. What error logging do you get? Turn on client and server error logging. On
the client, set these environment variables, and try to reproduce the problem:
=export DISTCC_VERBOSE=1 DISTCC_LOG=/tmp/distcc.log=. Start the server with
the --verbose option. If the problem is intermittent, leave logging enabled and
then pull out the lines from the log file when the problem recurs.
7. If you got an error message on stderr, quote that error exactly. Find the
lines in the log files pertaining to the compile, and include all of them in
your report, by looking at the process ID in square brackets. If you can't work
that out, quote the last few hundred lines leading up to the failure.
Original issue reported on code.google.com by Smith.Ja...@gmail.com on 17 Feb 2015 at 11:54
Original issue reported on code.google.com by
Smith.Ja...@gmail.comon 17 Feb 2015 at 11:54