[freenet-support] Webinterface with 6495
I yesterday executed the update.sh script and got that way the 6495 build. But I had to reinstall the old build a hour later, because with 6495 build the webinterface stopped working. At least I could not access it with any network computer I tried, and that worked all builds before. I cannot test, if the webinterface works at the node-pc, since that computer is running only in the console mode of linux, and I do not now enough linux commands to test, if the PC is even listening on the right port and so on. (and the xserver is broken on that pc, no way to get a graphical interface there, without having to mess with a lot linux things, which I do not understand...) I will try another update now, but I wanted to report this, since I have not read of a similar problem with that build until now in the support group. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] RNF
I have asked this question before with no answer so I am asking again. I have 50 node references in my RT. So why are only one or two being contacted or at times none at all? I reseed regularly. Freenet Route Not Found Network Error Couldn't retrieve key: [EMAIL PROTECTED]/why.html Hops To Live: 10 Error: Route Not Found Attempts were made to contact 0 nodes. 0 were totally unreachable. 0 restarted. 0 cleanly rejected. The request couldn't even make it off of your node. Try again, perhaps with the GPL to help your node learn about others. The publicly available seed nodes have been very busy lately. If possible try to get a friend to give you a reference to their node instead. Route Not Found messages mean that your node, or the rest of the network, didn't find the data or enough nodes to send the request to. You should retry, with the same Hops-To-Live; if it persists, there may be a problem (check that your internet connection is working). Try reseeding your node, and if that doesn't work, contact [EMAIL PROTECTED] Change Hops To Live to and --- Robert Greenage --- [EMAIL PROTECTED] --- EarthLink: It's your Internet. hops.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.pngspace15_15.png___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
RE: [freenet-support] RNF
This happens when all nodes are backed-off (usually due to their min request intervals). Doc ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Webinterface with 6495
New unstable builds webinterface is broken for me too. If I go back to 6493 the webinterface works again so I do not belive it is my settings, etc. I am running windows xp here. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 04, 2004 4:22 AM Subject: [freenet-support] Webinterface with 6495 I yesterday executed the update.sh script and got that way the 6495 build. But I had to reinstall the old build a hour later, because with 6495 build the webinterface stopped working. At least I could not access it with any network computer I tried, and that worked all builds before. I cannot test, if the webinterface works at the node-pc, since that computer is running only in the console mode of linux, and I do not now enough linux commands to test, if the PC is even listening on the right port and so on. (and the xserver is broken on that pc, no way to get a graphical interface there, without having to mess with a lot linux things, which I do not understand...) I will try another update now, but I wanted to report this, since I have not read of a similar problem with that build until now in the support group. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Webinterface with 6495
I will try another update now, but I wanted to report this, since I have not read of a similar problem with that build until now in the support group. It failed, too. Just now I run that build without the webinterface, but I will switch back to the old build, soon. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] [toad@amphibian.dyndns.org: [Tech] Unstable build 6499]
Some people on support were having problems with unstable. If you run unstable you should read tech or devl and upgrade daily or so. - Forwarded message from Toad [EMAIL PROTECTED] - To: [EMAIL PROTECTED], [EMAIL PROTECTED] From: Toad [EMAIL PROTECTED] Cc: Subject: [Tech] Unstable build 6499 X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.4 Reply-To: [EMAIL PROTECTED] List-Id: tech.freenetproject.org List-Unsubscribe: http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/tech, mailto:[EMAIL PROTECTED] List-Archive: http://dodo.freenetproject.org/pipermail/tech List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/tech, mailto:[EMAIL PROTECTED] Freenet unstable build 6499 is now available. The snapshots have been updated. Please upgrade. The major change in this build is a gross and horrible hack to make the node start up when running on Windows. It appears we are still using a utility called winconfig on Windows. This produces config files where *everything* is hard-coded, and nothing can be changed by the node, with the result that the network is stuck with ancient settings for key network parameters. Hence when we renamed InsertServlet_ to InsertServlet, Windows machines with existing ini files could no longer start up the unstable branch Freenet. A horrible hack has been introduced (when we see InsertServlet_, change it to InsertServlet), but a longer term solution would be nice and would help w.r.t. network issues. However, at least Windows unstable nodes will run now. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. ___ Tech mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/tech - End forwarded message - -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
