Re: openssh cygwin: connection closed by remote host

Running ssh -vv or -vvv on the client will give you more information, which
may help to illuminate what happened.

What do the server logs show from this exchange? Did you crank up LogLevel
to VERBOSE or DEBUG in /etc/ssh/sshd_config and restart sshd?

So I have noticed that upon logout from a remote session that the
forked sshd process is not killed. So say after having logged in and
then out 5 complete round trips there will be 6 sshd processes running
on the remote windows box, 1 corresponding to the original and 5 forked
processes from the 5 now closed connections. Could it be that this is
the source of my problems?

I don't see anything in sshd_config that relates to the number of allowed
concurrent connections from one user, but it is strange that those old
processes stay around, and that might be related to your problem.

Also when running sshd in debug mode I was
unable to open a connection, got: will not fork when running in
debugging mode. Should I need to fork on the first and only
connection?

Any time someone logs into the server, it forks off a new process to handle
the new connection. But you misunderstood me: I didn't say to run sshd in
debug mode (sshd -d). I said to set LogLevel to VERBOSE or DEBUG in
/etc/ssh/sshd_config, and restart sshd.

Any thoughts? If this is the problem, is there a way to force the sshd
process for the current connection closed without disturbing the
orignal sshd process? Thanks for any help.

Yes, you can kill the child sshd processes without harming the parent sshd.
Try doing that by hand before you reach 5 leftover processes, and see if
that allows you to keep logging in.

--
To reply by email, change "deadspam.com" to "alumni.utexas.net"
.

Relevant Pages

  • Re: openssh cygwin: connection closed by remote host
    ... forked sshd process is not killed. ... unable to open a connection, got: will not fork when running in ... Any time someone logs into the server, it forks off a new process to handle ... that allows you to keep logging in. ...
    (comp.security.ssh)
  • Re: openssh cygwin: connection closed by remote host
    ... debug1: Connection established. ... So I have noticed that upon logout from a remote session that the ... forked sshd process is not killed. ...
    (comp.security.ssh)
  • Re: openssh cygwin: connection closed by remote host
    ... parent pid = pid of the original sshd process, ... So two new sshd processes are created per new connection. ... I have shell scripts logging in, doing stuff, and then ... and you should report it as such to the Cygwin ...
    (comp.security.ssh)
  • Re: SSH connection problems
    ... NWR> check its contents. ... NWR> sshd process. ... the error message indicates the server terminated ... the connection immediately after opening it, ...
    (comp.security.ssh)