I'm forwarding this to devl as this seems the more appropriate list. (Previously only appeared on support).
-------- Original Message -------- Subject: [freenet-support] Getting a stable node Date: Sun, 04 May 2003 12:42:40 +0200 From: Menno Jonkers <[email protected]> Reply-To: devl at freenetproject.org To: devl at freenetproject.org CC: support at freenetproject.org [moved intro to bottom] Questions/remarks: 1) Does anyone have a node that actively runs for a number of days unattended without major problems? If so, I'd be interested to know your setup. 2) Does anyone have a monitor/restart tool for Freenet or hints on other ways to make it more self healing? I'm willing to help out by sending detailed bug reports and maybe even dig into the source code, but I'm not sure on what build or what problem to focus my energy. 4) What's the release policy for reaching a stable 0.52? Build 592 has been dubbed rc1, should I focus on that version? Or on the latest stable? 5) Bug tracking doesn't seems very formal currently. It would help a lot if the dev team gave feedback on all bugs posted. What are you guys already working on? 6) What kind of info should I sent along with my report? (And what's the sensitive data I should _not_ send along?) 7) Remark: the download page on freenetproject.org only offers 0.5.2rc1. Shouldn't it also offer the last non-beta / rc release? Bottom-line: I'm looking for a way to get my permanent node running properly and am willing to contribute to the project (if I can spend my time effectively). Cheers, Menno [intro] Hi, A couple of weeks ago I installed Freenet, having last looked at it over a year ago. Performance and usability have improved a lot, congratulations for the development team for that! I'm now trying to run a permanent node, but fail to reach a setup that will run unattended for more than a few hours. I'll summarize my questions/findings below, leaving out detailed error reports at this stage. The environment is a 256Mb PIII 800Mhz Red Hat 9 machine on a 512/256 ADSL connection that's basically dedicated to run Freenet with a 10Gb store. I've tried most builds from 588 onward; all with Sun JDK 1.4.1_02, some with JDK 1.4.2-beta; with both the default configuration and with more constrained configurations and a max heap of 128Mb for the JVM. I'm currently on build 593 with JDK 1.4.2. My node has gotten well connected in the Freenet work, pushing out data at max bandwidth with a few thousand local queries per hour. But after 1-5 hours performance collapses: routing time becomes a few thousand milliseconds, all incoming requests are rejected, but no bytes are sent and the number of inbound connections is much higher than the number of outbound connections. There's hardly any network, cpu or disk activity. The log shows some debug exceptions at CPAlgoRoutingTable.isRoutable and a lot of out of memory errors "while receiving message" - even though according to the Environment page the JVM has 10's of unused Mbs. Restarting the node "fixes" the situation and I'll probably put a monitor on it that does so automatically anyway, but that doesn't seem to be a very structural solution. _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
