broken pipe error

[Jacob D Levin]

Hi all, I keep getting an error when trying to ftp a file through the internet. the error is:
sendfile: Broken pipe
426 Connection closed; transfer aborted.

Does anyone know why this might be happening and what I can do to prevent it?
Thanks

[Sanjay_6]

Hi Jacob,

IS this transfer throuh a firewall and are you trying to transfer lage files. This looks like a timeout problem, either effected by the firewall or the network.

Hope this helps.

Regds

[Jacob D Levin]

I'm trying to send multiple files, no larger than 1.7m each. I am transfering through our firewall to the site. Is this possibly due to a lack of bandwidth through the firewall?

[PIYUSH D. PATEL]

Hi,

It seems that this is a timeout problem when you are trying to send the large files.

Piyush

[Sanjay_6]

Hi,

This looks like a firewall timing out the connection because it thinks there is no activity on the terminal. Though the ftp of files is going on the firewall thinks it is an inactive port / terminal / connection. Talk to your firewall team.

Hope this hels.

Regds

[Jordan Bean]

Maybe it's not bandwidth... Perhaps is the transfer method itself.

Passive mode works through most firewalls, but is not a default for some ftp programs. In command line ftp, use the 'passive' command to toggle this mode on and off. In IE, you will find this option labeled "Use Passive FTP..." in the browser section of the Advanced tab of the Internet Options dialog. In WS FTP, it's a checkbox in the Advanced tab of the Session Properties.

[Manoj Jain_3]

Jacob,

I am having the same..

sendfile: Broken pipe error
426 Connection closed; transfer aborted.

What you did to fix this problem?

Please reply
Manoj

[U.SivaKumar_2]

Hi,

Try the connection again. And analyse the firewall logs about the FTP events and errors reported. Come back with results

regards,
U.SivaKumar

[Tyler Rager]

I don't know if this will help or even relates to your situation, but I thought I would let you know what I found on a broken pipe problem we were encountering.
We were FTP'ing from an external server through the firewall to our mainframe. Our files existed on the mainframe but were migrated to backup storage tape. The FTP jobs had to pull the files off of backup tape so that they could be deleted prior to the new file being created. This process took long enough that our FTP jobs abended with a broken pipe error which was basically a timeout situation.
We changed this process to not allow the files to ever migrate to backup tape and we have never encountered this problem again.
I don't know if this will help, but thought I would throw it out here anyway.
-Tyler