On Fri, Jan 31, 2003 at 05:00:41PM +0000, Gordan Bobic wrote: > Hi. > > I've got a problem. Just about ever time I stop my note to upgrade the > library to a newer version, the node refuses to start afterwards. The last Are you sure you stopped it properly? If it was still running it might cause some nasty symptoms. > message in the log is usually starting mainport. Sometimes, quite > infrequently, it will stop a bit before that. Set logLevel=debug, try again, mail me the log. > > The only way to get it to start again after that is to delete the routing > table files and the data store. Otherwise it will always refuse to start. Deleting only the routing table files, or only the datastore, does not cause it to break? > > I have also found that in the latest downloadable version, having too many > node references in the seednodes.ref file will make the node crash during > the process of initializing the routing table. I had about 400 fresh node > references dumped into the file before stopping for the upgrade last time, > and after cleaning out the node to get it to re-start again, it would not > start again until I used an older, smaller seednodes.ref file. 400 is ridiculous. > > Is this normal? What is the maximum number of entries allowed in > seednodes.ref? Why does my node refuse to start again after being stopped Your node only has 50 references in its routing table normally. 400 seednodes is ludicrous. > after 10-20+ hours? Is this a known problem? It seems very > counter-productive to have to delete several GB of data store on every > re-start. No, it's not a known problem, it has not been reported by anyone else, we would like to fix it. > > What configuration options could be to blame? Here are some of the options > I use that I think coulbd be relevant to the problem. > > Any ideas where it's all going wrong? > > rtMaxRefs=64 Hmm. > rtMaxNodes=1024 HMMMM. This is um, a bit high. It's possible that your routing table is always corrupted because it takes so long to write it out that it never actually reaches disk whole. > maxRoutingSteps=64 > storeType=native > storeBlockSize=4096 > storeFile=store > storeSize=17179869184 No problems here. > > Is there something in the handling of the routing tables that dies with > the entries of rtMaxRefs=64 and rtMaxNodes=1024? I upped the rtMaxNodes > number because 256 filled up quite quickly. It looks like it tops out at > 384, presumably, due to the lack of more permanent nodes? I have seen in > the configuration options that the default values for both of these are > 50. I didn't think that upping rtMaxRefs to 64 would hurt things, but the > maximum of 50x50=2500 is a lot less than 64x1024=65536 entries in the > routing table. > > But if it was just the routing table getting corrupted, then why doesn't > deleting just the routing table enough to get the node to start? Why does > the data store need to be deleted as well? And why doesn't the node start > if a big seednodes.ref file is used when the routing table needs to be > pre-seeded (the one I had dumped to a file was over 400KB). I can't tell you why until I find out exactly what it does rather than working. See above. And once the node is up it should find new nodes without needing a seednodes file. > > Could any of this be related to the heisenbug warning/panic I occasionally > see in the log? I doubt it, but you never know. > > Note that the node will run just fine until it is stopped, showing no > sign of problems before stopping. It will just fail to start next time, > sometimes reporting a few lines like "deleting orphaned entry XYZ". > > Thanks. > > Gordan
-- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/JpabimWi840/ ICTHUS.
msg01099/pgp00000.pgp
Description: PGP signature
