ssh Connection reset by peer -- Suggestions for getting debug messages?
Hello LQers. I hope I have some good karma -- because this one is weird.
[Just spent an hour helping a noob with a graphics card problem ... karma].
We all understand this message:
Things you should know:
At this point I am just looking for intelligent questions to ask.
How can I diagnose this?
I did not see any messages with dmesg,
or /var/log/syslog. I saw some posts about enabling verbose logging
with sshd on the server -- but could not make that work. So maybe
that is a place to start.
what is it that you tried? # ssh -vvvv users@server
Dear Mr. Chitambira -- Thanks for helping me think about this differently.
I had been looking for debug messages on the server side. Evidently
you can start sshd with debug flags as well. I had not had luck
making this work, however.
On the client side, I have two problems. One is that the first
logon almost always ends in failure, the other is that the second
logon does not last. The only thing I can see that differentiates
the two is that the second logon happens shortly after the first
attempt. It as if the first attempt changes some state on the server.
It all seems like magic at the moment.
Thinking perhaps that something is horked up on the client side,
I did an
Anyway -- I will post an excerpt from a failed logon attempt.
If anything strikes you as odd -- I will pursue it further.
hmmm... seems like you are trying to run X over ssh (X forwading) ;) need logs from server /var/log/secure, /var/log/Xorg.0.log if available, then also need full client session debug for both fisrt and second ssh connection attempts, then lastly your /etc/ssh/ssh_config from client side
Client side config
As far as X forwarding goes -- that is a very helpful feature -- but I was
not using it. I there something in the log that suggests I was?
(I just checked my aliases -- ssh is not aliased to ssh -X)
As far as client side ssh_config -- I had not previously had one
for my userID, but I created one as follows:
THanks for staying involved.
How about this issue? already fixed?
Now I also met same problem, and I am finding the solution...
|All times are GMT -5. The time now is 05:30 AM.|