I had the same problem as Art and reseeded late yesterday and a couple more times since then. It's now 9 hours since I last reseeded and my node is still seeing minimal traffic. Next to nobody is requesting from me (~400 req in 9 hours) even though I have many incoming connections and despite having about 20 5046 nodes in my RT I still can't retrieve anything of significance. Most requests yield either RNF or an immediate DNF, and there are only ~20 keys in the routing table key histogram. On the node status pages, I see that almost all nodes are in the 'fetching ark' state, and the logfile is reporting a lot of ark lookup failures.
I'm hoping that this is mainly due to the small number of 5046 nodes around at the moment. Kevin. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Edward J. Huff Sent: 30 November 2003 18:16 To: [EMAIL PROTECTED] Subject: Re: [freenet-support] Suddenly unable to connect to network On Sun, 2003-11-30 at 11:34, Art Charbonneau wrote: > I upgraded to version 5046 yesterday, and now I always get the error > message: > > "Couldn't connect to the network. Are you sure you have configured > Freenet correctly? Also make sure that you are connected to the > internet." > > I have not changed anything in my configuration, and I am connected to > the internet. Is the network down, or could this be a bug in 5046? > You need to reseed. The stable network is being disconnected from unstable, but most if not all of your references are to nodes which are still in the unstable network. Get the latest seednodes.ref file http://freenetproject.org/snapshots/seednodes.ref and replace your copy of seednodes.ref. Right now there are 69 distinct nodes listed there. -- Edward J. Huff <[EMAIL PROTECTED]> _______________________________________________ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
