[freenet-support] Too many ongoing negotiations?
My node: build 534, running on Blackdown JRE 1.4.1. (Can't use Sun JRE, it runs on Linux-Sparc). I don't think I have any nonstandard config settings, except maximumTreads=30. I haven't looked closely at my node for a few weeks (except my traffic stats say it's still doing things)... and now I see that I can't retreive anything anymore: always 'Route Not Found' with all contacted nodes totally unreachable. And I see my logs are full with the following message (about 10 per minute) Too many ongoing negotiations! (7/7) After I raised maximumTrheads to 120, just to see what would happen, I got no success, and: Too many ongoing negotiations! (30/30) Can anyone tell me what this message means, or point me to documentation if it exists? Question #2: I wanted to first upgrade my node to the latest build (541 according to _my_ node), but the latest version I find for downloading is 0.5.0.7! Am I stupid? Where should I look for node upgrades (or are 'normal users' discouraged from keeping their node up-to-date and should they wait until a 0.5.0.8/0.5.2)? ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Too many ongoing negotiations?
On Tue, Jan 07, 2003 at 02:53:37PM +0100, Roderik Muit wrote: My node: build 534, running on Blackdown JRE 1.4.1. (Can't use Sun JRE, Um, 534 is old. Update. it runs on Linux-Sparc). I don't think I have any nonstandard config settings, except maximumTreads=30. I haven't looked closely at my node for a few weeks (except my traffic stats say it's still doing things)... and now I see that I can't retreive anything anymore: always 'Route Not Found' with all contacted nodes totally unreachable. And I see my logs are full with the following message (about 10 per minute) Too many ongoing negotiations! (7/7) After I raised maximumTrheads to 120, just to see what would happen, I What did you have it set to? got no success, and: Too many ongoing negotiations! (30/30) Can anyone tell me what this message means, or point me to documentation if it exists? It's not causing your RNFs. At least with a recent build this is normal and indicates slight overload, but shouldn't stop locally originated requests. Question #2: I wanted to first upgrade my node to the latest build (541 according to _my_ node), but the latest version I find for downloading is 0.5.0.7! Am I stupid? Where should I look for node upgrades (or are 'normal users' discouraged from keeping their node up-to-date and should they wait until a 0.5.0.8/0.5.2)? Use the update script. ./update.sh. This fetches http://freenetproject.org/snapshots/freenet-latest.jar. -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Freenet/Coldstore open source hacker. Contracted full time by Freenet Project Inc. http://freenetproject.org/ ICTHUS. msg02512/pgp0.pgp Description: PGP signature
[freenet-support] Re: Too many ongoing negotiations?
Thanks and sorry. I was so used to updating by hand that update.sh slipped my mind. Build 541 works like a charm. Matthew Toseland wrote: After I raised maximumTrheads to 120, just to see what would happen, What did you have it set to? 30. (Was a leftover from when Kaffe gave me 'out of memory', now keeping it at 120.) ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] temp files
On Mon, Jan 06, 2003 at 06:03:10PM +0100, [EMAIL PROTECTED] wrote: At 22.26 05/01/03 +, you wrote: btw my ./freenet/freenet/store_*/temp dir is empty, and I do not regularl= y=20 delete the files manually. Not surprising. It is cleaned out on node startup. It is not so simple; all 4 nodes I run (539 to 629) had 100Mb or more 629 is ancient. Look for a message in the logs that says FEC Using: some dir - is this the same dir? The node sometimes uses several temp dirs... there have been some improvements recently on unstable. in temp dir that never goes away restarting the node; I need to do that by hand - the orphaned propriety message are diaplayed al lot of time at next restart. Yeah, I'm a little concerned about these. I suspect the looked as valid data and are reused for some reason. A good rm -rf * at startup would be a great idea, if the deletion algoritm is not robust. We do this, in the main temp dir, usually store/temp/. Some secure deletion would be better .. Rewriting doesn't work consistently on journaled FS's, or generally across platforms. We should encrypt the data in the first place with temporary keys if it is a big problem. FWIW. Marco -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Freenet/Coldstore open source hacker. Contracted full time by Freenet Project Inc. http://freenetproject.org/ ICTHUS. msg02536/pgp0.pgp Description: PGP signature
RE: [freenet-support] Still not announcing..
Looking in your logfile I can see a couple of failed announcement attempts, I have taken a couple of guesses on what they might mean: 216.187.243.77:32374 - Peer hung up ---broken or maybe firewalled node Cannot connect to: check.ath.cx:41552 ---Node not running or have announced wrong address for itself or similar) Cannot connect to: check.ath.cx:41552 ---Node not running or have announced wrong address for itself or similar) 216.187.243.77:32374 - Peer hung up ---broken or maybe firewalled node Cannot connect to: check.ath.cx:41552 ---Node not running or have announced wrong address for itself or similar) Announcement attempt failed: freenet.Message: QueryRejected (possibly 64.32.194.167:21279) Node to busy to answer (Matthew, maybe log node-address here too?) 216.187.243.77:32374 - Peer hung up ---broken or maybe firewalled node Best shot would probably be to have a larger seednodes.ref, all your current ref:s seems to be broken.. /N ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
