[prev in list] [next in list] [prev in thread] [next in thread]
List: pureftpd-list
Subject: [pure-ftpd] Quicjk question was Re: [pure-ftpd] resume files > 4G
From: Nigel Sollars <njs () vx ! com>
Date: 2009-10-14 18:36:20
Message-ID: 4AD61A24.4020605 () vx ! com
[Download RAW message or body]
Is this one fixed in latest version?
Regards
Nige
Marcus Engene wrote:
> Frank Denis wrote:
>> Le Tue, Sep 15, 2009 at 10:59:30PM +0200, Marcus Engene ecrivait :
>>
>>> Sorry for butting in here. My users have complained that resume
>>> doesn't work (for any file size) after I've installed 1.0.22;
>>> instead the uploadscript grabs broken uploads (for example users
>>> with shaky dsl:s).
>>>
>>> Would it be any point in trying to remove the tls compile option for
>>> me too?
>>>
>>
>> Hello Marcus,
>> Indeed, it looks like 1.0.22 broke the resume feature when
>> compiled with
>> TLS support.
>>
>> So yes, you can remove the TLS compile option as a temporary
>> workaround,
>> or apply the patch posted yesterday.
>>
>> I'll try to roll up a new release quickly in order to fix this.
>> Best regards,
>> -Frank.
>>
>>
>>
>
> Hi Frank,
>
> One user has reported back his progress.
>
> Had a few connection issues overnight, and there are still problems
> with APPEnd. The part-file on the server can't be seen when the
> reconnection is made, so the upload starts again from scratch.
>
> I have only tried it once, but when I paused the upload the part-file
> was held on the server for me to resume at my leisure.
>
> Log from overnight pasted here, but unfortunately the colours which
> aid readability are lost in this text box. Although there are four
> "Upload failed" messages there are only two events. During one loss of
> connection (7:57) the system has decided that the upload ought to be
> aborted and removed the file from the server. The earlier failure at
> 5:47 is more straightforward, in that the file can't be found on the
> server so the upload starts from scratch.
>
> (04:31:24) Status: Starting upload of S:\ttt\testfile1.zip
> (04:31:24) Command: TYPE I
> (04:31:24) Response: 200 TYPE is now 8-bit binary
> (04:31:24) Command: PORT 192,168,0,2,6,180
> (04:31:25) Response: 200 PORT command successful
> (04:31:25) Command: STOR testfile1.zip
> (04:31:25) Response: 150 Connecting to port 1716
> (05:47:06) Error: Upload failed
> (05:47:06) Status: Starting upload of S:\ttt\testfile1.zip
> (05:47:06) Command: TYPE A
> (05:47:17) Response: 202 .
> (05:47:17) Command: PORT 192,168,0,2,8,205
> (07:57:38) Response: 426-Error during read from data connection:
> Connection timed out
> (07:57:38) Response: 426-ABRT is the only legal command while
> uploading
> (07:57:38) Response: 426-Transfer aborted
> (07:57:38) Response: 426 testfile1.zip removed
> (07:57:38) Command: PASV
> (07:57:38) Response: 200 PORT command successful
> (07:57:38) Error: Upload failed
> (07:57:38) Status: Starting upload of S:\ttt\testfile1.zip
> (07:57:38) Command: TYPE A
> (07:57:38) Response: 227 Entering Passive Mode
> (123,124,125,126,40,181)
> (07:57:38) Command: PORT 192,168,0,2,12,103
> (07:57:38) Response: 200 TYPE is now ASCII
> (07:57:38) Command: LIST
> (07:57:38) Response: 200 PORT command successful
> (07:57:38) Error: Upload failed
> (07:57:38) Status: Starting upload of S:\ttt\testfile1.zip
> (07:57:38) Command: TYPE A
> (08:00:47) Response: 425 Could not open data connection to port
> 3175: Connection timed out
> (08:00:47) Error: Upload failed
> (08:00:47) Response: 200 TYPE is now ASCII
> (08:00:47) Status: Starting upload of S:\ttt\testfile1.zip
> (08:00:47) Command: TYPE A
> (08:00:47) Response: 200 TYPE is now ASCII
> (08:00:47) Command: PORT 192,168,0,2,12,125
> (08:00:48) Response: 200 PORT command successful
> (08:00:48) Command: LIST
> (08:00:48) Response: 150 Connecting to port 3197
> (08:00:48) Response: 226-Options: -l
> (08:00:48) Response: 226 0 matches total
> (08:00:48) Command: TYPE I
> (08:00:48) Response: 200 TYPE is now 8-bit binary
> (08:00:48) Command: PORT 192,168,0,2,12,126
> (08:00:48) Response: 200 PORT command successful
> (08:00:48) Command: STOR testfile1.zip
> (08:00:48) Response: 150 Connecting to port 3198
> (09:46:41) Response: 226-File successfully transferred
> (09:46:41) Response: 226 6352.512 seconds (measured here), 34.63
> Kbytes per second
> (09:46:41) Status: Upload successful
> (09:46:41) Status: Starting upload of S:\ttt\testfile3.zip
>
>
> and server side:
>
>
> Sep 17 19:21:34 domU-12-31-39-01-60-B2 pure-ftpd: (?@11.22.33.44)
> [INFO] username is now logged in
> Sep 17 23:31:24 domU-12-31-39-01-60-B2 pure-ftpd:
> (username@11.22.33.44) [NOTICE] /mnt/ftpupload/username//testfile2.zip
> uploaded (528207210 bytes, 34.47KB/sec)
> Sep 18 02:57:38 domU-12-31-39-01-60-B2 pure-ftpd:
> (username@11.22.33.44) [ERROR] Error during read from data connection:
> Connection timed out
> Sep 18 04:46:41 domU-12-31-39-01-60-B2 pure-ftpd:
> (username@11.22.33.44) [NOTICE] /mnt/ftpupload/username//testfile1.zip
> uploaded (225259110 bytes, 34.63KB/sec)
> Sep 18 06:54:14 domU-12-31-39-01-60-B2 pure-ftpd:
> (username@11.22.33.44) [NOTICE] /mnt/ftpupload/username//testfile3.zip
> uploaded (267099162 bytes, 34.09KB/sec)
> Sep 18 07:00:06 domU-12-31-39-01-60-B2 pure-ftpd:
> (username@11.22.33.44) [INFO] Logout.
>
> Pureftpd is started like this:
> po
> /usr/local/sbin/pure-authd -s /var/run/ftpd.sock -r
> /stuff/bin/ftp-auth-handler -B &
>
> /usr/local/sbin/pure-ftpd --chrooteveryone
> -lextauth:/var/run/ftpd.sock -t 400:4 -o --anonymouscantupload -E
> --tls=1 --daemonize -I 2880 -p 10000:11000 -c 500 -C 20 -P
> `/usr/local/bin/hostname_ip` -U 000:000 -H &
>
> /usr/local/sbin/pure-uploadscript -r /stuff/bin/uploadscript.py
> --daemonize &
>
>
> Please tell me what you'd like me to try.
>
>
> Best regards,
> Marcus
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic