[Bug 121] New: ssh hangs on exit (not damon, nor background)

[Joshua Mehlman]

Sorry it took so long to get back (it is much eayser to test for it with a
client change). But I have been able to reproduce 3 times in the past 4h
without the pach and 0 with. Thanks much and sorry for not thinging that
this was the problem that I was seeing. The discription was pritty old and
looked a little different to me.
I assume that this patch will be in the next rel?

                           -----------------------
                            Joshua B. Mehlman
                            Systems Administrator
                            Morgan Stanley Online
                           -----------------------

On Tue, 19 Feb 2002, Nicolas Williams wrote:

> This sounds like the SIGCHLD race bug.
>
> Check if the sshd has a defunct child when hanging - if so, send SIGCHLD
> to the sshd and watch the connection close.
>
> Search the list. Patches have been posted.
>
> Cheers,
>
> Nico
>
>
> On Wed, Feb 20, 2002 at 08:24:45AM +1100, bugzilla-daemon at mindrot.org wrote:
> > http://bugzilla.mindrot.org/show_bug.cgi?id=121
> >
> >            Summary: ssh hangs on exit (not damon, nor background)
> >            Product: Portable OpenSSH
> >            Version: 3.0.2p1
> >           Platform: Other
> >         OS/Version: other
> >             Status: NEW
> >           Severity: normal
> >           Priority: P2
> >          Component: ssh
> >         AssignedTo: openssh-unix-dev at mindrot.org
> >         ReportedBy: joshua.mehlman at morganstanley.com
> >
> >
> > ssh running on Solaris 2.8 ocasionaly hangs on exit. I run the command
> > ssh -v server hostname
> > we have also seen this with different commands and even just getting a shell.
> > (note I have tryed with -t, -n and of course without the -v and a -v -v -v give
> > no more info)
> > and about 1 time out of 1000 it hangs.
> > The verbose output is as follows:
> > debug1: Sending command: hostname
> > debug1: channel 0: open confirm rwindow 0 rmax 16384
> > debug1: channel 0: rcvd eof
> > debug1: channel 0: output open -> drain
> > server
> > debug1: channel 0: obuf empty
> > debug1: channel 0: output drain -> closed
> > debug1: channel 0: close_write
> >
> >
> > Then comes the hang. Note that this is differnt than the bg file wait issue.
> >
> > an netstat on the client:
> > client# netstat -a | grep server
> > client.34819        server.ssh         17520      0 33580      0 ESTABLISHED
> > client.34820        server.ssh         17520      0 33580      0 TIME_WAIT
> >
> >
> > and one on the server:
> > server# netstat -a | grep client
> > server.full.domain.name.com.ssh client.34819        33580      0 17520      0
> > ESTABLISHED
> >
> > and some ps :
> > client# ps -ef | grep hostname
> >     root 19944  2917  0 12:32:19 ?        0:01 /usr/local/bin/ssh -n -v server
> > hostname
> >
> > server# ps -ef | grep ssh
> >     root  3439 10524  0 12:32:21 ?        0:01 /services/ssh/sbin/sshd
> >
> >
> >
> > ------- You are receiving this mail because: -------
> > You are the assignee for the bug, or are watching the assignee.
> > _______________________________________________
> > openssh-unix-dev at mindrot.org mailing list
> > http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
> --
> -DISCLAIMER: an automatically appended disclaimer may follow. By posting-
> -to a public e-mail mailing list I hereby grant permission to distribute-
> -and copy this message.-
>
> Visit our website at http://www.ubswarburg.com
>
> This message contains confidential information and is intended only
> for the individual named.  If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail.  Please
> notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system.
>
> E-mail transmission cannot be guaranteed to be secure or error-free
> as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses.  The sender therefore
> does not accept liability for any errors or omissions in the contents
> of this message which arise as a result of e-mail transmission.  If
> verification is required please request a hard-copy version.  This
> message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
>