Bug#757794: Error messages should say which host is broken

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#757794: Error messages should say which host is broken

Ian Jackson-11
Package: distcc
Version: 3.1-5
Severity: important

Summary:

The messsage
    ERROR: server provided no answer. Is the server configured to
    allow access from your IP address? Does the server have the
    compiler installed? Is the server configured to access the
    compiler?
(and/or perhaps other relevant messages) should contain the server
hostname and protocol.


One of the hosts in our build cluster is broken:

osstest@army:~$ DISTCC_HOSTS=armpit/4 distcc gcc -Wall -c t.c
distcc[6366] (dcc_readx) ERROR: failed to read: Connection reset by peer
distcc[6366] (dcc_r_token_int) ERROR: read failed while waiting for token "DONE"
distcc[6366] (dcc_r_result_header) ERROR: server provided no answer. Is the server configured to allow access from your IP address? Does the server have the compiler installed? Is the server configured to access the compiler?
distcc[6366] Warning: failed to distribute t.c to armpit/4, running locally instead
osstest@army:~$ DISTCC_HOSTS=armpit/4 distcc gcc -Wall -c t.c
distcc[6372] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
osstest@army:~$ DISTCC_FALLBACK=0 DISTCC_HOSTS=armpit/4 distcc gcc -Wall -c t.c
distcc[6399] (dcc_build_somewhere) Warning: failed to distribute and fallbacks are disabled
osstest@army:~$

There are some problems with these error messages.  This bug report is
(primarily) about the message from the first run above.

None of the output mentions the hostname (`armpit' in this case).  In
a real run with multiple hosts, this means that the error messages
which don't tell you what to investigate.

IMO at least one of these messages should contain the target hostname
(and perhaps the protocol or other details).


Because of the difficulties that this can pose for someone trying to
debug problems (particularly intermittent ones), I have set the
severity to `important'.  I hope that meets with your approval.

Thanks,
Ian.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#757794: Error messages should say which host is broken

Shawn Landden-6
Source: distcc
Followup-For: Bug #757794

You can get the host if you turn on verbose logging with DISTCC_VERBOSE=1

If you still are not satisfied, please send a pull request on GIthub

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Foreign Architectures: armel, armhf

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)