sshd crashing

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

sshd crashing

Pawel Jasinski
hi,

I have a fresh installation of cygwin on xp and win7 (both run 1.17.16-1).
I have run ssh-host-config followed by rebaseall. The CYGWIN variable
for sshd is not set.
I have tried with and without priv. separation.
It is started with cygrunsrv -S sshd
I can connect with ssh localhost. Things are ok until I do vi
/etc/profile. At this moment it crashes.

Now if I try the version without priv separation to start by hand:
/usr/sbin/sshd -D -d -e things go well and it does not crashes when in
ssh session /etc/profile is edited.
Am I missing something in config?

--pawel

Info from Event Viewer:

The description for Event ID 0 from source sshd cannot be found.
Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or
repair the component on the local computer.

If the event originated on another computer, the display information
had to be saved with the event.

The following information was included with the event:

sshd: PID 484: service `sshd' failed: signal 11 raised

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

cygcheck (76K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Reini Urban
On Fri, Jul 27, 2012 at 4:44 PM, Pawel Jasinski wrote:

> I have a fresh installation of cygwin on xp and win7 (both run 1.17.16-1).
> I have run ssh-host-config followed by rebaseall. The CYGWIN variable
> for sshd is not set.
> I have tried with and without priv. separation.
> It is started with cygrunsrv -S sshd
> I can connect with ssh localhost. Things are ok until I do vi
> /etc/profile. At this moment it crashes.
>
> Now if I try the version without priv separation to start by hand:
> /usr/sbin/sshd -D -d -e things go well and it does not crashes when in
> ssh session /etc/profile is edited.
> Am I missing something in config?

Inspect /var/log/sshd.log for obvious rebase errors and run rebaseall then.
I fixed the same problem this way.

> sshd: PID 484: service `sshd' failed: signal 11 raised
--
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Pawel Jasinski
as I said I did rebaseall :-(
In a mean time I also tried with CYGWIN=pipe_byte, no change
At the moment of crash there is nothing new in the /var/log/sshd.log

--pawel


On Sat, Jul 28, 2012 at 12:52 AM, Reini Urban <[hidden email]> wrote:

> On Fri, Jul 27, 2012 at 4:44 PM, Pawel Jasinski wrote:
>> I have a fresh installation of cygwin on xp and win7 (both run 1.17.16-1).
>> I have run ssh-host-config followed by rebaseall. The CYGWIN variable
>> for sshd is not set.
>> I have tried with and without priv. separation.
>> It is started with cygrunsrv -S sshd
>> I can connect with ssh localhost. Things are ok until I do vi
>> /etc/profile. At this moment it crashes.
>>
>> Now if I try the version without priv separation to start by hand:
>> /usr/sbin/sshd -D -d -e things go well and it does not crashes when in
>> ssh session /etc/profile is edited.
>> Am I missing something in config?
>
> Inspect /var/log/sshd.log for obvious rebase errors and run rebaseall then.
> I fixed the same problem this way.
>
>> sshd: PID 484: service `sshd' failed: signal 11 raised
> --
> Reini Urban
> http://cpanel.net/   http://www.perl-compiler.org/
>
> --
> 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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Christopher Faylor-8
On Sat, Jul 28, 2012 at 01:04:47AM +0200, Pawel Jasinski wrote:
>as I said I did rebaseall :-(
>In a mean time I also tried with CYGWIN=pipe_byte, no change
>At the moment of crash there is nothing new in the /var/log/sshd.log

Oh boy.  "CYGWIN=pipe_byte" will now become the voodoo fix for the masses.
I should have seen that one coming.

For the record, there is absolutely no reason to use pipe_byte with Cygwin
programs.

cgf

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Pawel Jasinski
In reply to this post by Reini Urban
hi,

So I did the core dump homework ...
I can find the sshd.exe.stacktrace in /
It is not encouraging:

Exception: STATUS_ACCESS_VIOLATION at eip=00000000
eax=FFFFFFFF ebx=00000000 ecx=0022D000 edx=00000004 esi=FFFFFFFF edi=0022A280
ebp=0000010C esp=0022A230 program=C:\cygwin\usr\sbin\sshd.exe, pid
3504, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
      5 [main] sshd 3504 exception::handle: Error while dumping state
(probably corrupted stack)


I also tried to core dump with:
/usr/bin/cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a "-D"
-y tcpip -u cyg_server -w xxxxxx  -e CYGWIN="error_start=dumper -d %1
%2"

The file is there (/sshd.exe.core), but again gdb doesn't show any
encouraging information:


$ gdb /usr/sbin/sshd.exe sshd.exe.core
GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-cygwin".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/sshd.exe...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New Thread 0x1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
[New process 1]
#0  0x00000000 in ?? ()
(gdb) where
#0  0x00000000 in ?? ()
#1  0x0022a280 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Larry Hall (Cygwin)
On 7/28/2012 5:27 AM, Pawel Jasinski wrote:

<snip>

> I also tried to core dump with:
> /usr/bin/cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a "-D"
> -y tcpip -u cyg_server -w xxxxxx  -e CYGWIN="error_start=dumper -d %1
> %2"
>
> The file is there (/sshd.exe.core), but again gdb doesn't show any
> encouraging information:
>
>
> $ gdb /usr/sbin/sshd.exe sshd.exe.core
> GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-cygwin".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/sbin/sshd.exe...(no debugging symbols found)...done.
                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^
Without debug symbols, you're not going to see much useful in the debugger.
I'd recommend rebuilding the package as debug and trying again.

--
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?


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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Ryan Johnson-10
In reply to this post by Christopher Faylor-8
On 27/07/2012 10:18 PM, Christopher Faylor wrote:
> On Sat, Jul 28, 2012 at 01:04:47AM +0200, Pawel Jasinski wrote:
>> as I said I did rebaseall :-(
>> In a mean time I also tried with CYGWIN=pipe_byte, no change
>> At the moment of crash there is nothing new in the /var/log/sshd.log
> Oh boy.  "CYGWIN=pipe_byte" will now become the voodoo fix for the masses.
> I should have seen that one coming.
>
> For the record, there is absolutely no reason to use pipe_byte with Cygwin
> programs.
FAQ entry? It might work to have documentation for each CYGWIN= value
that says specifically what it will *not* do. For example, pipe_byte
will *not do anything* for cygwin programs, ttysec will *not do
anything* at all, etc. Added bonus: a link for google to point the
masses at that's *not* a third-party cygwin support page filled with out
of date voodoo.

Ryan


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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Pawel Jasinski
In reply to this post by Larry Hall (Cygwin)
hi,

I have already tried. So my first step is to recompile sshd without
any changes (adding debug etc.)
As far as I can tell from documentation, sshd is type 3, covered by
cygport tool.
So I did:

$ cygport /usr/src/openssh-6.0p1-2.cygport prep
>>> Preparing openssh-6.0p1-2
*** Info: gnupg must be installed in order to check signatures.
>>> Unpacking source openssh-6.0p1.tar.gz
>>> Preparing working source directory
*** Info: applying patch openssh-6.0p1-2.cygwin.patch:
patching file CYGWIN-PATCHES/setup.hint
*** Info: applying patch openssh-6.0p1-2.src.patch:

things are ok until now. If I should do anything else, please tell me.

now step 2:

$ cygport /usr/src/openssh-6.0p1-2.cygport compile
>>> Compiling openssh-6.0p1-2
/usr/src/openssh-6.0p1-2/src/openssh-6.0p1/configure
--srcdir=/usr/src/openssh-6.0p1-2/src/openssh-6.0p1 --prefix=/usr
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/lib --datadir=/usr/share --localstatedir=/var
--sysconfdir=/etc --datarootdir=/usr/share
--docdir=/usr/share/doc/openssh -C --libexecdir=/usr/sbin
--with-kerberos5=/usr --with-tcp-wrappers --with-libedit
--with-xauth=/usr/bin/xauth
configure: loading cache config.cache
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/usr/src/openssh-6.0p1-2/build':
configure: error: C compiler cannot create executables
See `config.log' for more details
*** ERROR: configure failed

If I look at config,log the things look funny around gcc invocation,
but I am kind of novice to cygport and can not figure out what's going
on:

gcc -ggdb -O2 -pipe
-fdebug-prefix-map=/usr/src/openssh-6.0p1-2/build=/usr/src/debug/openssh-6.0p1-2
-fdebug-prefix-ma
p=/usr/src/openssh-6.0p1-2/src/openssh-6.0p1=/usr/src/debug/openssh-6.0p1-2
  conftest.c  >&5
cc1: error: unrecognized command line option
"-fdebug-prefix-map=/usr/src/openssh-6.0p1-2/build=/usr/src/debug/openssh-6.0p1-2"
cc1: error: unrecognized command line option
"-fdebug-prefix-map=/usr/src/openssh-6.0p1-2/src/openssh-6.0p1=/usr/src/debug/openssh-6.0

What am I missing?

Cheers,
Pawel

On Mon, Jul 30, 2012 at 4:13 PM, Larry Hall (Cygwin) <your spam filter
complains about it> wrote:

> On 7/28/2012 5:27 AM, Pawel Jasinski wrote:
>
> <snip>
>
>
>> I also tried to core dump with:
>> /usr/bin/cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a "-D"
>> -y tcpip -u cyg_server -w xxxxxx  -e CYGWIN="error_start=dumper -d %1
>> %2"
>>
>> The file is there (/sshd.exe.core), but again gdb doesn't show any
>> encouraging information:
>>
>>
>> $ gdb /usr/sbin/sshd.exe sshd.exe.core
>> GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
>> Copyright (C) 2011 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "i686-cygwin".
>> For bug reporting instructions, please see:
>> <http://www.gnu.org/software/gdb/bugs/>...
>> Reading symbols from /usr/sbin/sshd.exe...(no debugging symbols
>> found)...done.
>
>                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^
> Without debug symbols, you're not going to see much useful in the debugger.
> I'd recommend rebuilding the package as debug and trying again.
>
> --
> Larry
>

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

A Lichner
In reply to this post by Pawel Jasinski
Hello,

I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to be limited to VMWare guests in my case. Any write attempt within the /etc directory causes sshd to crash. Other directories are fine.

uname -a before upgrade (sshd doens't crash):
CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
and after upgrade (sshd crashes):
CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin


cygrunsrv -S sshd
ssh localhost
$ touch /etc/x
Connection to localhost closed by remote host.
Connection to localhost closed.


A familiar message appears in the event log:
service sshd failed: signal 11 raised 

The /etc/x file gets created in the example above. If running vim /etc/x instead, the  .x.swp file gets also created and a vim-nox.exe process keeps on living, taking all CPU resources till it's killed.

I have reproduced this on over ten machines running MS Server 2003 and 2008, all VMware guests.

Ales

pawel.jasinski wrote
hi,

I have a fresh installation of cygwin on xp and win7 (both run 1.17.16-1).
I have run ssh-host-config followed by rebaseall. The CYGWIN variable
for sshd is not set.
I have tried with and without priv. separation.
It is started with cygrunsrv -S sshd
I can connect with ssh localhost. Things are ok until I do vi
/etc/profile. At this moment it crashes.

Now if I try the version without priv separation to start by hand:
/usr/sbin/sshd -D -d -e things go well and it does not crashes when in
ssh session /etc/profile is edited.
Am I missing something in config?

--pawel

Info from Event Viewer:

The description for Event ID 0 from source sshd cannot be found.
Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or
repair the component on the local computer.

If the event originated on another computer, the display information
had to be saved with the event.

The following information was included with the event:

sshd: PID 484: service `sshd' failed: signal 11 raised

 
--
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
Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Corinna Vinschen-2
On Jul 30 17:49, Aleš wrote:

>
> Hello,
>
> I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to
> be limited to VMWare guests in my case. Any write attempt within the /etc
> directory causes sshd to crash. Other directories are fine.
>
> uname -a before upgrade (sshd doens't crash):
> CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
> and after upgrade (sshd crashes):
> CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
>
>
> cygrunsrv -S sshd
> ssh localhost
> $ touch /etc/x
> Connection to localhost closed by remote host.
> Connection to localhost closed.
>
>
> A familiar message appears in the event log:
> service sshd failed: signal 11 raised
>
> The /etc/x file gets created in the example above. If running vim /etc/x
> instead, the  .x.swp file gets also created and a vim-nox.exe process keeps
> on living, taking all CPU resources till it's killed.
>
> I have reproduced this on over ten machines running MS Server 2003 and 2008,
> all VMware guests.

I can reproduce this as well.  I also found the patch which introduced
the problem, but it's not clear yet, why.  Stay tuned.


Corinna

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

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Reini Urban
In reply to this post by Pawel Jasinski
On Mon, Jul 30, 2012 at 5:50 PM, Pawel Jasinski wrote:

> checking for gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/usr/src/openssh-6.0p1-2/build':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> *** ERROR: configure failed
>
> If I look at config,log the things look funny around gcc invocation,
> but I am kind of novice to cygport and can not figure out what's going
> on:
>
> gcc -ggdb -O2 -pipe
> -fdebug-prefix-map=/usr/src/openssh-6.0p1-2/build=/usr/src/debug/openssh-6.0p1-2
> -fdebug-prefix-ma
> p=/usr/src/openssh-6.0p1-2/src/openssh-6.0p1=/usr/src/debug/openssh-6.0p1-2
>   conftest.c  >&5
> cc1: error: unrecognized command line option
> "-fdebug-prefix-map=/usr/src/openssh-6.0p1-2/build=/usr/src/debug/openssh-6.0p1-2"
> cc1: error: unrecognized command line option
> "-fdebug-prefix-map=/usr/src/openssh-6.0p1-2/src/openssh-6.0p1=/usr/src/debug/openssh-6.0
>
> What am I missing?

You are using gcc (version 3) and not gcc4.
--
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Corinna Vinschen-2
In reply to this post by Corinna Vinschen-2
On Jul 31 14:28, Corinna Vinschen wrote:

> On Jul 30 17:49, Aleš wrote:
> >
> > Hello,
> >
> > I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to
> > be limited to VMWare guests in my case. Any write attempt within the /etc
> > directory causes sshd to crash. Other directories are fine.
> >
> > uname -a before upgrade (sshd doens't crash):
> > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
> > and after upgrade (sshd crashes):
> > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
> >
> >
> > cygrunsrv -S sshd
> > ssh localhost
> > $ touch /etc/x
> > Connection to localhost closed by remote host.
> > Connection to localhost closed.
> >
> >
> > A familiar message appears in the event log:
> > service sshd failed: signal 11 raised
> >
> > The /etc/x file gets created in the example above. If running vim /etc/x
> > instead, the  .x.swp file gets also created and a vim-nox.exe process keeps
> > on living, taking all CPU resources till it's killed.
> >
> > I have reproduced this on over ten machines running MS Server 2003 and 2008,
> > all VMware guests.
>
> I can reproduce this as well.  I also found the patch which introduced
> the problem, but it's not clear yet, why.  Stay tuned.

I've just applied a patch to fix this problem.  It seems this is a long
standing bug which could result in random stack corruption after changing
or adding any file to /etc.  I'm just generating a developer snapshot.
Please test the today's snapshot from http://cygwin.com/snapshots/
Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.


Thanks in advance,
Corinna

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

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Pawel Jasinski
hi,

the fix works, I have tested it with the only vm I have with me.

thanks
pawel

On Tue, Jul 31, 2012 at 10:19 PM, Corinna Vinschen <corinna-cygwin at
cygwin.com> wrote:

> On Jul 31 14:28, Corinna Vinschen wrote:
>> On Jul 30 17:49, Aleš wrote:
>> >
>> > Hello,
>> >
>> > I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to
>> > be limited to VMWare guests in my case. Any write attempt within the /etc
>> > directory causes sshd to crash. Other directories are fine.
>> >
>> > uname -a before upgrade (sshd doens't crash):
>> > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
>> > and after upgrade (sshd crashes):
>> > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
>> >
>> >
>> > cygrunsrv -S sshd
>> > ssh localhost
>> > $ touch /etc/x
>> > Connection to localhost closed by remote host.
>> > Connection to localhost closed.
>> >
>> >
>> > A familiar message appears in the event log:
>> > service sshd failed: signal 11 raised
>> >
>> > The /etc/x file gets created in the example above. If running vim /etc/x
>> > instead, the  .x.swp file gets also created and a vim-nox.exe process keeps
>> > on living, taking all CPU resources till it's killed.
>> >
>> > I have reproduced this on over ten machines running MS Server 2003 and 2008,
>> > all VMware guests.
>>
>> I can reproduce this as well.  I also found the patch which introduced
>> the problem, but it's not clear yet, why.  Stay tuned.
>
> I've just applied a patch to fix this problem.  It seems this is a long
> standing bug which could result in random stack corruption after changing
> or adding any file to /etc.  I'm just generating a developer snapshot.
> Please test the today's snapshot from http://cygwin.com/snapshots/
> Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.
>
>
> Thanks in advance,
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
>
> --
> 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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

A Lichner
In reply to this post by Corinna Vinschen-2
Thanks Corinna. The fix works.
Ales

Corinna Vinschen-2 wrote
On Jul 31 14:28, Corinna Vinschen wrote:
> On Jul 30 17:49, Aleš wrote:
> >
> > Hello,
> >
> > I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to
> > be limited to VMWare guests in my case. Any write attempt within the /etc
> > directory causes sshd to crash. Other directories are fine.
> >
> > uname -a before upgrade (sshd doens't crash):
> > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
> > and after upgrade (sshd crashes):
> > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
> >
> >
> > cygrunsrv -S sshd
> > ssh localhost
> > $ touch /etc/x
> > Connection to localhost closed by remote host.
> > Connection to localhost closed.
> >
> >
> > A familiar message appears in the event log:
> > service sshd failed: signal 11 raised
> >
> > The /etc/x file gets created in the example above. If running vim /etc/x
> > instead, the  .x.swp file gets also created and a vim-nox.exe process keeps
> > on living, taking all CPU resources till it's killed.
> >
> > I have reproduced this on over ten machines running MS Server 2003 and 2008,
> > all VMware guests.
>
> I can reproduce this as well.  I also found the patch which introduced
> the problem, but it's not clear yet, why.  Stay tuned.

I've just applied a patch to fix this problem.  It seems this is a long
standing bug which could result in random stack corruption after changing
or adding any file to /etc.  I'm just generating a developer snapshot.
Please test the today's snapshot from http://cygwin.com/snapshots/
Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.


Thanks in advance,
Corinna

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

--
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
Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Corinna Vinschen-2
On Jul 31 15:59, A Lichner wrote:

>
> Thanks Corinna. The fix works.
> Ales
>
>
> Corinna Vinschen-2 wrote:
> >
> > On Jul 31 14:28, Corinna Vinschen wrote:
> >> On Jul 30 17:49, Aleš wrote:
> >> >
> >> > Hello,
> >> >
> >> > I can confirm the issue. It's occurring after upgrade to 1.7.16 and
> >> seems to
> >> > be limited to VMWare guests in my case. Any write attempt within the
> >> /etc
> >> > directory causes sshd to crash. Other directories are fine.
> >> >
> >> > uname -a before upgrade (sshd doens't crash):
> >> > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
> >> > and after upgrade (sshd crashes):
> >> > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
> >> >
> >> >
> >> > cygrunsrv -S sshd
> >> > ssh localhost
> >> > $ touch /etc/x
> >> > Connection to localhost closed by remote host.
> >> > Connection to localhost closed.
> >> >
> >> >
> >> > A familiar message appears in the event log:
> >> > service sshd failed: signal 11 raised
> >> >
> >> > The /etc/x file gets created in the example above. If running vim
> >> /etc/x
> >> > instead, the  .x.swp file gets also created and a vim-nox.exe process
> >> keeps
> >> > on living, taking all CPU resources till it's killed.
> >> >
> >> > I have reproduced this on over ten machines running MS Server 2003 and
> >> 2008,
> >> > all VMware guests.
> >>
> >> I can reproduce this as well.  I also found the patch which introduced
> >> the problem, but it's not clear yet, why.  Stay tuned.
> >
> > I've just applied a patch to fix this problem.  It seems this is a long
> > standing bug which could result in random stack corruption after changing
> > or adding any file to /etc.  I'm just generating a developer snapshot.
> > Please test the today's snapshot from http://cygwin.com/snapshots/
> > Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.

Thanks to you and Pawel for your feedback.


Corinna

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

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Corinna Vinschen-2
On Aug  1 09:02, Corinna Vinschen wrote:

> On Jul 31 15:59, A Lichner wrote:
> >
> > Thanks Corinna. The fix works.
> > Ales
> > [...]
> > Corinna Vinschen-2 wrote:
> > > I've just applied a patch to fix this problem.  It seems this is a long
> > > standing bug which could result in random stack corruption after changing
> > > or adding any file to /etc.  I'm just generating a developer snapshot.
> > > Please test the today's snapshot from http://cygwin.com/snapshots/
> > > Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.
>
> Thanks to you and Pawel for your feedback.

I've just uploaded another snapshot.  Can you please test this one as
well?


Thanks,
Corinna

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

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

A Lichner
The cygwin1.dll from the latest snapshot is fine too - sshd doesn't crash when writing to /etc folder.
$ uname -a
CYGWIN_NT-6.0-WOW64 dbs14 1.7.17s(0.262/5/3) 20120801 11:02:01 i686 Cygwin

Corinna Vinschen-2 wrote
On Aug  1 09:02, Corinna Vinschen wrote:

I've just uploaded another snapshot.  Can you please test this one as
well?
Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

Corinna Vinschen-2
On Aug  1 21:44, A Lichner wrote:

>
> The cygwin1.dll from the latest snapshot is fine too - sshd doesn't crash
> when writing to /etc folder.
> $ uname -a
> CYGWIN_NT-6.0-WOW64 dbs14 1.7.17s(0.262/5/3) 20120801 11:02:01 i686 Cygwin
>
>
> Corinna Vinschen-2 wrote:
> >
> > On Aug  1 09:02, Corinna Vinschen wrote:
> >
> > I've just uploaded another snapshot.  Can you please test this one as
> > well?

Thanks again for the feedback.


Corinna

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

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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

bourne
In reply to this post by Corinna Vinschen-2
Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

----------------------- SNIPPET ---------------------------

> >
> > I can reproduce this as well.  I also found the patch which introduced
> > the problem, but it's not clear yet, why.  Stay tuned.
>
> I've just applied a patch to fix this problem.  It seems this is a long
> standing bug which could result in random stack corruption after changing
> or adding any file to /etc.  I'm just generating a developer snapshot.
> Please test the today's snapshot from http://cygwin.com/snapshots/
> Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.
>
> Thanks in advance,
> Corinna
>


Hey,

Just wanted to thank you guys for this fix.
I had this issue on an install I did and it was driving me nuts as I couldn't
find the issue.
This fixed things up perfectly!!

Cheers


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

Reply | Threaded
Open this post in threaded view
|

Re: sshd crashing

The love dada
I too would like to thank those who fixed this issue. I had the same problem on Windows 7 but not only with sshd, also with rxvt exiting unexpectedly whenever I accessed files under /etc. All fine with todays snapshot cywin1.dll.