Bug#239999: Read from socket failed on Alpha
> # not testing-specific
> tags 239999 - sarge
> thanks
>
> On Thu, Mar 25, 2004 at 10:18:32AM +0100, Stephane Leclerc wrote:
>> After upgrading ssh to 3.8p1-1 (or 3.8p1-2), I encountered a trouble with
>> ssh connection to Alpha machine.
>>
>> (it seemed i386 machine is okay with ssh 3.8p1-1)
>>
>> When I tried to ssh to Alpha machine with ssh 3.8p1-1 then it refused with a
>> message,
>>
>> ns1:/home/sleclerc# ssh sleclerc@localhost
>> Read from socket failed: Connection reset by peer
>
> Can I see the output from 'ssh -vvv sleclerc@localhost', please, and any
> relevant entries in /var/log/auth.log on the server? If you could run
> the server with -ddd then that might also be useful.
>
> Thanks,
Below the debug output with ssh 1:3.8p1-2, Kernel 2.2.19 and openssl
0.9.7d-1
ns1:/home/sleclerc# ssh -vvv sleclerc@localhost
OpenSSH_3.8p1 Debian 1:3.8p1-2, SSH protocols 1.5/2.0, OpenSSL 0.9.7c 30 Sep
2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type 0
debug3: Not a RSA1 key file /root/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.8p1
Debian 1:3.8p1-2
debug1: match: OpenSSH_3.8p1 Debian 1:3.8p1-2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8p1 Debian 1:3.8p1-2
debug1: SSH2_MSG_KEXINIT sent
Read from socket failed: Broken pipe
SSHD_OPTS="-ddd"
ns1:/home/sleclerc# /etc/init.d/ssh restart
Restarting OpenBSD Secure Shell server: sshddebug2: read_server_config:
filename /etc/ssh/sshd_config
debug1: sshd version OpenSSH_3.8p1 Debian 1:3.8p1-2
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
socket: Address family not supported by protocol
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from 127.0.0.1 port 1956
debug1: Client protocol version 2.0; client software version OpenSSH_3.8p1
Debian 1:3.8p1-2
debug1: match: OpenSSH_3.8p1 Debian 1:3.8p1-2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-1.99-OpenSSH_3.8p1 Debian 1:3.8p1-2
debug2: Network child is on pid 5634
debug3: privsep user:group 100:65534
debug3: preauth child monitor started
debug3: mm_request_receive entering
debug1: permanently_set_uid: 100/65534
setresgid 65534: Function not implemented
debug1: do_cleanup
debug1: PAM: cleanup
debug3: PAM: sshpam_thread_cleanup entering
debug1: do_cleanup
debug1: PAM: cleanup
debug3: PAM: sshpam_thread_cleanup entering
...............................................................
. Linux - Debian - php4 - JAVA/Tomcat - MySQL - Infogerance .
. email: info@actionweb.fr - http://www.actionweb.fr/ .
. Tel: (0)141 906 100 - Fax: (0)141 906 101 .
...............................................................
Reply to: