WebDAV upload fails (object usage after disposal)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. configure backup on Linux with WebDAV store (SSL)
2. run backup

What is the expected output? What do you see instead?
Everything works fine until the upload of generated files. This fails (see 
backtrace).

What version of Duplicati are you using? On what operating system?
- Duplicati 1.3, current Debian Squeeze, Mono JIT compiler version 2.6.7

What backend (destination) are you using?
- WebDAV (over SSL)

------------- Backtrace ---------------------
Error: Failed to upload file 
"duplicati-full-content.20120107T170505Z.vol1.zip.aes": The object was used 
after being disposed.

Error: System.Exception: Failed to upload file 
"duplicati-full-content.20120107T170505Z.vol1.zip.aes": The object was used 
after being disposed. ---> System.ObjectDisposedException: The object was used 
after being disposed.
  at System.Net.WebConnection.BeginWrite (System.Net.HttpWebRequest request, System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
  at System.Net.WebConnectionStream.WriteRequestAsync (System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
  at System.Net.WebConnectionStream.BeginWrite (System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at Duplicati.Library.Main.BackendWrapper.PutInternal (Duplicati.Library.Main.BackupEntryBase remote, System.String filename) [0x00000] in <filename unknown>:0 
  at Duplicati.Library.Main.BackendWrapper.ProcessQueue (System.Object dummy) [0x00000] in <filename unknown>:0 
InnerError: System.ObjectDisposedException: The object was used after being 
disposed.
  at System.Net.WebConnection.BeginWrite (System.Net.HttpWebRequest request, System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
  at System.Net.WebConnectionStream.WriteRequestAsync (System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
  at System.Net.WebConnectionStream.BeginWrite (System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0 
Cleanup output:

Original issue reported on code.google.com by i.am.on....@gmail.com on 7 Jan 2012 at 5:28

[GoogleCodeExporter]

I had a simuler experience have you failtoban activated??? if so plz. test if 
user og ip is blocked!

Original comment by tommy.gr...@gmail.com on 8 Jan 2012 at 12:51

[GoogleCodeExporter]

Hi, no failtoban, no firewall is active. The WebDAV connection works within 
Dolphin, cadaver etc.

Meanwhile I tested other backends:
- WebDAV without SSL: no success, same error
- FTP: no success (550, unable to change to folder). Again, this one is working 
with other FTP clients
- File based: working!

I installed full Debian Squeeze mono (package 'mono-complete'), is there 
anything else I need to install? Which mono version is known to be working?

Best, Martin

Original comment by i.am.on....@gmail.com on 8 Jan 2012 at 6:24

[GoogleCodeExporter]

It looks like a problem with Mono being different than the .Net runtime.
The error message is most likely something else, but it is being hidden because 
the other error occurs.
Can you try setting the advanced option "synchronous-upload" to true ?
This will change the way the error occurs and hopefully it will be easier to 
see where the error occurs.

Original comment by kenneth@hexad.dk on 9 Jan 2012 at 2:38

• Changed state: Accepted

[GoogleCodeExporter]

Ok, backup works with 'duplicati-commandline'. 

WebDAV:
Due to lighttpd I had to set the '--disable-expect100-continue' option as I got 
417 HTTP errors. duplicati-commandline did not report those but the same "The 
object was used after being disposed." error.

FTP is fine with the commandline client as well.

I will check tomorrow again with the GUI, async upload seems to be working.

Original comment by i.am.on....@gmail.com on 9 Jan 2012 at 10:51