[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):

 Replying to [comment:3 davidsarah]:
 > Hmm. d3fycapp and lehmccp7 were the servers that were not contacted in
 the failed upload, and they have IPs 127.0.0.1 and 192.168.0.1
 respectively. But wo6akhxt also has IP 127.0.0.1 and that was contacted in
 the failed upload, so that might be a red herring.

 Note that the assigned IPs are not always the same: a restart of all
 storage nodes reshuffles them. My last failed attempt was with d3fycapp
 and lehmccp7 seen both on 10.8.0.10 (VPN IP) by the client node (5 nodes
 where seen on 10.8.0.10 with ughwvrtu on 192.168.0.1 and the client
 (omkzwfx5) on loopback. It seems the IP addresses used don't change the
 error: I've always seen the same (only 5 servers queried) since the
 problem appeared.

 The problem may not have anything to do with IP address choices but it
 seems to me these inconsistencies are odd enough to keep in mind.

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