Re: [freenet-support] Stable build 5087

2004-07-28 Thread Klaus Brüssel 
Am Mittwoch, 28. Juli 2004 01:49 schrieb Klaus Brüssel:
 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

 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 !

The node now runs smooth (uptime 9 hours 56 minutes, with frost running)

Some stats:

Connections open (Inbound/Outbound/Limit)
53 (41/12/200)
Transfers active (Transmitting/Receiving)
286 (241/45)
Data waiting to be transferred
33 KiB
Total amount of data transferred
753 MiB

Uptime:   0 days,   9 hours,   56 minutes 
 Current routingTime: 1119ms. 
 Pooled threads running jobs: 45 (45%)   [Rejecting incoming connections 
and requests!] 
 Pooled threads which are idle: 13
 It's normal for the node to sometimes reject connections or requests for a 
limited period. If you're seeing rejections continuously the node is 
overloaded or something is wrong (i.e. a bug). Current estimated load for 
rate limiting: 665,2%. 
Load due to thread limit = 45%
Load due to routingTime = 111,9% = 1119ms / 1000ms  overloadLow (100%)
Load due to messageSendTimeRequest = 665,2% = 6651ms / 1000ms  overloadLow 
(100%)
Load due to output bandwidth limiting = 70,2% because outputBytes(269389) = 
limit (384000,006 ) = outLimitCutoff (0,8) * outputBandwidthLimit (8000) * 60
Load due to expected inbound transfers: 7,9% because: 21987.039935646477 
req/hr * 0.00318876043202 (pTransfer) * 265017.0 bytes = 18580713 
bytes/hr expected from current requests, but maxInputBytes/minute = 3571834 
(max observed bytes per minute) * 60 * 1.1 = 235741044 bytes/hr target
 Current estimated load for QueryRejecting: 35%.
-

I don't complain anymore :-) Good work !

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]

Re: [freenet-support] Stable build 5087

2004-07-28 Thread Ian Clarke 
Toad wrote:
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.
Note that recent versions of the update.sh script on Linux machines will 
detect this and automatically upgrade freenet-ext.jar.

Ian.
___
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

2004-07-27 Thread Klaus Brüssel 
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.init(BootstrappingDecayingRunningAverage.java:163)
at 
freenet.node.rt.BootstrappingDecayingRunningAverageFactory.create(BootstrappingDecayingRunningAverageFactory.java:36)
at 
freenet.node.rt.SlidingBucketsKeyspaceEstimator.init(SlidingBucketsKeyspaceEstimator.java:158)
at 
freenet.node.rt.OptimizingSlidingBucketsKeyspaceEstimator.init(OptimizingSlidingBucketsKeyspaceEstimator.java:27)
at 
freenet.node.rt.OptimizingSlidingBucketsKeyspaceEstimatorFactory.createTime(OptimizingSlidingBucketsKeyspaceEstimatorFactory.java:82)
at 
freenet.node.rt.StandardNodeEstimator.init(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.init(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]