Hi Kyle! Sorry that I didn't see this before now.
I'm sorry that the error message is so frustrating. Fixing that is the topic of https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2101 (improve error messages from failed uploads). The best solution would be for it to just show, visually, a complete map of which shares went to which servers, and which shares failed when it attempted to send them to which servers, and how each one failed. The issue sounds like #1382. Perhaps you could try the #1382 branch (https://github.com/zooko/tahoe-lafs/tree/1382-rewrite-3) and see if that fixes it! Since it is so nicely reproducible for you. On Sun, Dec 7, 2014 at 10:19 PM, Kyle Markley <k...@arbyte.us> wrote: > > When this error occurs, it has a side-effect of killing any other operation > occurring on the same node at the same time. (If I'm doing two "tahoe > backup" operations, they /both/ die.) But the problem is 100% reproducible > with a simple "tahoe put" operation running by itself. This is really interesting! I really want to understand this. I can't think of any reason why separate operations would effect one another. Could you please trigger an incident report on the gateway and also on the server? Here's how to trigger an incident report: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug Thank you! Regards, Zooko _______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
