Processed: Re: Bug#851877: fails every time

2017-05-14 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs) Severity set to 'important' from 'serious' -- 851877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#851877: fails every time

2017-05-14 Thread Adam Borowski
Control: severity -1 important On Mon, May 15, 2017 at 01:52:09AM +0200, Guillaume Delacour wrote: > Le 15/05/2017 à 00:50, Adam Borowski a écrit : > > So it's a fully _reproducible_ bug, with a well-defined immediate cause > > (even if we haven't identified the indirect cause yet) -- unlike the >

Bug#851877: fails every time

2017-05-14 Thread Guillaume Delacour
Hi, Le 15/05/2017 à 00:50, Adam Borowski a écrit : > > So it's a fully _reproducible_ bug, with a well-defined immediate cause > (even if we haven't identified the indirect cause yet) -- unlike the > original report by Santiago Villa. Thus, it looks we have two different > bugs that just happen

Bug#851877: fails every time

2017-05-14 Thread Adam Borowski
On Sun, May 14, 2017 at 10:37:17PM +0200, Michael Stapelberg wrote: > On Sun, May 14, 2017 at 7:59 AM, Adam Borowski wrote: > > > Use: gcc -Wall -o gai gai.c && ./gai localhost 9002 > > > > On all three machines, it looks fine: > > ai_family = 10 > > host=::1, serv=9002 > > ai_family = 2 >

Bug#851877: fails every time

2017-05-14 Thread Michael Stapelberg
On Sun, May 14, 2017 at 7:59 AM, Adam Borowski wrote: > On Sat, May 13, 2017 at 08:44:15PM +0200, Michael Stapelberg wrote: > > Sorry for the late reply. > > > > Adam, could you run the attached example program (derived from the > > getaddrinfo and getnameinfo manpages) please? The output should

Bug#851877: fails every time

2017-05-13 Thread Adam Borowski
On Sat, May 13, 2017 at 08:44:15PM +0200, Michael Stapelberg wrote: > Sorry for the late reply. > > Adam, could you run the attached example program (derived from the > getaddrinfo and getnameinfo manpages) please? The output should help us > narrow down whether the problem is with the application

Bug#851877: fails every time

2017-05-13 Thread Michael Stapelberg
Sorry for the late reply. Adam, could you run the attached example program (derived from the getaddrinfo and getnameinfo manpages) please? The output should help us narrow down whether the problem is with the application code of sslh or something in the environment. Use: gcc -Wall -o gai gai.c &&

Bug#851877: fails every time

2017-05-09 Thread Guillaume Delacour
Hi, On Sat, 6 May 2017 20:57:44 +0200 Adam Borowski wrote: > On Sat, May 06, 2017 at 08:00:11PM +0200, Michael Stapelberg wrote: > > Thanks. It seems like getaddrinfo() is returning two results when resolving > > localhost. Can you provide the contents of your hostname resolution-related > > conf

Bug#851877: fails every time

2017-05-06 Thread Adam Borowski
On Sat, May 06, 2017 at 08:00:11PM +0200, Michael Stapelberg wrote: > Thanks. It seems like getaddrinfo() is returning two results when resolving > localhost. Can you provide the contents of your hostname resolution-related > configuration please? I.e., /etc/hosts, /etc/resolv.conf, > /etc/nsswitch

Bug#851877: fails every time

2017-05-06 Thread Michael Stapelberg
Thanks. It seems like getaddrinfo() is returning two results when resolving localhost. Can you provide the contents of your hostname resolution-related configuration please? I.e., /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, anything else you might have tweaked in that area. On Sat, May 6, 20

Bug#851877: fails every time

2017-05-06 Thread Michael Stapelberg
Thanks for the strace. We can see that sslh creates two sockets of the same address family, on the same host and port: […] [pid 23812] socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 3 [pid 23812] setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 [pid 23812] setsockopt(3, SOL_IP, IP_FREEBIND, [1], 4)

Bug#851877: fails every time

2017-05-06 Thread Michael Stapelberg
On Sat, May 6, 2017 at 4:02 PM, Adam Borowski wrote: > On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote: > > I pushed a commit adding a patch which fixes the test by picking an > > unused port. The mechanism is not atomic (i.e., the port is picked by > > the test process, as opp

Bug#851877: fails every time

2017-05-06 Thread Adam Borowski
On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote: > I pushed a commit adding a patch which fixes the test by picking an > unused port. The mechanism is not atomic (i.e., the port is picked by > the test process, as opposed to the listening process itself and > communicated back to

Bug#851877: fails every time

2017-05-06 Thread Adam Borowski
On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote: > Tomasz Buchert writes: > > On 04/05/17 04:47, Adam Borowski wrote: > >> [...] > > > > I cannot reproduce these failures. I've built in my stretch sbuild > > around 15 times, and succedeed every time. I found just one of my mach

Bug#851877: fails every time

2017-05-06 Thread Michael Stapelberg
control: tags -1 + pending Hi, Tomasz Buchert writes: > On 04/05/17 04:47, Adam Borowski wrote: >> [...] > > I cannot reproduce these failures. I've built in my stretch sbuild > around 15 times, and succedeed every time. > > I use: > gbp buildpackage --git-builder='sbuild --source-only-changes -

Bug#851877: fails every time

2017-05-05 Thread Tomasz Buchert
On 04/05/17 04:47, Adam Borowski wrote: > [...] I cannot reproduce these failures. I've built in my stretch sbuild around 15 times, and succedeed every time. I use: gbp buildpackage --git-builder='sbuild --source-only-changes -v -As --build-dep-resolver=apt --dist=stretch -j4' "$@" Tomasz sig