[tahoe-lafs-trac-stream] [tahoe-lafs] #1679: Nondeterministic NoSharesError for direct CHK download in 1.8.3 and 1.9.1

[tahoe-lafs]

#1679: Nondeterministic NoSharesError for direct CHK download in 1.8.3 and 1.9.1
--------------------------+------------------------------------
     Reporter:  nejucomo  |      Owner:  nejucomo
         Type:  defect    |     Status:  new
     Priority:  critical  |  Milestone:  soon
    Component:  code      |    Version:  1.8.3
   Resolution:            |   Keywords:  download heisenbug lae
Launchpad Bug:            |
--------------------------+------------------------------------
Changes (by Zancas):

 * owner:  somebody => nejucomo


Old description:

> Hi,
>
> I have two separate tahoe clients on two separate hosts.  One is version
> 1.8.3 and is able to retrieve a capability, the other is 1.9.1 and says
> (in browser):
>
> {{{
> NoSharesError: no shares could be found. Zero shares usually indicates a
> corrupt URI, or that no servers were connected, but it might also
> indicate severe corruption. You should perform a filecheck on this object
> to learn more.
>
> The full error message is:
> no shares (need 1). Last failure: None
> }}}
>
> Both web apis show the same introducer furl with a connected status and
> the same storage servers with connected status.
>
> The full version blobs from the UI:
>
> This one *succeeds*:
> {{{
> allmydata-tahoe: 1.8.3, foolscap: 0.6.1, pycryptopp: 0.5.29, zfec: 1.4.5,
> Twisted: 11.0.0, Nevow: 0.10.0, zope.interface: unknown, python: 2.7.2+,
> platform: Linux-Ubuntu_11.10-x86_64-64bit_ELF, pyOpenSSL: 0.12,
> simplejson: 2.1.6, pycrypto: 2.3, pyasn1: unknown, mock: 0.7.1, sqlite3:
> 2.6.0 [sqlite 3.7.7], setuptools: 0.6 [distribute] Warning: dependency
> twisted-web (version 11.0.0) found by pkg_resources not found by import.
> Warning: dependency twisted-core (version 11.0.0) found by pkg_resources
> not found by import.
> }}}
>
> This one gives the {{{NoSharesError}}} response page:
>
> {{{
> allmydata-tahoe: 1.9.1, foolscap: 0.6.3, pycryptopp: 0.5.29, zfec:
> 1.4.22, Twisted: 11.1.0, Nevow: 0.10.0, zope.interface: unknown, python:
> 2.7.2+, platform: Linux-debian_wheezy/sid-i686-32bit_ELF, pyOpenSSL:
> 0.13, simplejson: 2.2.0, pycrypto: 2.4, pyasn1: unknown, mock: 0.7.2,
> sqlite3: 2.6.0 [sqlite 3.7.7], setuptools: 0.6 [distribute]
> }}}

New description:

 Hi,

 I have two separate tahoe clients on two separate hosts.  One is version
 1.8.3 and is able to retrieve a capability, the other is 1.9.1 and says
 (in browser):

 {{{
 NoSharesError: no shares could be found. Zero shares usually indicates a
 corrupt URI, or that no servers were connected, but it might also indicate
 severe corruption. You should perform a filecheck on this object to learn
 more.

 The full error message is:
 no shares (need 1). Last failure: None
 }}}

 Both web apis show the same introducer furl with a connected status and
 the same storage servers with connected status.

 The full version blobs from the UI:

 This one *succeeds*:
 {{{
 allmydata-tahoe: 1.8.3, foolscap: 0.6.1, pycryptopp: 0.5.29, zfec: 1.4.5,
 Twisted: 11.0.0, Nevow: 0.10.0, zope.interface: unknown, python: 2.7.2+,
 platform: Linux-Ubuntu_11.10-x86_64-64bit_ELF, pyOpenSSL: 0.12,
 simplejson: 2.1.6, pycrypto: 2.3, pyasn1: unknown, mock: 0.7.1, sqlite3:
 2.6.0 [sqlite 3.7.7], setuptools: 0.6 [distribute] Warning: dependency
 twisted-web (version 11.0.0) found by pkg_resources not found by import.
 Warning: dependency twisted-core (version 11.0.0) found by pkg_resources
 not found by import.
 }}}

 This one gives the {{{NoSharesError}}} response page:

 {{{
 allmydata-tahoe: 1.9.1, foolscap: 0.6.3, pycryptopp: 0.5.29, zfec: 1.4.22,
 Twisted: 11.1.0, Nevow: 0.10.0, zope.interface: unknown, python: 2.7.2+,
 platform: Linux-debian_wheezy/sid-i686-32bit_ELF, pyOpenSSL: 0.13,
 simplejson: 2.2.0, pycrypto: 2.4, pyasn1: unknown, mock: 0.7.2, sqlite3:
 2.6.0 [sqlite 3.7.7], setuptools: 0.6 [distribute]
 }}}

--

Comment:

 Per zooko's "P.S." the linked changes have been implemented.

 https://leastauthority.zendesk.com/entries/21800143-500-internal-error-
 from-s3-fixed

 It's quite possible that this fixed the bug.  I'm reluctant to close the
 ticket without confirmation from nejucomo.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1679#comment:14>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage