Re: [freenet-support] "Freenet Down!"
Oh, come now. Does not anyone remember that a version number below 1.00 or a variation there of means "developmental." As long as any software is developmental it means failures of a new version is almost certain. Even multi-billion companies can seldom produce software that runs on every machine. I can think of one rather large company that can't (won't) even try to make software work if you run anything but their software on a freshly install machine. Need I say who that company is? miguel wrote: For the first time since I started Freenet some 10 months ago it has failed! Build 5085 was fine. 5086... trash. Downhill. It would not find even YoYo, plus, it would just disconnect after 4 or 5 hours. This is a first for me since I usually run Freenet for days without a restart. Enter 5087. THe last time 5086 disconnected I went to my web interface and I found 5087. Great! I'll update and these problems with 5086 will be fixed. Fat chance. Now Freenet won't even connect, period! Log file: Jul 27, 2004 5:21:34 PM (freenet.node.Main, main, ERROR): Caught java.lang.OutOfMemoryError running or seeding node java.lang.OutOfMemoryError This is a first for me. A rollback to 5085 is in order. Danke! (Do I need to polish my German a bit and go to Entropy?) Ich denke das ist nicht sehr gut. Auf wiedersehn Freenet? ___ 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]
[freenet-support] "Freenet Down!"
For the first time since I started Freenet some 10 months ago it has failed! Build 5085 was fine. 5086... trash. Downhill. It would not find even YoYo, plus, it would just disconnect after 4 or 5 hours. This is a first for me since I usually run Freenet for days without a restart. Enter 5087. THe last time 5086 disconnected I went to my web interface and I found 5087. Great! I'll update and these problems with 5086 will be fixed. Fat chance. Now Freenet won't even connect, period! Log file: Jul 27, 2004 5:21:34 PM (freenet.node.Main, main, ERROR): Caught java.lang.OutOfMemoryError running or seeding node java.lang.OutOfMemoryError This is a first for me. A rollback to 5085 is in order. Danke! (Do I need to polish my German a bit and go to Entropy?) Ich denke das ist nicht sehr gut. Auf wiedersehn Freenet? ___ 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] Re: Stable build 5087
Klaus Brüssel schrieb: P.S. I deleted those *_a and *_b files and replaced seednodes.ref with a version that is much smaller (2 nodes) and my node starts up ! ciao --klaus Reading the big seednode files in takes a whole lot of memory. Using an 8MB seednode.ref I had an initial memory usage of more the 200MB when fred starts, which dropped to around 70MB after some minutes. As the current ref has 23MB I suspect the initial memory usage to be gigantic. ___ 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] NPE with build 5087
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) on Linux 2.6.7, Athlon XP using Athlon-optimized jbigi libs from latest freenet-ext.jar. Another bug(?): only transmitting connections are marked as active in /servlet/nodestatus/ocmContents.html?setMode=Connection while others are always shown as idle. Jul 27, 2004 10:35:42 PM (freenet.node.Node, YThread-76, ERROR): Error while receiving message freenet.Message: StoreData@(hopsSinceReset=2,requestsPerHour=10206,dataSource=tcp/x.x.x.x:x, sessions=1, presentations=3, ID=DSA(x x x x x x x x x x), version=Fred,0.5,STABLE-1.50,5084) in state [EMAIL PROTECTED]: key=xx, hopsToLive=17, id=, routes=null, [EMAIL PROTECTED], orig=DSA(x x x x x x x x x x), last=DSA(x x x x x x x x x x)(neverInsert): java.lang.NullPointerException java.lang.NullPointerException at freenet.node.Node.getStringAddress(Node.java:5161) at freenet.node.states.request.AwaitingStoreData.relayStoreData(AwaitingStoreData.java:188) at freenet.node.states.request.AwaitingStoreData.receivedMessage(AwaitingStoreData.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at freenet.node.State.received(State.java:143) at freenet.node.StateChain.received(StateChain.java:177) at freenet.node.StateChain.received(StateChain.java:61) at freenet.node.StateChainManagingMessageHandler$ChainContainer.run(StateChainManagingMessageHandler.java:332) at freenet.node.StateChainManagingMessageHandler$ChainContainer.received(StateChainManagingMessageHandler.java:285) at freenet.node.StateChainManagingMessageHandler$ChainContainer.access$100(StateChainManagingMessageHandler.java:204) at freenet.node.StateChainManagingMessageHandler.handle(StateChainManagingMessageHandler.java:96) at freenet.Ticker$Event.run(Ticker.java:323) at freenet.thread.YThreadFactory$YThread.run(YThreadFactory.java:285) ___ 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] Stable build 5087
Am Dienstag, 27. Juli 2004 23:26 schrieb Toad: > Stable build 5087 is now available. The snapshots have been updated. > Please upgrade. You can do this on Windows by using the update option on Well...upgraded with update.sh on my linux box anf then: - [EMAIL PROTECTED]:~/freenet > ./start-freenet.sh Detected freenet-ext.jar Detected freenet.jar Sun java detected. Starting Freenet now: Command line: java -Xmx128m -XX:MaxDirectMemorySize=128m freenet.node.Main Done [EMAIL PROTECTED]:~/freenet > INFO: Native CPUID library jcpuid loaded from resource INFO: Optimized native BigInteger library 'libjbigi-linux-athlon.so' loaded from resource Caught java.lang.OutOfMemoryError running or seeding node java.lang.OutOfMemoryError Caught, in Main: java.lang.OutOfMemoryError java.lang.OutOfMemoryError - [EMAIL PROTECTED]:~/freenet > cat freenet.log 28.07.2004 01:29:23 (freenet.node.rt.NGRoutingTable, main, ERROR): Caught java.io.IOException: Value out of range: 450.0 deserializing a NodeEstimator for DataObjectRoutingMemory:tcp/220.147.157.155:32367, sessions=1, presentations=3, ID=DSA(6bdd 26bd 0a5f f693 8fe4 9809 0c53 24f9 af1f cc36), version=Fred,0.5,STABLE-1.50,5084:6bdd26bd0a5ff6938fe498090c5324f9af1fcc36 java.io.IOException: Value out of range: 450.0 at freenet.node.rt.BootstrappingDecayingRunningAverage.(BootstrappingDecayingRunningAverage.java:163) at freenet.node.rt.BootstrappingDecayingRunningAverageFactory.create(BootstrappingDecayingRunningAverageFactory.java:36) at freenet.node.rt.SlidingBucketsKeyspaceEstimator.(SlidingBucketsKeyspaceEstimator.java:158) at freenet.node.rt.OptimizingSlidingBucketsKeyspaceEstimator.(OptimizingSlidingBucketsKeyspaceEstimator.java:27) at freenet.node.rt.OptimizingSlidingBucketsKeyspaceEstimatorFactory.createTime(OptimizingSlidingBucketsKeyspaceEstimatorFactory.java:82) at freenet.node.rt.StandardNodeEstimator.(StandardNodeEstimator.java:563) at freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFactory.java:95) at freenet.node.rt.NGRoutingTable.loadEstimators(NGRoutingTable.java:370) at freenet.node.rt.NGRoutingTable.(NGRoutingTable.java:187) at freenet.node.Main.main(Main.java:858) 28.07.2004 01:31:12 (freenet.node.Main, main, ERROR): Caught java.lang.OutOfMemoryError running or seeding node java.lang.OutOfMemoryError - linux kernel 2.6.7 sun jvm Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) questions: 1) builds 5085 and 5086 often crashed with signal 11, can this corrupt the routing table files (those *_a *_b) ? 2) is something wrong with the seednodes.ref ? 3) startup times are much too long lately - only conducted by the big datastore ? How much memory (RAM) is recommended if used with 20+ GB datastore ? P.S. I deleted those *_a and *_b files and replaced seednodes.ref with a version that is much smaller (2 nodes) and my node starts up ! ciao --klaus ___ 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] windows 2000 service
I've spent most of the day trying to get freenet to run as a service in Windows 2000. I'm almost there, but there's one thing that I haven't been able to fix. I used instsrv and srvany to get freenet.exe to run as a service. It works as long as I don't log off of windows. It will start fine when the system boots and still runs when someone logs in. But, as soon as the user logs off, javavm dies. If you log back in, the freenet icon has a flashing ! saying that there's a problem. It will restart, but has the same problem if the user logs off again. ___ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com ___ 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] Stable build 5087
Stable build 5087 is now available. The snapshots have been updated. Please upgrade. You can do this on Windows by using the update option on the start menu. On Linux, OS/X etc, you can update by using the update.sh script (and restart the node). You can alternatively shut down your node and download http://freenetproject.org/snapshots/freenet-latest.jar over your existing freenet.jar, then restart your node. To obtain best performance from this build, you will need to update your freenet-ext.jar. Shut down the node, download the new freenet-ext.jar from http://freenetproject.org/snapshots/freenet-ext.jar , copy it over your existing freenet-ext.jar, and then restart the node. If you do this, and you are using a supported platform (pentium 2/3/4, athlon, on windows or linux), you should get a significant reduction in CPU usage with this build. We have included native code optimizations for the above platforms for certain heavy math operations that Freenet does frequently and that Sun's implementation is not good at. Specifically, on my Athlon XP, I get a factor of 8 performance gain on modPow(), which is a very common operation in asymmetric crypto, and a big part of Freenet's overall CPU usage. I also get a factor of 3 gain in BigInteger.doubleValue(), which is used constantly in routing. Other changes: Fixed several major bugs introduced recently, which generally had the effect of preventing the node from opening connections. These are hopefully the main causes of the problems reported with 5085/5086; obviously the node will not run well if it only has 10 or 20 connections. Also, back off connection attempts to a node if the connection lasts less than 20 seconds. Traffic padding improvements (reduced padding size to 200 bytes, laid the groundwork for further reductions once 5087 is common by no longer sending RequestInterval on all FNP messages, instead send smaller fixed length packet-messages containing the MRI, one with every packet). Fix a rare NPE, delete some unused code, add some comments, change some logging, SuSE wants LD_ASSUME_KERNEL=2.4.1 (not 2.2.5) in start-freenet.sh. -- 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]
[freenet-support] Re: Subscription payment cancel
On Tue, 27 Jul 2004 18:32:19 +0200, "Friso" <[EMAIL PROTECTED]> wrote: >Dear Freenet, > >I would like to cancel my monthly Paypal subscription payment. > >My subscription information: > >Subscription Name: Freenet Project Membership >Subscription Number: S-66D07690XR015150A > >Kind regards, > >Friso Geerlings, >Eindhoven, The Netherlands If I am not mistaken, you are the only one that can cancel that subscription (by logging into paypal with your username and doing it from there). Taken from a faq I found somewhere on the net: 1. Log into PayPal 2. Click "History" 3. Select "Subscriptions" from the "Show:" drop-down box. 4. You may need to select a longer timeframe from the "For:" drop-down box if you have had your account longer than a month. Try selecting "Past Year". 5. Press submit. 6. You should see an entry there for your Freenet subscription. There will be a link in the "Status" column that tells you the status of the subscription. If it says "Active", click it. 7. Click the button that says "Cancel Subscription" and follow the remainder of the steps. Kind regards. -- Jose M. Arnesto j[insert my surname [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]
[freenet-support] Subscription payment cancel
Dear Freenet, I would like to cancel my monthly Paypal subscription payment. My subscription information: Subscription Name: Freenet Project Membership Subscription Number: S-66D07690XR015150A Kind regards, Friso Geerlings, Eindhoven, The Netherlands ___ 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] new stable(part 2)
On Tue, Jul 27, 2004 at 10:12:44AM +0200, Newsbyte wrote: > Connections open (Inbound/Outbound/Limit) 6 (0/6/200) This is the problem. This is caused by a bug I am going to fix. Which affects both branches, and causes connections to fail. -- 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]
[freenet-support] Re: new stable(part 2)
Newsbyte wrote: And that is really crappy: my statusbar is around 1-2% and stays there, no activelinks show up at all, etc. I'm too noticing lower activity. Bandwidth consumption is for sure lower, and the activelink were too irretrievable (until, casually, my last try. Maybe the critical period is ending). I can't retrieve neither FBNI nor YoYo! (are they being inserted in summer? FIND carries a warning in the front page but the others I don't know). Anyway, I'm seeing a bunch of these in the logfile: 26-jul-2004 9:30:05 (freenet.node.rt.NGRoutingTable, main, ERROR): Caught java.io.IOException: Value out of range: 450.0 deserializing a NodeEstimator for DataObjectRoutingMemory:tcp/x.9.x.3x:3, sessions=1, presentations=3, ID=DSA(011f c535 4102 cab4 210f f65d b10d 3441 1374 50df), version=Fred,0.5,STABLE-1.50,5084:011fc5354102cab4210ff65db10d3441137450df java.io.IOException: Value out of range: 450.0 I'm fairly well connected: Connections open (Inbound/Outbound/Limit) 124 (122/2/512) ___ 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] new stable(part 2)
Ok...despite Ian telling me to f- read what toad wrote, what I feared would happen has happend: whether or not I let it run longer, it's still the same. Basically, it's still crap. On the contrary, it seems to get worse the longer I let it on. In the very beginnings, it worked (more or less), but then it went steadily worse, untill nothing was retrievable. After some discussions (and the well-thought of responses on the maillist ;-) ) someone on IIP suggested to update my seednodes.ref. So I did. And indeed, when restarting things seemed to have improved. I thought the seednodes didn't update when using the auto-update, but toad assured me they would/should. And I guess he might be right, because after a while it deteriorated again, untill it was as crappy as before. And that is really crappy: my statusbar is around 1-2% and stays there, no activelinks show up at all, etc. Now, I AM using a router and what not, but it never deteriorated like this before, and build 5085 is supposed to work *better* with routers, right? So, I have basically no idea what is going on (neither do the coders, I suspect ;-)), but I'm pretty sure it's not due to being not well-connected to the network in the normal sense and that it will improve with time. I would send some data on it, if I knew what exactly would be interesting to know. (openconnections?) Connections open (Inbound/Outbound/Limit) 6 (0/6/200) Transfers active (Transmitting/Receiving) 1 (0/1) Data waiting to be transmitted/received None/None Amount of data transmitted/received over currently open connections 2,219 KiB/3,740 KiB Total amount of data transmitted/received 24 MiB/27 MiB Number of distinct nodes connected 6 After a whole night, 24MB seems rather puny. - Original Message - From: Newsbyte To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 23, 2004 11:31 AM Subject: new stable Tried it out, and thusfar...it's crap. Maybe (hope so) this is temporary, but it definately works WAY worse then it used to. Actually, I almost don't get anything exept RNF, DNF and other 'can't connect' messages. I know it's maybe too early to tell, but what if all the changes didn't do a thing (again) to improve Freenet? I mean...we could be busy untill men land on mars and Bush becomes a saint (I would've said an intelligent dude, but I want to keep it remotely possible). If things don't work, and don't keep working, maybe we should make a dramatic departure and throw away the concept of NGR and the current bw/limiting shemes? Maybe we just made it too complicated, and we should revert or at least think about moving it to something more simple again, akin to the classical routing? Also, IMHO, one might implement something that makes a node more keen on (more) rapidly using other nodes it gets aware of, even if they seem - or are - 'less good' then the seednodes. I think the seednodes.ref causes rather an all-to-long-remaining bottleneck when contacting the network. Maybe it will get (preferable much) better, and I truelly hope so, but if it doesn't it has been yet another giant waste of time. I mean, I'm sure there are lots of improvements, but if endusers don't see the difference and still get a crappy working network, it's rather pointless. Maybe I'm just talking in a mood of dissapointment, but, even as a fan of Freenet (or I wouldn't do what I'm doing), I'm getting rather tired of all those months and even years of 'improvements' that just don't seem to materialise into a better, faster Freenet. I've expressed my opinion before: I think the only chance of actually getting somewhere, is by creating a large, 'real-life' testnetwork where the actual workings can be followed in detail. Toads' little network already showed some promise, but falls far short of what is needed. I can't but feel that, if we had done that a year before, we would now be much further in the development and with a good chance of having a working Freenet. ___ 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]
