[tahoe-lafs-trac-stream] [tahoe-lafs] #1791: UploadUnhappinessError with available storage nodes > shares.happy

[tahoe-lafs]

#1791: UploadUnhappinessError with available storage nodes > shares.happy
-------------------------+------------------------
     Reporter:  gyver    |      Owner:  davidsarah
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  undecided
    Component:  unknown  |    Version:  1.9.2
   Resolution:           |   Keywords:  happy
Launchpad Bug:           |
-------------------------+------------------------

Comment (by gyver):

 Yes, I'm quite sure all 7 were active. I start all nodes with a single
 script that in turns:
 - starts the introducer,
 - starts each storage node.
 If one of the expected node can't be started I see it right away in the
 script output when starting the grid.
 At the time of failure, I even checked the web interface of both the node
 I use as a client and the introducer and they both listed all 7 storage
 nodes.
 I even checked that there was plenty of free space on each storage node
 and that there was no configured reserved space that could explain a
 possible node refusal of storing data.

 I just rechecked and noticed something. The server has 3 IP addresses: the
 loopback, a private IP on a local network and a private IP on a VPN
 (managed by OpenVPN). Apparently each node advertises its services on all
 3 IPs (I assume it's by design).
 But the listing of storage nodes given by my "client" node isn't exactly
 consistent with the one given by the introducer.

 Here are the current outputs (there shouldn't be any security problem
 publishing this so I didn't obfuscate anything):

 Introducer's Service Announcements:
 ||= Nickname =||= Advertised IPs =||= Announced =||= Version =||= Service
 name =||
 || store_1 omkzwfx5fconrg4fjqxwt3hdzsmvhfdv || 192.168.0.1 10.8.0.10 ||
 00:45:24 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_2 d3fycappvcjuma7vwc45spfolaei6n24 || 192.168.0.1 10.8.0.10 ||
 00:45:25 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_3 lehmccp7am6cydjh3qsfmdp3scxzprmv || 192.168.0.1 10.8.0.10 ||
 00:45:26 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_4 pa2myijhnj3ld4owmqxsihow4hv2botv || 192.168.0.1 10.8.0.10 ||
 00:45:27 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_5 wo6akhxtren7esuhbtjscmpzvjwuvken || 192.168.0.1 10.8.0.10 ||
 00:45:29 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_6 zp6jpfeudsrxv3n2sz6he3kep3mw3tgr || 192.168.0.1 10.8.0.10 ||
 00:45:30 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||
 || store_8 ughwvrtu7ht6x4xpgr2abbsb457ipcvr || 192.168.0.1 10.8.0.10 ||
 00:45:31 07-Jul-2012 || allmydata-tahoe/1.9.2 || storage ||

 Introducer's Subscribed Clients:

 ||= Nickname =||= PeerID =||= Advertised IPs =||= Connected From =||=
 Since =||= Version =||= Subscribed To =||
 || store_1 || omkzwfx5fconrg4fjqxwt3hdzsmvhfdv || 192.168.0.1 10.8.0.10 ||
 192.168.0.1:54872 || 00:45:24 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_5 || wo6akhxtren7esuhbtjscmpzvjwuvken || 192.168.0.1 10.8.0.10 ||
 192.168.0.1:54949 || 00:45:29 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_2 || d3fycappvcjuma7vwc45spfolaei6n24 || 192.168.0.1 10.8.0.10 ||
 192.168.0.1:54884 || 00:45:25 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_3 || lehmccp7am6cydjh3qsfmdp3scxzprmv || 192.168.0.1 10.8.0.10 ||
 127.0.0.1:55124 || 00:45:26 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_4 || pa2myijhnj3ld4owmqxsihow4hv2botv || 192.168.0.1 10.8.0.10 ||
 127.0.0.1:55143 || 00:45:27 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_6 || zp6jpfeudsrxv3n2sz6he3kep3mw3tgr || 192.168.0.1 10.8.0.10 ||
 127.0.0.1:55207 || 00:45:30 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||
 || store_8 || ughwvrtu7ht6x4xpgr2abbsb457ipcvr || 192.168.0.1 10.8.0.10 ||
 127.0.0.1:55252 || 00:45:31 07-Jul-2012 || allmydata-tahoe/1.9.2 ||
 storage ||

 "The storage node I use as a client"'s status:

 Connected to 7 of 7 known storage servers:
 ||= Service Name =||= Nickname PeerID =||= Connected? =||= Since =||=
 First Announced =||= Version =||
 || storage || store_2 d3fycappvcjuma7vwc45spfolaei6n24 || Yes: to
 127.0.0.1:48397 || 00:45:25 07-Jul-2012 || 00:45:25 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||
 || storage || store_3 lehmccp7am6cydjh3qsfmdp3scxzprmv || Yes: to
 192.168.0.1:38708 || 00:45:26 07-Jul-2012 || 00:45:26 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||
 || storage || store_1 omkzwfx5fconrg4fjqxwt3hdzsmvhfdv || Yes: to
 (loopback) || 00:45:24 07-Jul-2012 || 00:45:24 07-Jul-2012 || allmydata-
 tahoe/1.9.2 ||
 || storage || store_4 pa2myijhnj3ld4owmqxsihow4hv2botv || Yes: to
 10.8.0.10:40626 || 00:45:27 07-Jul-2012 || 00:45:27 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||
 || storage || store_8 ughwvrtu7ht6x4xpgr2abbsb457ipcvr || Yes: to
 10.8.0.10:49604 || 00:45:31 07-Jul-2012 || 00:45:31 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||
 || storage || store_5 wo6akhxtren7esuhbtjscmpzvjwuvken || Yes: to
 127.0.0.1:50958 || 00:45:29 07-Jul-2012 || 00:45:29 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||
 || storage || store_6 zp6jpfeudsrxv3n2sz6he3kep3mw3tgr || Yes: to
 10.8.0.10:52661 || 00:45:30 07-Jul-2012 || 00:45:30 07-Jul-2012 ||
 allmydata-tahoe/1.9.2 ||

 I'm not sure how the service announcement and IP selection works, but
 there seems to be at least some amount of chance involved in the IP
 selection. All nodes should behave themselves in the same way so AFAIK the
 same IP should be selected.

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