|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
Further information, the machine in question is running:
CentOS 5 2.6.18-53.1.21.el5PAE Kernel |
|
||||
|
Through our tests we have actually tested on 3 different machines. All 3 machines have the same configuration and same hardware.
I'm currently in the process of setting up a 4th server to test with so I can try some custom compiles of pure-ftpd. The other 3 servers were live so I couldn't really tinker with the FTP service much. This server will not be using the PAE kernel. Hopefully I'll have some positive results. |
|
||||
|
Same results on the new machine with the standard RPM, no love.
|
|
||||
|
No luck with pure-ftpd compiled --without-sendfile. I did get an strace this time:
FTP Log: Code:
May 30 17:37:17 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 150 Connecting to port 1853 May 30 17:37:17 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 226-Options: -l May 30 17:37:17 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 226 8 matches total May 30 17:37:26 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] Command [port] [68,62,84,9,7,62] May 30 17:37:26 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 200 PORT command successful May 30 17:37:26 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] Command [retr] [FILENAME] May 30 17:37:26 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 150-Connecting to port 1854 May 30 17:37:26 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 150 2390.8 kbytes to download May 30 17:53:51 SERVER pure-ftpd: (USER@IPADDRESS) [INFO] Transfer aborted May 30 17:53:51 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 450 Error during write to data connection May 30 17:53:51 SERVER pure-ftpd: (USER@IPADDRESS) [INFO] Logout. May 30 17:53:51 SERVER pure-ftpd: (USER@IPADDRESS) [DEBUG] 450 Logout. Code:
root@SERVER [/etc]# strace -p 4590
Process 4590 attached - interrupt to quit
write(3, "\21\376\312\374<\0\353\6_\3=\374\315\371\320\374\326\4\304\6\326\376\355\371\335\375\220\1\251\1\350\1"..., 5190) = 5190
munmap(0xb7d28000, 65536) = 0
mmap2(NULL, 65536, PROT_READ, MAP_SHARED, 4, 0x100) = 0xb7d28000
write(3, "\7\21\10\243\t\262\r\n]\r\n\243\r\n{\r\n1\t\346\t\312\t\301\t\33\7\255\6f\6\5"..., 66124) = 20874
write(3, "\240\377\16\377`\0\216\1\23\0\234\377T\376\217\377z\0\306\0\240\377\212\376\354\3774\377\251\377\t\375"..., 45250) = -1 ETIMEDOUT (Connection timed out)
close(4) = 0
close(3) = 0
time(NULL) = 1212184431
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
send(2, "<94>May 30 17:53:51 pure-ftpd: ("..., 96, MSG_NOSIGNAL) = 96
setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0
time(NULL) = 1212184431
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
send(2, "<95>May 30 17:53:51 pure-ftpd: ("..., 122, MSG_NOSIGNAL) = 122
write(1, "450 Error during write to data c"..., 43) = 43
setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0
alarm(1800) = 85415
select(1, [0], NULL, NULL, {900, 0}) = 1 (in [0], left {900, 0})
read(0, "", 4112) = 0
time(NULL) = 1212184431
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
send(2, "<94>May 30 17:53:51 pure-ftpd: ("..., 87, MSG_NOSIGNAL) = 87
setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0
time(NULL) = 1212184431
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2202, ...}) = 0
send(2, "<95>May 30 17:53:51 pure-ftpd: ("..., 92, MSG_NOSIGNAL) = 92
write(1, "450 Logout.\r\n", 13) = 13
setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0
exit_group(0) = ?
Process 4590 detached
Looks like it might be time for a support ticket. |
|
||||
|
We don't want to use proftpd, but for completeness, I figured I'd try. Same results.
|
|
||||
|
We ended up having a problem within our network and had to power cycle one of our core routers. Once the router came back up, we no longer had this issue on any of the servers I used for testing.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|