Debugging SFTP question

[Graeme Wallace]

The client is Axway Secure Transport. The files we are receiving are from a
vendor so I don't have any control over the client side unfortunately.

The file shouldnt be sparse as its a bzipped ASCII file.

I've also downloaded the bzip source and dumped out the offset at which its
corrupt, and it doesnt correspond to the offset jumps. (I'm still confused
about whats going on there)

If i look at the debug logs from sftpd, the 32K packet that contains the
corrupt offset says it was received ok.

What else can I check ? (The vendor assures me that they transmit files
around using Axway all over the place without problems and its just our
system....)


regards


Graeme



On Sun, May 5, 2013 at 8:15 AM, Darren Tucker <dtucker at zip.com.au> wrote:

> On Fri, May 03, 2013 at 05:58:59PM -0500, Graeme Wallace wrote:
> > Is it normal for request numbers and offsets to suddenly jump massively ?
>
> The client doesn't happen to be sshfs does it?  If so the offset jump
> might be the client writing a sparse file.
>
> --
> Darren Tucker (dtucker at zip.com.au)
> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
>     Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.
>



-- 
Graeme Wallace
CTO
FareCompare.com
O: 972 588 1414
M: 214 681 9018