Menu

#899 OPERATION_TIMEDOUT encountered when ftp upload a large file

closed-fixed
ftp (93)
5
2014-08-19
2010-02-22
ryan chan
No

I targeted to upload a file (~1GB) to a ftp server (FileZilla Server) using passive mode.
I use libcurl-7.20.0 in my application, but CURLE_OPERATION_TIMEDOUT was encountered after the file is uploaded to the server.
The same error code I encountered when I use curl-7.20.0 (windows version).

Here is the output when I upload with curl-7.20.0:
D:\ryan.chan\curl>curl-7.20.0 -v --ftp-method nocwd --disable-epsv -T ../SLX_2210 ftp://192.168.180.2:2010 -u rchan:rchan
* About to connect() to 192.168.180.2 port 2010 (#0)
* Trying 192.168.180.2... % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0connected
* Connected to 192.168.180.2 (192.168.180.2) port 2010 (#0)
< 220-FileZilla Server version 0.9.34 beta
< 220-written by Tim Kosse (Tim.Kosse@gmx.de)
< 220 Please visit http://sourceforge.net/projects/filezilla/
> USER rchan
< 331 Password required for rchan
> PASS rchan
< 230 Logged on
> PWD
< 257 "/" is current directory.
* Entry path is '/'
> PASV
* Connect data stream passively
< 227 Entering Passive Mode (192,168,180,2,4,226)
* Trying 192.168.180.2... connected
* Connecting to 192.168.180.2 (192.168.180.2) port 1250
> TYPE I
< 200 Type set to I
> STOR SLX_2210
< 150 Connection accepted
} [data not shown]
99 1413M 0 0 99 1406M 0 8084k 0:02:59 0:02:58 0:00:01 8192k* Remembering we are in dir ""
* FTP response timeout
* control connection looks dead
100 1413M 0 0 100 1413M 0 8085k 0:02:59 0:02:59 --:--:-- 8182k* Closing connection #0

curl: (28) FTP response timeout

However, I successfully get my job done using curl-7.19.7 with return code curle_ok.

Here is the result when I use curl-7.19.7:

D:\ryan.chan\curl>curl-7.19.7 -v --ftp-method nocwd --disable-epsv -T ../SLX_2210 ftp://192.168.180.2:2010 -u rchan:rchan
* About to connect() to 192.168.180.2 port 2010 (#0)
* Trying 192.168.180.2... connected
* Connected to 192.168.180.2 (192.168.180.2) port 2010 (#0)
< 220-FileZilla Server version 0.9.34 beta
< 220-written by Tim Kosse (Tim.Kosse@gmx.de)
< 220 Please visit http://sourceforge.net/projects/filezilla/
> USER rchan
< 331 Password required for rchan
> PASS rchan
< 230 Logged on
> PWD
< 257 "/" is current directory.
* Entry path is '/'
> PASV
* Connect data stream passively
< 227 Entering Passive Mode (192,168,180,2,4,227)
* Trying 192.168.180.2... connected
* Connecting to 192.168.180.2 (192.168.180.2) port 1251
> TYPE I
< 200 Type set to I
> STOR SLX_2210
< 150 Connection accepted
} [data not shown]
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
99 1413M 0 0 99 1409M 0 8076k 0:02:59 0:02:58 0:00:01 8179k* Remembering we are in dir ""
< 226 Transfer OK
100 1413M 0 0 100 1413M 0 8076k 0:02:59 0:02:59 --:--:-- 8180k* Connection #0 to host 192.168.180.2 left intact

> QUIT
< 221 Goodbye
* Closing connection #0

My testing environment (upload source):
- Windows 2003 Server x64
- curl-7.20.0 / curl-7.19.7

My testing environment (upload destination):
- Windows 2003 Server x64
- Filezilla server 0_9_34

Discussion

  • ryan chan

    ryan chan - 2010-02-22
    • priority: 5 --> 9
     
  • Daniel Stenberg

    Daniel Stenberg - 2010-02-22
    • priority: 9 --> 5
     
  • Daniel Stenberg

    Daniel Stenberg - 2010-02-22

    Please leave 'priority' field for the curl project team to decide.

     
  • ryan chan

    ryan chan - 2010-02-22

    Opps... I am sorry for that.
    It's my first time to submit bug report for curl project.

     
  • Daniel Stenberg

    Daniel Stenberg - 2010-03-02

    Thanks, this is now believed to be fixed in CVS. It'd be great if you tried the CVS code or tomorrow's daily snapshot and verified that it truly is so for you as well.

     
  • Daniel Stenberg

    Daniel Stenberg - 2010-03-02
    • status: open --> pending-fixed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed