DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=AKPxj7i
	pzF2JGmtOQlDsTjC7QXSXS2n3JQLcA6tslotqq3I+yoOBjXKLI+x574+HptSolnI
	cv3YPFikgr1VHLDjjZtguQr7ObMdeYl3mzDub2cA6AUv3HdMeX7i+hZtTz2TrjOr
	ValviPRuctZHZxKzOHbm+StjSyOAOoGOIri8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <CAALQ5r=2=hY6H4jFSg9y7j6CC9Y3+xdUFSt7GQNZE+hKVcoCpA@mail.gmail.com>
References: <CAMv+u9JcRKFsORXEEXbtKx8VqMFc__LXJBpuaeL9C4pFsCd8HA AT mail DOT gmail DOT com> <CAALQ5r=2=hY6H4jFSg9y7j6CC9Y3+xdUFSt7GQNZE+hKVcoCpA AT mail DOT gmail DOT com>
From: Robert Pendell <shinji+cygwin AT elite-systems DOT org>
Date: Mon, 2 Jun 2014 11:27:56 -0400
Message-ID: <CAAeCd-OwxNtqEksnnH9zE8-=kNsLszLtRr4_7f4dtLpSz8NUtg@mail.gmail.com>
Subject: Re: tmux failed and got the message: failed to connect to server: No error
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

On Mon, Jun 2, 2014 at 4:37 AM, Michael Wild <> wrote:
> Hi Guan-Zhong
>
> The problem is known upstream [1, 2] and I'm also trying to figure out
> which change in the cygwin DLL triggered this issue. I'll post here
> again once I know more.
>
> Michael
>
> [1] http://sourceforge.net/p/tmux/mailman/message/32396655/
> [2] http://sourceforge.net/p/tmux/mailman/message/32400834/
>
> On Sat, May 31, 2014 at 5:29 PM, Guan-Zhong Huang wrote:
>> cygwin-1.7.29-2 is ok.
>> After updating to cygwin-1.7.30-1, I can't start tmux.
>>
>> I find it is because when tmux tries to connect to the unix domain
>> socket that tmux server listens and tmux server hasn't started yet,
>> connect() fails but errno is 0, not "Connection Refused (111)". This
>> causes tmux to exit with error.
>>
>> If you want to reproduce this bug.
>> tmux might work at the first time because the unix domain socket is not created.
>> But after that, tmux will fail due to incorrect errno.
>>
>> Here's the strace I got:
>> cygwin-1.7.30-1:
>>    96 1063224 [main] tmux 4072 cygwin_connect: -1 = connect(5,
>> 0x229780, 24), errno 0
>> cygwin-1.7.29-2:
>>    92 1054064 [main] tmux 3548 cygwin_connect: -1 = connect(5,
>> 0x229780, 24), errno 111
>>
>>
>> Best regads,
>> Guan-Zhong

I took a look and ran through some snapshots.  I remembered a
discussion last month regarding the propogation of socket errors to
dup'd sockets.  It seems the patch (or something commited at the same
time) broke this as on the 4/18 snapshot all works well and it breaks
on the 4/24 snapshot which is the same one that got that last bit
patched.  I do not know if the patch was ever tested as the OP of that
thread never responded from what I can tell.

I tested on x86 only as my x86_64 install is running May 23rd snapshot
and for some reason trying to go to an older snapshot resulted in an
unusable install so I reinstalled my x86 one in order to test the
older snapshot releases.

Thread: https://cygwin.com/ml/cygwin/2014-04/msg00539.html

Robert Pendell
A perfect world is one of chaos.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple