Received disconnect from xxx.xxx.xxx.xxx: 2: Packet corrupt

Discussion of Co:Z sftp, a port of OpenSSH sftp for z/OS
Post Reply
maw
Posts: 5
Joined: Thu Sep 04, 2014 12:50 pm

Received disconnect from xxx.xxx.xxx.xxx: 2: Packet corrupt

Post by maw »

Co:Z V2.4.5, Z/OS 1.13

Receiving this in my z/OS Co:Z batch job log sending a file to a client's Linux server.

Received disconnect from xxx.xxx.xxx.xxx: 2: Packet corrupt

General Google searches seem to indicate this is some kind of issue with a network adapter, checksums, etc. Is there a good way to shoot these issues to find a root cause ?

Section of log:

..54.272. debug3: SSH2_FXP_STATUS 0
..54.272. debug3: In write loop, ack for 27 32768 bytes at 753664
..54.272. debug3: Sent message SSH2_FXP_WRITE I:44 O:1310720 S:32768
..54.471. debug3: SSH2_FXP_STATUS 0
..54.471. debug3: In write loop, ack for 28 32768 bytes at 786432
..54.507. debug3: Sent message SSH2_FXP_WRITE I:45 O:1343488 S:32768
..54.822. debug3: SSH2_FXP_STATUS 0
..54.822. debug3: In write loop, ack for 29 32768 bytes at 819200
..54.822. debug3: Sent message SSH2_FXP_WRITE I:46 O:1376256 S:32768
..54.822. debug3: SSH2_FXP_STATUS 0
..54.822. debug3: In write loop, ack for 30 32768 bytes at 851968
..54.822. debug3: Sent message SSH2_FXP_WRITE I:47 O:1409024 S:32768
.Received disconnect from 10.224.14.138: 2: Packet corrupt
.
..54.850. Connection closed
.CoZBatch.I.: returning rc=exitcode=255

Packet trace shows a RST coming from Linux server.
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Re: Received disconnect from xxx.xxx.xxx.xxx: 2: Packet corrupt

Post by dovetail »

These errors indicate that the remote SSH server detected that it received a corrupted SSH packet. The remote server sent an SSH "DISCONNECT" packet back to the z/OS OpenSSH client and then disconnected the socket.

This error indicates that there is some kind of network error (firewall, bad adapter, etc) that is corrupting data.

I can't recommend any specific tools for diagnosing a network problem, but you would probably need to get a network engineer to diagnose it.
Post Reply