Debugging SFTP question

[Darren Tucker]

On Sun, May 05, 2013 at 08:29:41AM -0500, Graeme Wallace wrote:
> 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

Without knowing what the client is doing it's kinda hard to say.  I
think we'll need to see a complete debug trace.

Does the client upload the file with a .part extension then rename it
when it's done?  I could imagine some kind of race where the rename
happens before the last write.  In that case I'd imagine the file
differences would be at the last offset sent.

Other possible variables: what filesystem is sftp-server writing to?

-- 
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.