PDA

View Full Version : SSH hangs after authenticating myself?


joshua
11-09-2006, 10:22 AM
When I try to log into my web hosting account by SSH, it's rare that I actually get connected. I managed to get connected once today, but never after that. I try to connect using

ssh -l singwayland@singwayland.org singwayland.org

It asks me for my password, and when I mistype my password, it tells me of that successfully; but when I give it the right password, it (usually) just sits there. If I hit a key after a while, it says "Read from remote host singwayland.org: Connection reset by peer".

If I try ssh -v -v -v -l singwayland@singwayland.org singwayland.org , the last message it gives me before it sits is "debug1: Entering interactive session."

Any tips?

joshua

Matt
11-09-2006, 03:36 PM
Out of the sake of curiosity, are you still experiencing the issue now? It may be an issue with the log socket used by syslog to log activity.

dkozinn
11-09-2006, 04:30 PM
Out of the sake of curiosity, are you still experiencing the issue now? It may be an issue with the log socket used by syslog to log activity.
I am, now (15:30 EST).

joshua
11-09-2006, 04:49 PM
Yes, I am (Thu Nov 9 15:49:15 EST 2006).

Matt
11-09-2006, 10:47 PM
After trying to reproduce the problem you're running into, I can see what you're talking about. Unfortunately we've had a user forget mailing list etiquette on the server. For example, some golden rules to remember are:
- ensure your mailing list works and doesn't generate a bounce for every single recipient
- don't start the mailing list during peak server hours (9 AM - 10 PM EST)
- if you have a bounce-back address, ensure that it can receive e-mail instead of creating even more failure notices in the process
- don't send all 6,000+ letters at once especially if zero of the three preconditions are satisfied

All four helpful rules were violated and as a result, the server has been going through some tumultuous times today. I've quarantined the second batch of disruptive failure notices and hopefully this will be the end of that. If not, file a ticket in the control panel and I can get that taken care of for you.