On Thu, Feb 20, 2003 at 09:28:42AM -0600, Glenn Crocker wrote: > > I've got a clean install of 561 that has been running for 20 hours. I set > the announce delay to 3000 to speed things up, and have downloaded a bunch > of stuff. I haven't done any deliberate key insertions, but I think my FEC > download may have inserted missing blocks. I have 50 node references and > the "client" side of Freenet seems to be up and working well. > > My node has announcedTo Events=9, Value Change=20 (for the day). I have a > lot of log entries like "Announcement failed to a292 2a5a a443 18ea 6666 > b287 4f78 80bb 1642 050e at depth 2." And I have 49 incoming key requests.
Have you seen ANY successful announcements? > > Question: What causes announcements to fail? Lots of things. But if your node is receiving some incoming requests... and some successful incoming connections (check the diagnostics), that eliminates most things... > > In loadStats, I have 28 entries and globalRequestsPerHour: 3881.625 localRequestsPerHour is what? > > My concern is that when 0.5.1 launches there will be a LOT of nodes exactly > like mine leeching from the network and bringing the big Freenet nodes to > their knees. It's possible (and I'd say hard to tell) that the network just > "doesn't need" my node at this point, or maybe it's deliberate that nodes > are integrated this slowly. Yeah. If there is a big problem with announcement, we have serious difficulties. > > I'm using the node reference list the windows web installer defaults to. > This seems like a key risk point for the release. If it's getting the same > 50 nodes for every new user, those 50 are going to be hurting. Yeah, which is why it's closer to 150. However the Main.seedRoutingTable method only uses the last 50... I have committed a fix for this to unstable, but it needs some testing. Looking into my node logs... SEC Feb 21, 2003 1:07:54 AM (freenet.node.states.announcing.SendAnnouncement, FThread-1, MINOR): Sending NodeAnnouncement failed: freenet.ConnectFailedException: Against peer DSA(e86a a3b4 c550 dcd4 7e99 3e2b b805 a245 4758 f590) @ 128.211.145 .133:2810 - Cannot connect to: 128.211.145.133:2810 (terminal) SEC Feb 21, 2003 1:07:54 AM (freenet.node.states.announcing.SendAnnouncement, FThread-1, MINOR): Sending NodeAnnouncement failed: freenet.ConnectFailedException: Against peer DSA(19c3 eb47 b0fb 4ff4 28ac 978b 699b d9de 680a 7db4) @ chapweske.c om:17215 - Cannot connect to: chapweske.com:17215 (terminal) SEC Feb 21, 2003 1:07:54 AM (freenet.node.states.announcing.SendAnnouncement, FThread-1, MINOR): Sending NodeAnnouncement failed: freenet.ConnectFailedException: Against peer DSA(708f 4edd 8759 53b4 3f69 7fb1 57e9 d218 2e85 eb58) @ 68.45.166.1 15:6521 - Exceeded blocked connection limit: 1 for 68.45.166.115:6521 (terminal) All three were in my ancient seednodes file. I was under the impression that reannouncements caused by low traffic were sent to nodes from the routing table... it would seem that this is not the case. > > Question: Is there anything that needs to be done to "spread the network > out" during (or before) launch? > > -glenn > -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/1AmszPTmr3I/ ICTHUS.
msg07010/pgp00000.pgp
Description: PGP signature
