scp failing

[Peter Heinemann]

HP-UX 11-11; Bastille B.02.01.01

scp is failing. On the target, the following entries:

Jul 28 11:09:34 pa2padm1 sshd[28266]: fatal: buffer_get: trying to get more bytes 129 than in buffer 78
Jul 28 11:09:35 pa2padm1 sshd[28268]: fatal: buffer_get: trying to get more bytes 129 than in buffer 78

Wasn't able to get any hits on itrc searches. Can anyone shed some light? scp has worked before to this target.

Thanks!
...Peter

[Steven E. Protter]

I you let Bastille set up ipfilter firewall it may have blocked port 22. Check that.

Also try ssh -v or scp -v and you may get a little more detail on the error log.

SEP

[RAC_1]

Is target running out of buffer cache??

Check with glance. Any buffer cache related messages in syslog??)target machin)

Anil

[Peter Heinemann]

Anil:

glance shows:

Buffer Cache 204.8mb na 204.8mb na
Buffer Cache Min 204.8mb
Buffer Cache Max 204.8mb

Steven,

Port 22 seems ok, judging by the -v output below. Note that I tried ssh; it's choking the same way as scp. Same entry in syslog.

OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to (snipped host/address info) port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p2
debug1:


debug1: Mechanism encoded as toWM5Slw5Ew8Mqkay+al2g==
debug1:


debug1: Mechanism encoded as A/vxljAEU54gt9a48EiANQ==
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'pa2padm1' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: external-keyx,gssapi,publickey,password,keyboard-interactive
debug1: Next authentication method: external-keyx
debug1: Authentications that can continue: external-keyx,gssapi,publickey,password,keyboard-interactive
debug1: Next authentication method: gssapi
debug1:


debug1:


debug1:


debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Offering public key: /root/.ssh/id_dsa
Connection closed by (snipped address)
debug1: Calling cleanup 0x40017092(0x0)

[Steven E. Protter]

I agree with your conclusions on connectivity and ipfilter. Clearly the connection is not being blocked.

I'd pursuue issues on the target server at this point.

tail -f /var/adm/syslog/syslog.log

Connect again and see what happens. You may need to toggle enhanced logging with inetd -l

Plus the other posters suggestion. Seems like we have an OS issue on the target.

Can we boot it?

SEP

[RAC_1]

Also post
sar -b 5 10

Anil

[Peter Heinemann]

Steven:
Yeah, I'll try a reboot. Hate it when a 7410 acts like a Windoze system.

BTW, I tried a SIGHUP on sshd but no improvement:

Jul 28 13:34:14 pa2padm1 sshd[678]: Received SIGHUP; restarting.
Jul 28 13:34:14 pa2padm1 sshd[29524]: Server listening on 0.0.0.0 port 22.
Jul 28 13:34:30 pa2padm1 sshd[29527]: fatal: buffer_get: trying to get more bytes 129 than in buffer 78
Jul 28 13:40:40 pa2padm1 sshd[29579]: fatal: buffer_get: trying to get more bytes 129 than in buffer 78




Anil:

13:40:32 bread/s lread/s %rcache bwrit/s lwrit/s %wcache pread/s pwrit/s
13:40:37 0 12 100 1 1 25 0 0
13:40:42 0 74 100 0 3 100 0 0
13:40:47 0 2 100 1 1 20 0 0
13:40:52 0 134 100 0 6 94 1 0
13:40:57 0 2 100 2 2 0 0 0
13:41:02 0 17 100 2 3 47 0 0
13:41:07 0 3 100 1 2 25 0 0
13:41:12 0 10 100 1 5 88 0 0
13:41:17 0 2 100 1 1 20 0 0
13:41:22 0 10 100 1 3 56 0 0

Average 0 26 100 1 3 66 0 0

[Peter Heinemann]

Reboot didn't clear the condition!

Jul 28 14:05:04 pa2padm1 syslogd: restart
(snip)
Jul 28 14:06:45 pa2padm1 sshd[1597]: fatal: buffer_get: trying to get more bytes 129 than in buffer 78

[RAC_1 · Accepted solution]

How did you built the authorized_keys file on target system?? Did you cut and paste???

If yes, do not do that. Trnasfer the *.pub file and do a cat and append the key to target's authorized_keys file

cat rsa.pub >> $HOME/.ssh/authorized_keys file. Restart sshd and post

Anil

[Peter Heinemann]

Anil,

That was it. Works now.

Thanks to both of you.