![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| error messages in /var/adm/messages | nitinp82 | UNIX for Advanced & Expert Users | 1 | 04-17-2007 07:17 AM |
| /var/adm/messages | FrankC | UNIX for Dummies Questions & Answers | 3 | 09-18-2006 08:25 AM |
| /var/adm/messages | soliberus | SUN Solaris | 2 | 06-29-2005 07:18 AM |
| /var/adm/messages | finster | SUN Solaris | 5 | 12-17-2003 06:41 AM |
| /var/adm/messages- Help | finster | SUN Solaris | 1 | 12-11-2003 06:03 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
help debuging ssh messages.
Hi Everyone,
I am having problems SSHing from a client to the server. When the server is restarted, everything works fine. Few days/weeks (this happens at irregular intervals) after restarting, the problem (i.e.,not able to SSH) appears again. note: ------- I am able to ping the server and get all the replies even when it is not SSH'able. The server which acts as a gateway keeps routing the traffic from the internal network irrespective of the SSH issue. When I issued an SSH command with the -vvv option, it displays the following: Code:
[root@devBox ~]# ssh -v <ipaddress> OpenSSH_4.2p1, OpenSSL 0.9.7f 22 Mar 2005 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to <ipaddress> [<ipaddress>] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 ssh_exchange_identification: read: Connection reset by peer -Karthik. |
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
The sshd server is breaking the connection, but there is no indication why on the client side. Server logs, and debugging sshd itself, could be more useful.
|
|||
| Google The UNIX and Linux Forums |