Cyberduck Mountain Duck CLI

#9598 closed defect (fixed)

Resuming file transfer starts over and errors out

Reported by: jreiter1975 Owned by: dkocher
Priority: normal Milestone: 5.0.11
Component: b2 Version: 5.0
Severity: normal Keywords:
Cc: Architecture: Intel
Platform: Windows 10


I have seen this behavior on Windows 10 and Windows 7, both 64 bit systems. I have seen the behavior with 5.0.1 and now 5.0.3 Cyberduck. I am seeing that the resume function does not work. It will simply start over in the upload process or error out. Is there something I am missing in getting the resume to work? Happy to send logs if you let me know which ones you need. Thanks, Jeff

Change History (13)

comment:1 Changed on Jun 20, 2016 at 9:07:42 AM by dkocher

  • Summary changed from Backblaze B2 resume not working to Resuming file transfer starts over and errors out
  • Version set to 5.0

comment:2 Changed on Jul 15, 2016 at 12:54:12 PM by dkocher

Please attach the file cyberduck.log in the application support directory.

comment:3 Changed on Jul 20, 2016 at 1:14:40 AM by oleksandr

Can confirm the bug on v5.0.9 (20675) Win10 x64, backblaze b2

Cyberduck.log contains a single exception report:

2016-07-20 03:46:56,843 [http-vs2013.2.iso-1] ERROR ch.cyberduck.core.threading.LoggingUncaughtExceptionHandler - Thread http-vs2013.2.iso-1 has thrown uncaught exception:Connection pool shut down
java.lang.IllegalStateException: Connection pool shut down
	at org.apache.http.util.Asserts.check(
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.requestConnection(
	at org.apache.http.impl.execchain.MainClientExec.execute(
	at org.apache.http.impl.execchain.ProtocolExec.execute(
	at org.apache.http.impl.execchain.RetryExec.execute(
	at org.apache.http.impl.execchain.RedirectExec.execute(
	at org.apache.http.impl.client.InternalHttpClient.doExecute(
	at org.apache.http.impl.client.CloseableHttpClient.execute(
	at org.apache.http.impl.client.CloseableHttpClient.execute(
	at synapticloop.b2.request.BaseB2Request.execute(
	at synapticloop.b2.request.BaseB2Request.executePost(
	at synapticloop.b2.request.B2UploadPartRequest.getResponse(
	at synapticloop.b2.B2ApiClient.uploadLargeFilePart(
	at ch.cyberduck.core.b2.B2PartWriteFeature$
	at ch.cyberduck.core.b2.B2PartWriteFeature$
	at ch.cyberduck.core.http.AbstractHttpWriteFeature$
	at ch.cyberduck.core.threading.NamedThreadFactory$

Last edited on Jul 20, 2016 at 5:37:34 AM by dkocher (previous) (diff)

comment:4 Changed on Jul 20, 2016 at 8:20:12 AM by dkocher

  • Milestone set to 5.1
  • Owner set to dkocher
  • Status changed from new to assigned

comment:5 Changed on Jul 20, 2016 at 8:58:18 AM by dkocher

What is the error displayed when trying to resume the transfer?

comment:6 Changed on Jul 20, 2016 at 10:01:45 AM by oleksandr

It tries to login, resume, fiddles for a while, then displays "Transfer incomplete". Screenshot is from Server 2012, but the behavior is about the same.

comment:7 Changed on Jul 27, 2016 at 10:01:02 AM by dkocher

#9622 closed as duplicate.

comment:8 Changed on Jul 29, 2016 at 10:44:29 AM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r21163.

comment:9 Changed on Jul 30, 2016 at 8:38:49 PM by dkocher

Fix resume in r21172. Always use different upload URI for segments of large uploads for better reliability (r21174).

comment:10 Changed on Jul 30, 2016 at 8:43:34 PM by dkocher

Please update to snapshot build 5.1.20726 or later which should fix this issues with large uploads to B2. Refer to on how to update to a snapshot build.

comment:11 Changed on Aug 4, 2016 at 10:51:42 AM by dkocher

  • Milestone changed from 5.1 to 5.0.11

comment:12 follow-up: Changed on Aug 4, 2016 at 2:49:27 PM by jreiter1975

I installed the snapshot build 5.1.20739 and I haven't seen any issues with the resume so far.

comment:13 in reply to: ↑ 12 Changed on Aug 4, 2016 at 6:26:42 PM by dkocher

Replying to jreiter1975:

I installed the snapshot build 5.1.20739 and I haven't seen any issues with the resume so far.

Thanks for your confirmation!

Note: See TracTickets for help on using tickets.