This is the mail archive of the
mailing list for the Cygwin project.
Re: tmux failed and got the message: failed to connect to server: No error
- From: Michael Wild <themiwi at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 6 Jun 2014 07:22:07 +0200
- Subject: Re: tmux failed and got the message: failed to connect to server: No error
- Authentication-results: sourceware.org; auth=none
- References: <CAMv+u9JcRKFsORXEEXbtKx8VqMFc__LXJBpuaeL9C4pFsCd8HA at mail dot gmail dot com> <CAALQ5r=2=hY6H4jFSg9y7j6CC9Y3+xdUFSt7GQNZE+hKVcoCpA at mail dot gmail dot com> <CAAeCd-OwxNtqEksnnH9zE8-=kNsLszLtRr4_7f4dtLpSz8NUtg at mail dot gmail dot com>
On Mon, Jun 2, 2014 at 5:27 PM, Robert Pendell wrote:
> 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.
>>  http://sourceforge.net/p/tmux/mailman/message/32396655/
>>  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:
>>> 96 1063224 [main] tmux 4072 cygwin_connect: -1 = connect(5,
>>> 0x229780, 24), errno 0
>>> 92 1054064 [main] tmux 3548 cygwin_connect: -1 = connect(5,
>>> 0x229780, 24), errno 111
>>> Best regads,
> 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.
Yesterday I uploaded tmux-1.9a-2 which papers over this issue:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple