A user of ours is receiving the error:
Note: Not "450 Error during write to data connection: Invalid Argument"
We've gone through all of the usual steps, check firewalls, check anti-virus software, binary vs. ASCII mode, the problem persists.
I found a suggestion on another thread and in the pure-ftpd documentation that sendfile support doesn't work properly on some kernels. We didn't have a problem on our CentOS 4 boxes, so I'm hoping the culprit is sendfile support on CentOS 5.
Any chance we could get a pure-ftpd RPM with the --without-sendfile flag compiled in? If worst comes to worst, we can try compiling from source.
I found a --without-sendfile compiled RPM on one of the old threads here in the forums. I'd prefer to not use an outdated RPM, but it 404'd anyways. Really I'm just grasping at straws here because we're unsure of what else could be causing this.
Oddly enough, it only happens with certain files and only happens on certain networks. We have tested this from many locations around the world. When tested from within the network, the files download fine. When tested from some external locations, it again works fine. When tested from others, it drops the connection. It's so sporradic, yet completely reproducable with the right file and location.
At the time of the error, the FTP client shows:
The FTP server shows:
I've already enabled verbose logging and enabled FTP logging in syslog. No relevant information is presented other than the error in this thread title.
Any ideas?
On a lighter note, at one point while troubleshooting this issue, the FTP server told me:
Code:
450 Error during write to data connection
We've gone through all of the usual steps, check firewalls, check anti-virus software, binary vs. ASCII mode, the problem persists.
I found a suggestion on another thread and in the pure-ftpd documentation that sendfile support doesn't work properly on some kernels. We didn't have a problem on our CentOS 4 boxes, so I'm hoping the culprit is sendfile support on CentOS 5.
Any chance we could get a pure-ftpd RPM with the --without-sendfile flag compiled in? If worst comes to worst, we can try compiling from source.
I found a --without-sendfile compiled RPM on one of the old threads here in the forums. I'd prefer to not use an outdated RPM, but it 404'd anyways. Really I'm just grasping at straws here because we're unsure of what else could be causing this.
Oddly enough, it only happens with certain files and only happens on certain networks. We have tested this from many locations around the world. When tested from within the network, the files download fine. When tested from some external locations, it again works fine. When tested from others, it drops the connection. It's so sporradic, yet completely reproducable with the right file and location.
At the time of the error, the FTP client shows:
Code:
200 PORT command successful
150-Connecting to port 3824
150 2375.7 kbytes to download
Connection closed by remote host.
Code:
May 29 20:43:34 SERVER pure-ftpd: ([email protected]) [DEBUG] 150-Connecting to port 3824
May 29 20:43:34 SERVER pure-ftpd: ([email protected]) [DEBUG] 150 2375.7 kbytes to download
May 29 20:46:20 SERVER pure-ftpd: ([email protected]) [INFO] Transfer aborted
May 29 20:46:20 SERVER pure-ftpd: ([email protected]) [DEBUG] 450 Error during write to data connection
May 29 20:46:20 SERVER pure-ftpd: ([email protected]) [INFO] Logout.
May 29 20:46:20 SERVER pure-ftpd: ([email protected]) [DEBUG] 450 Logout.
Any ideas?
On a lighter note, at one point while troubleshooting this issue, the FTP server told me:
Silly Easter Eggs.PureFTP Service said:200 PORT command successful
150-Connecting to port 3577
150-The computer is your friend. Trust the computer
150 2375.7 kbytes to download
Connection closed by remote host.