pure-ftp times out, pro-ftp glibc errors, please help...

splicesite

Member
Jul 16, 2006
14
0
151
Hi,
Running pure-ftp I am currently unable to upload any files larger than around 300kb with any consistency. 90% of the time the upload will simply stop in its tracks and the connection will time out with " [INFO] Timeout (no new data for 900 seconds) ", after only a minute or so. I tried uncommenting the Passive Ports option in pure-ftpd.conf and opening said ports in APF to no avail. (Chirpy has said in another related post that this should be unnecessary anyway.) I also checked one supposed fix for this problem which involves a missing ip_conntrack_ftp module but this is present and loaded on my server. I have tried several clients with no difference and even FTP using WinSCP with SSH exhibits the same behavior, as well as from several different locations. Occasionally a few files will make it through but then the upload always stops and times out in the same manner. I reinstalled pure-ftp using the newest version and the same behavior occurs.

This is making things impossible.

In frustration I switched to Pro-ftp using the WHM script. The problem with uploads was resolved but I am now getting *** glibc detected *** double free or corruption (!prev): 0x0945c220 *** everytime an FTP logout occurs. I saw many threads on this issue which pointed to the 3.0+ versions of Zend Optimizer as a possible source of this error. So I downgraded Zend to 2.6.2, and still getting this glibc error using Pro-ftpd.

So,

1) Any thoughts on the pure-ftp issue? I have tried all posted solutions that I have been able to find. This must be affecting others as well.

2)Things are working with Pro-ftp but I'm getting the glibc errors on any FTP logout even after downgrading Zend Optimizer. Should I be concerned about these errors? Any other insights?

Thanks so much in advance.
 

splicesite

Member
Jul 16, 2006
14
0
151
UPDATE:

1)The pure-ftp problem appears to be due to APF. With APF stopped, transfers proceed normally. The proper ports are indicated in the APF and pure-ftp conf files for passive transfers. However this issue seems to be present whether using passive or active transfers on any port (or do all my FTP clients default to passive since I am behind NAT?). This was somewhat discussed in this thread.

Can anyone confirm this is a bug in APF?


2)Still stumped by this glibc error.
 
Last edited:

ozarkhost

Active Member
Oct 9, 2003
32
0
156
OK in /etc/pureftpd.conf file uncomment the passive port range put the range for example
3000 5000

stop pureftp
start pureftp

edit apf config file apply the port range as well stop apf firewall and start it

all ftp clients should use passive not active