Robert Hajime Lanning wrote: > On 12/7/06, samljones <[EMAIL PROTECTED]> wrote: > [snip] >> debug1: Next authentication method: password >> [EMAIL PROTECTED]'s password: >> debug1: Authentication succeeded (password). >> debug1: channel 0: new [client-session] >> debug1: Entering interactive session. >> debug1: Sending environment. >> debug1: Sending env LANG = en_US.UTF-8 >> =========================================== >> >> After that last line, the cursor goes to the next line, and hangs. No >> connection, no rejection, no command line, just flashing cursor. Can't >> even >> ctrl-c out of it; have to close the terminal/tab. > > This actually sounds like a system resource issue. At that point sshd > fork()s > your login shell. Sounds like something is either stopping or slowing > down the > fork()ing or exec()ing the shell. > > Try waiting a while, to see if the shell prompt eventually appears. >
I tend to agree with you. Samljones, how many connections per second and on what hardware are you reaching? How many of those are ssl? What does dmesg say? There is actually no link whatsoever between ssh and apache/mod_ssl other than the openssl libraries. This reminds me of some issue i solved some time ago where ssh couln't accept incoming or outgoing connections, i don't remember exactly, because of some problem in udev. No sense but there it was.
