Okay, It looks like your node knows about 30 other nodes. You're using port 13906, and your own node's seed looks okay. I noticed that your logging is set to "normal". You can change this to "minor" to see more details about what is going on. However, make sure you clear your log file every once in a while (it can get pretty big, mine is 40MB now). You can clear your log file by simply deleting it.
Also, are you able to access any files from the network? If you are, then you are all set. You don't need to worry about the IO errors. There will always be some errors, and the node will handle them. However, I think I've had the same problem that you're having now. I'm not sure exactly what fixed it, because I tried several things. When I had the problem, my node wasn't starting at all, or it did start, and when it started to say IO error in Servlet, it stopped working. I don't know exactly what causes that error. You may want to try the following steps: 1. Make sure you are running the latest snapshot. On windows you would simply run the update snapshot script. Since you're running linux, I don't know how you should do it. If you figure it out, please tell me how you got it to work. See if this solves to problem. 2. Add the contents of the attached seednodes.ref file to your seednodes.ref. I've sent you my node refs. My node knows about 100 other nodes on the network. If you are still having serious problems (I.E., the node doesn't work and you can't access and data, including the Freedom Engine) go to step 3. 3. Remove Freenet COMPLETELY. Reinstall from scratch. Restore your old preferences in freenet.conf. Import all the seed nodes you can. Repeat step 2. If none of this works, the problem may not be in your node. Sometimes, if the nodes your node knows are not working or are overloaded, it can take a while for your node to be fully integrated into the network. Leave your node running for a few hours/days. Keep coming back to in periodically and try to retrieve documents. It took me a while for my node to start working. My node's seed should help speed up the integration process. The network as a whole has been experiencing massive overloading. Recent builds (471 and higher) have improvements to help combat this. Hopefully, the network should be in a good condition soon. Good luck, Wesley. > -----Original Message----- > From: Marion Bates [mailto:[EMAIL PROTECTED]] > Sent: Saturday, 29 June, 2002 15:25 > To: [EMAIL PROTECTED] > Subject: RE: [freenet-support] Freenet broken today. > > > --- You wrote: > If you want, you can send me the following files: > > freenet.ini (or freenet.conf on Linux) > seednodes.ref > myown.ref > -------- > > Enclosed -- thanks for the assistance! > > -------- > Also, you can > tell me the size, but DON'T SEND THE WHOLE FILE, of node_16966 and > store_16966 (the numbers will vary, depending on which port number you use > for freenet). > ---------- > > Sure. Here's the dir listing: > > -rw-rw-r-- 1 mbates mbates 735 Jun 29 17:39 node_13906 > -rw-rw-r-- 1 mbates mbates 209715200 Jun 29 17:53 store_13906 > > ---------- > If you want, you can send me the snippet of your log file that > you are refering to, but please don't send the whole thing. > --- end of quote --- > > I am just about to post the latest errors from the log to the > support list. I seem to get a different set of errors every time > I reinstall and re-run Freenet. :/ Here's what I'm about to send: > > ----------- > I just hosed the install (again) and started from scratch. I also > reverted to Kaffe, though that doesn't seem to really matter. > > I'm not getting the startup errors now, but still getting a fair > number of new and exciting I/O errors. These began right after > the "finished initializing store" line in the log: > > 29-Jun-02 5:47:13 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-76): I/O error in servlet > 29-Jun-02 5:47:13 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-32): I/O error in servlet > 29-Jun-02 5:47:14 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-74): I/O error in servlet > 29-Jun-02 5:47:14 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-79): I/O error in servlet > 29-Jun-02 5:47:14 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-78): I/O error in servlet > 29-Jun-02 5:47:14 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-3): I/O error in servlet > 29-Jun-02 5:47:14 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-18): I/O error in servlet > 29-Jun-02 5:47:17 PM > (freenet.interfaces.servlet.SingleHttpServletContainer, > PThread-77): I/O error in servlet > 29-Jun-02 5:47:21 PM (freenet.node.states.data.ReceiveData, > PThread-8): I/O error while moving data: CB_RECV_CONN_DIED > java.io.IOException: Could not read all the expected data, read 0 of 1025 > at java.lang.Throwable.fillInStackTrace(Throwable.java:native) > at java.lang.Throwable.<init>(Throwable.java:38) > at java.lang.Exception.<init>(Exception.java:24) > at java.io.IOException.<init>(IOException.java:25) > at > freenet.node.states.data.ReceiveData.received(ReceiveData.java:102) > at freenet.node.StateChain.received(StateChain.java:115) > at freenet.node.StateChain.received(StateChain.java:41) > at > freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHand > ler.java:182) > at > freenet.node.StandardMessageHandler$Ticket.received(StandardMessag > eHandler.java:133) > at > freenet.node.StandardMessageHandler$Ticket.access$0(StandardMessag > eHandler.java:line unknown, pc 0x87586ba) > at > freenet.node.StandardMessageHandler.handle(StandardMessageHandler.java:66) > at freenet.Ticker$Event.run(Ticker.java:196) > at > freenet.thread.PThreadFactory$PThread.run(PThreadFactory.java:138) > > (repeated) > > and I'm seeing DNFs but at least not RNFs. > --------------- > > Thanks again, I really appreciate your willingness to try to help > me out! :) > > -- MB >
seednodes.ref
Description: Binary data
