Error In Server Response Closing Control Connection. Retrying
Sun, 9 Feb 2003 09:25:06 +0000 Message-id: <[🔎]20030209093102.LVMM4529.mta02-svc.ntlworld.com@there> Reply-to: dave_arahan@yahoo.co.uk In-reply-to: <[🔎]20030209085000.GH8810@elendil.bearhouse.org> References: <[🔎]20030209082839.UIFK3191.mta07-svc.ntlworld.com@there> <[🔎]20030209085000.GH8810@elendil.bearhouse.org> On Sunday 09 February 2003 8:50 am, Jeffrey Taylor wrote: > Quoting Dave Selby
Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug465469 - wget does not resume broken ftp connection Summary: wget does not resume broken ftp connection Status: CLOSED WONTFIX Aliases: None Product: Fedora Classification: Fedora Component: wget (Show other bugs) Sub Component: --- Version: 13 Hardware: All Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Karsten Hopp QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: https://lists.debian.org/debian-user/2003/02/msg01785.html 2008-10-03 10:14 EDT by Need Real Name Modified: 2010-06-28 09:37 EDT (History) CC List: 2 users (show) karsten micah See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2010-06-28 06:45:17 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments https://bugzilla.redhat.com/show_bug.cgi?id=465469 (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Need Real Name 2008-10-03 10:14:07 EDT wget does not resume broken ftp connection, for some reason it asumes the file is already downloaded. wget --user=xxxx --password=yyyyy ftp://zzzzzzzzzzzzz.com/file.zip --2008-10-03 07:21:21-- ftp://zzzzzzzzzzzzz.com/file.zip => `file.zip' Connecting to zzzzzzzzzzzzz.com[1.1.1.1]:21... connected. Logging in as xxxx ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /ITCHFiles ... done. ==> SIZE file.zip ... 2546787098 ==> PASV ... done. ==> RETR file.zip ... done. Length: 2546787098 (2.4G) 3% [> ] 77,495,340 --.-K/s in 26m 6s 2008-10-03 07:47:29 (48.3 KB/s) - Data connection: Connection timed out; Data transfer aborted. Retrying. --2008-10-03 07:47:30-- ftp://zzzzzzzzzzzzz.com/file.zip (try: 2) => `file.zip' ==> CWD not required. ==> SIZE file.zip ... done. ==> PASV ... Error in server response, closing control connection. Retrying. --2008-10-03 07:47:32-- ftp://zzzzzzzzzzzzz.com/file.zip (try: 3) => `file.zip' Connecting to zzzzzzzzzzzzz.com[1.1.1.1]:21... connected. Logging in as xxxx ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /ITCHFiles ... done. ==> SIZE file.zip ... 2546787098 ==> PASV ... done. ==> RETR file.zip ... done. file.zip has sprung into existence. Retrying. --2008-10-03 07:47:37-- ftp://zzzzzzzzzzzzz.com/file
Hi, I'm using wget to recursively retrieve a directory tree from an FTP server. Occasionally there are connection failures (thanks to a flaky server, or possibly https://lists.gnu.org/archive/html/bug-wget/2009-06/msg00022.html dodgy network infrastructure on the route, but that's not the problem I'm concerned with here), so I'm relying on wget to retry failed downloads. I'm seeing a problem where the retry "succeeds" but results in an empty file. I've included log output (using the -d switch) from when this happens below. You'll see that for error in the retry wget sends a REST command to reset the start position before starting the RETR command. I'm confused about the argument to REST: 51132. It's the full length in bytes of the file to be retrieved. The RETR then shows the entire contents of the file being skipped, and wget announces that it successfully error in server retrieved and saved 0 bytes. Is that argument to REST correct? $ wget --version GNU Wget 1.11.4 $ wget ftp://ftp.site.com/Dir/All/dirname --ftp-user=user --ftp-password=password --recursive --no-host-directories --no-parent --cut-dirs=2 --timestamping --output-file output.log -P target-dir -d log output: ... skipped successful stuff ... --2009-06-10 09:50:54-- ftp://ftp.site.com/Dir/All/dirname/subdir/dirname => `target-dir/dirname/subdir/.listing' changing working directory Prepended initial PWD to relative path: pwd: '/' old: 'Dir/All/dirname/subdir' new: '/Dir/All/dirname/subdir' ==> CWD /Dir/All/dirname/subdir ... --> CWD /Dir/All/dirname/subdir 250 Directory successfully changed. done. conaddr is: XXX.XXX.XXX.XXX ==> PASV ... --> PASV 227 Entering Passive Mode (XXX,XXX,XXX,XX,XXX,XXX) trying to connect to XXX.XXX.XXX.XXX port 32175 Created socket 5. done. ==> LIST ... --> LIST -a 150 Here comes the directory listing. done. 0K 82.0K=0.002s Closed fd 5 226 Directory send OK. 2009-06-10 09:50:54 (82.0 KB/s) - `target-dir/dirname/subdir/.listing' saved [194] DIRECTORY; perms 775; size: 2048; month: Jun; day: 9; time: 15:12:00 (no yr); Ignoring `.' and `..'; Skipping. DIRECTORY; perms 775; size: 118784; month: Jun; day: 9; time: 23:18:00 (no yr); Ignoring `.' and `..'; Skipping. PLAINFILE; perms 6