From: Michael Wild <themiwi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: tmux failed and got the message: failed to connect to server: No error
Date: Fri, 06 Jun 2014 05:22:00 -0000 [thread overview]
Message-ID: <CAALQ5rm6XmxNMeajo88hvQBWpULSOrC-P=fRJ2Wc-_kj51T2cg@mail.gmail.com> (raw)
In-Reply-To: <CAAeCd-OwxNtqEksnnH9zE8-=kNsLszLtRr4_7f4dtLpSz8NUtg@mail.gmail.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.
>>
>> 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.
Yesterday I uploaded tmux-1.9a-2 which papers over this issue:
https://cygwin.com/ml/cygwin-apps/2014-06/msg00018.html
Michael
--
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
next prev parent reply other threads:[~2014-06-06 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 18:34 Guan-Zhong Huang
2014-06-02 8:38 ` Michael Wild
2014-06-02 15:28 ` Robert Pendell
2014-06-06 5:22 ` Michael Wild [this message]
2014-06-16 13:11 ` Corinna Vinschen
2014-06-16 16:08 ` Henry S. Thompson
2014-06-16 16:23 ` Corinna Vinschen
2014-06-17 14:49 ` Robert Pendell
2014-06-18 7:25 ` Michael Wild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAALQ5rm6XmxNMeajo88hvQBWpULSOrC-P=fRJ2Wc-_kj51T2cg@mail.gmail.com' \
--to=themiwi@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).