tmux failed and got the message: failed to connect to server: No error

tmux failed and got the message: failed to connect to server: No error

[Guan-Zhong Huang]

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

--
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

Re: tmux failed and got the message: failed to connect to server: No error

[Michael Wild]

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
>
> --
> 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
>

--
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

Re: tmux failed and got the message: failed to connect to server: No error

[Robert Pendell]

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

Re: tmux failed and got the message: failed to connect to server: No error

[Michael Wild]

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

Re: tmux failed and got the message: failed to connect to server: No error

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

On Jun  2 11:27, 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.

Yes, indeed.  The patch was supposed to fix the problem with the
SOL_SOCKET/SO_ERROR valus not being set when calling select on a
duplicated socket.

I just gave it a try and it turned out that the Winsock call setsockopt
sets the last WSA error code to 0 in case of success (grrr!), which I
didn't notice when applying the original patch, sorry.

I applied a patch to CVS which should fix the issue by simply calling
WSASetLastError after calling setsockopt.  The original SO_ERROR
testcase still works for me, and a faild connect attempt now returns an
ECONNREFUSED as expected.

I'll generate a new snapshot later today.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: tmux failed and got the message: failed to connect to server: No error

[Henry S. Thompson]

Corinna Vinschen writes:

> [Corinna is BACK!]
>
> I'll generate a new snapshot later today.

Hope you had a great holiday!  You were missed.

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
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

Re: tmux failed and got the message: failed to connect to server: No error

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

On Jun 16 17:08, Henry S. Thompson wrote:
> Corinna Vinschen writes:
> 
> > [Corinna is BACK!]
> >
> > I'll generate a new snapshot later today.
> 
> Hope you had a great holiday!  You were missed.

Holiday was great, thank you.

And the snapshot is up now.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: tmux failed and got the message: failed to connect to server: No error

[Robert Pendell]

On Mon, Jun 16, 2014 at 12:23 PM, Corinna Vinschen wrote:
> On Jun 16 17:08, Henry S. Thompson wrote:
>> Corinna Vinschen writes:
>>
>> > [Corinna is BACK!]
>> >
>> > I'll generate a new snapshot later today.
>>
>> Hope you had a great holiday!  You were missed.
>
> Holiday was great, thank you.
>
> And the snapshot is up now.
>
>

I just tested the 6/16 snapshot and tmux appears to be working for me now.

--
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

Re: tmux failed and got the message: failed to connect to server: No error

[Michael Wild]

On Tue, Jun 17, 2014 at 4:48 PM, Robert Pendell wrote:
> On Mon, Jun 16, 2014 at 12:23 PM, Corinna Vinschen wrote:
>> On Jun 16 17:08, Henry S. Thompson wrote:
>>> Corinna Vinschen writes:
>>>
>>> > [Corinna is BACK!]
>>> >
>>> > I'll generate a new snapshot later today.
>>>
>>> Hope you had a great holiday!  You were missed.
>>
>> Holiday was great, thank you.
>>
>> And the snapshot is up now.
>>
>>
>
> I just tested the 6/16 snapshot and tmux appears to be working for me now.
>

Which version of tmux? I uploaded 1.9a-2 with a patch recently:
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