Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
On Monday 25 May 2009 07:28:33 3BUIb3S50i 3BUIb3S50i wrote: I also have the same message with another IP. On Mon, May 25, 2009 at 1:26 AM, SmallSister development smallsis...@xs4all.nl wrote: theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! snip Yeah got the same message, 1 ip reports that the auto-update key is blown. Ip is in the range of 193.11.208.0/24. Some Student network in Goteborg. Freenet 0.7 Build #1210 build01210 Freenet-ext Build #26 r23771 ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Version 1179?
On Monday 17 November 2008 20:55:25 bbackde at googlemail.com wrote: > Another thing: anyone also noticed that starting with 1178 freesites > like the Frost freesite or Toads blog are not longer retrievable? > I get a temporary files error ... maybe this is already fixed with 1179. > Yes had that also with 1178 but with 1179 these errors are gone.
[freenet-support] (no subject)
On Monday 17 November 2008 20:27:13 Peter J. wrote: > On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: > > Correct. This should go away after 1178 is mandatory on Sunday, provided > > you restart your node at that point. However, the trend so far suggests > > that it won't go away and is still present. :< In any case we need to be > > told if it happens after Sunday. > > > > Ok Matthew, > > Seems to be still there even with version 1179. > > 11 of your peers are having severe problems (not acknowledging packets even > after 10 minutes). This is probably due to a bug in the code. Please report > it to us at the bug tracker at https://bugs.freenetproject.org/ or at > support at freenetproject.org. Please include this message and what version of > the node you are running. The affected peers (you may not want to include > this in your bug report if they are darknet peers) are: > 70.72.215.120:40858 > 212.202.31.3:43592 > 217.196.213.98:24330 > 88.175.66.28:52590 > 87.179.226.176:50173 > 217.153.12.122:50554 > 212.75.37.89:53150 > 85.229.124.96:13598 > 96.250.239.134:64676 > 86.54.216.133:53061 > 79.202.89.5:39002 > > ___ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or > mailto:support-request at freenetproject.org?subject=unsubscribe Also, node uptime is 3 hours now.
[freenet-support] (no subject)
On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: > Correct. This should go away after 1178 is mandatory on Sunday, provided > you restart your node at that point. However, the trend so far suggests > that it won't go away and is still present. :< In any case we need to be > told if it happens after Sunday. > Ok Matthew, Seems to be still there even with version 1179. 11 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at support at freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: 70.72.215.120:40858 212.202.31.3:43592 217.196.213.98:24330 88.175.66.28:52590 87.179.226.176:50173 217.153.12.122:50554 212.75.37.89:53150 85.229.124.96:13598 96.250.239.134:64676 86.54.216.133:53061 79.202.89.5:39002
Re: [freenet-support] (no subject)
On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: Correct. This should go away after 1178 is mandatory on Sunday, provided you restart your node at that point. However, the trend so far suggests that it won't go away and is still present. : In any case we need to be told if it happens after Sunday. snip Ok Matthew, Seems to be still there even with version 1179. 11 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: 70.72.215.120:40858 212.202.31.3:43592 217.196.213.98:24330 88.175.66.28:52590 87.179.226.176:50173 217.153.12.122:50554 212.75.37.89:53150 85.229.124.96:13598 96.250.239.134:64676 86.54.216.133:53061 79.202.89.5:39002 ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] (no subject)
On Monday 17 November 2008 20:27:13 Peter J. wrote: On Saturday 15 November 2008 18:37:20 Matthew Toseland wrote: Correct. This should go away after 1178 is mandatory on Sunday, provided you restart your node at that point. However, the trend so far suggests that it won't go away and is still present. : In any case we need to be told if it happens after Sunday. snip Ok Matthew, Seems to be still there even with version 1179. 11 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: 70.72.215.120:40858 212.202.31.3:43592 217.196.213.98:24330 88.175.66.28:52590 87.179.226.176:50173 217.153.12.122:50554 212.75.37.89:53150 85.229.124.96:13598 96.250.239.134:64676 86.54.216.133:53061 79.202.89.5:39002 ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] Also, node uptime is 3 hours now. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Version 1179?
On Monday 17 November 2008 20:55:25 [EMAIL PROTECTED] wrote: Another thing: anyone also noticed that starting with 1178 freesites like the Frost freesite or Toads blog are not longer retrievable? I get a temporary files error ... maybe this is already fixed with 1179. Yes had that also with 1178 but with 1179 these errors are gone. snip ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] (no subject)
On Saturday 15 November 2008 09:48:26 Peter J. wrote: > On Saturday 15 November 2008 01:05:57 Mike Cook wrote: > > 2 of your peers are having severe problems (not acknowledging packets > > even after 10 minutes). This is probably due to a bug in the code. Please > > report it to us at the bug tracker at https://bugs.freenetproject.org/ or > > at support at freenetproject.org. Please include this message and what > > version of the node you are running. The affected peers (you may not want > > to include this in your bug report if they are darknet peers) are: > > > > > > My Node > > * Freenet 0.7 Build #1178 r23592M > > * Freenet-ext Build #24 r23199 > > > > Got the same message with the same build of freenet. But I've got 4 peers > reported to have severe problems. Ok I didn't read the other new messages on the list before I read this one. So it is to be expected that this message is gone after Sunday when the new version of freenet is mandatory?
[freenet-support] (no subject)
On Saturday 15 November 2008 01:05:57 Mike Cook wrote: > 2 of your peers are having severe problems (not acknowledging packets even > after 10 minutes). This is probably due to a bug in the code. Please report > it to us at the bug tracker at https://bugs.freenetproject.org/ or at > support at freenetproject.org. Please include this message and what version of > the node you are running. The affected peers (you may not want to include > this in your bug report if they are darknet peers) are: > > > My Node > * Freenet 0.7 Build #1178 r23592M > * Freenet-ext Build #24 r23199 > Got the same message with the same build of freenet. But I've got 4 peers reported to have severe problems.
Re: [freenet-support] (no subject)
On Saturday 15 November 2008 01:05:57 Mike Cook wrote: 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: My Node * Freenet 0.7 Build #1178 r23592M * Freenet-ext Build #24 r23199 snip sig Got the same message with the same build of freenet. But I've got 4 peers reported to have severe problems. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] (no subject)
On Saturday 15 November 2008 09:48:26 Peter J. wrote: On Saturday 15 November 2008 01:05:57 Mike Cook wrote: 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: My Node * Freenet 0.7 Build #1178 r23592M * Freenet-ext Build #24 r23199 snip sig Got the same message with the same build of freenet. But I've got 4 peers reported to have severe problems. snip sig Ok I didn't read the other new messages on the list before I read this one. So it is to be expected that this message is gone after Sunday when the new version of freenet is mandatory? ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Odd startup errors
On Saturday 06 September 2008 20:46:25 Matthew Toseland wrote: > On Saturday 06 September 2008 18:56, Peter J. wrote: > > 3. That could explain alot: > > download: aprox. 3.3 Gib > > upload ? ? : aprox. 2.4 Gib > > That's a fair amount too. The downloads will use a significant amount of > RAM, the uploads will use a huge amount of RAM. You might like to try to > db4o branch, although there's a good chance the uploads won't work ... I > will work on uploads soon... > > Does increasing the memory limit help, or is it as high as you can go > without hitting swap already? > Ok, I set the maximum allocatable memory for java to 1016 MiB. I saw the actual allocated memory rise to around 1000 Mib once then it dropped and it is now fluctuating somewhere between 700 Mib and 850 Mib. The node is now running for 6 hours. The computer is swapping some memory (for the first time actually ;) ) but that doesn't really hurt the performance. Maybe if I drop 100 Mib memory it won't use swap anymore but as I don't notice any significant lost of performance I think I keep it this way. Anyway, thanks for the advise. Greetings
Re: [freenet-support] Odd startup errors
On Saturday 06 September 2008 20:46:25 Matthew Toseland wrote: On Saturday 06 September 2008 18:56, Peter J. wrote: snip 3. That could explain alot: download: aprox. 3.3 Gib upload : aprox. 2.4 Gib That's a fair amount too. The downloads will use a significant amount of RAM, the uploads will use a huge amount of RAM. You might like to try to db4o branch, although there's a good chance the uploads won't work ... I will work on uploads soon... Does increasing the memory limit help, or is it as high as you can go without hitting swap already? Ok, I set the maximum allocatable memory for java to 1016 MiB. I saw the actual allocated memory rise to around 1000 Mib once then it dropped and it is now fluctuating somewhere between 700 Mib and 850 Mib. The node is now running for 6 hours. The computer is swapping some memory (for the first time actually ;) ) but that doesn't really hurt the performance. Maybe if I drop 100 Mib memory it won't use swap anymore but as I don't notice any significant lost of performance I think I keep it this way. Anyway, thanks for the advise. Greetings snip ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Odd startup errors
On Saturday 06 September 2008 19:32:30 Matthew Toseland wrote: > > 3 questions: > 1. Please post your freenet.ini. What's the database memory usage limit > setting set to? > 2. What's the node's memory limit set to? > 3. How much stuff do you have on the queue? Approximate total bytes to > download, and total bytes to upload? > > > Greetings 1. freenet.txt attached 2. I have the maximum Java memory set to 508 MiB 3. That could explain alot: download: aprox. 3.3 Gib upload ? ? : aprox. 2.4 Gib Some information about the used Java version and OS: Maximum Java memory: 508 MiB Available CPUs: 2 Java Version: 1.6.0_07 JVM Vendor: Sun Microsystems Inc. JVM Version: 10.0-b23 OS Name: Linux OS Version: 2.6.25.14-69.fc8 OS Architecture: i386 Greetings -- next part -- fproxy.port= fproxy.enabled=true fproxy.allowedHosts=192.168.1.0/255.255.255.0,0:0:0:0:0:0:0:1 fproxy.advancedModeEnabled=true fproxy.showPanicButton=false fproxy.ssl=false fproxy.bindTo=0.0.0.0,0:0:0:0:0:0:0:1 fproxy.allowedHostsFullAccess=192.168.1.0/255.255.255.0,0:0:0:0:0:0:0:1 fproxy.css=boxed pluginmanager.loadplugin=JSTUN;SNMP;XMLSpider;ThawIndexBrowser;XMLLibrarian;KeyExplorer;Freemail toadletsymlinker.symlinks=/sl/gallery/%23/plugins/plugins.TestGallery/;/sl/search/%23/plugins/plugins.Librarian/ fcp.port=9481 fcp.allowedHosts=127.0.0.1,192.168.1.0/255.255.255.0,0:0:0:0:0:0:0:1 fcp.persistentDownloadsEnabled=true fcp.ssl=false fcp.bindTo=0.0.0.0,0:0:0:0:0:0:0:1 fcp.allowedHostsFullAccess=192.168.1.0/255.255.255.0,0:0:0:0:0:0:0:1 ssl.sslVersion=SSLv3 ssl.sslEnable=false ssl.sslKeyStore=datastore/certs ssl.sslKeyStorePass=freenet ssl.sslKeyPass=freenet node.opennet.enabled=true node.opennet.assumeNATed=true node.opennet.listenPort=19904 node.opennet.alwaysAllowLocalAddresses=true node.opennet.acceptSeedConnections=true node.opennet.bindTo=0.0.0.0 node.testnet.enabled=false node.tempDir=./temp-39242 node.l10n=English node.extraPeerDataDir=./extra-peer-data-39242 node.assumeNATed=true node.outputBandwidthLimit=80KiB node.storeSize=80GiB node.inputBandwidthLimit=-1 node.storeDir=datastore node.ipAddressOverride=83.161.29.2 node.downloadAllowedDirs=all node.listenPort=39242 node.uploadAllowedDirs=all node.name=freenet at somehwere.com node.nodeDir=. node.downloadsDir=downloads node.bindTo=0.0.0.0 console.enabled=false console.ssl=false security-levels.physicalThreatLevel=NORMAL security-levels.friendsThreatLevel=NORMAL security-levels.networkThreatLevel=NORMAL node.updater.extURI=USK at BFa1voWr5PunINSZ5BGMqFwhkJTiDBBUrOZ0MYBXseg,BOrxeLzUMb6R9tEZzexymY0zyKAmBNvrU4A9Q0tAqu0,AQACAAE/ext/21 node.updater.autoupdate=true node.updater.URI=USK at BFa1voWr5PunINSZ5BGMqFwhkJTiDBBUrOZ0MYBXseg,BOrxeLzUMb6R9tEZzexymY0zyKAmBNvrU4A9Q0tAqu0,AQACAAE/update/1161 logger.maxZippedLogsSize=128MiB logger.priority=NORMAL node.load.threadLimit=500 End
[freenet-support] Odd startup errors
On Saturday 06 September 2008 18:56:41 Peter J. wrote: > On Saturday 06 September 2008 17:49:07 Mr. Flibble wrote: > > I'm seeing the following (just by accident - I haven't really had time to > > use freenet since the last update): > > > > INFO | jvm 5 | 2008/09/06 16:34:33 | Key 4745216/5346530 OK (308 dupes, 0 > > failures) > > > > > Should I be concerned about this? > > What does it mean exactly? > > I haven't had chance to see how long this has been happening for yet. > > > > Thanks > > Yeah I'm getting this too. Here Freenet stops (crashes) every 2-4 hours > because it consumes all memory it is allowed to use and when it restarts I > get these messages. Takes a while before freenet is restarted. > > Greetings I'm also getting alot of these messages INFO | jvm 24 | 2008/09/06 19:14:10 | Bogus or unreconstructible key at slot 1019 : freenet.keys.SSKVerifyException: Unknown type byte 0 - lost block 1019 INFO | jvm 24 | 2008/09/06 19:14:10 | Key 1024/8160 OK (0 dupes, 20 failures)
[freenet-support] Odd startup errors
On Saturday 06 September 2008 17:49:07 Mr. Flibble wrote: > I'm seeing the following (just by accident - I haven't really had time to > use freenet since the last update): > > INFO | jvm 5 | 2008/09/06 16:34:33 | Key 4745216/5346530 OK (308 dupes, 0 > failures) > > Should I be concerned about this? > What does it mean exactly? > I haven't had chance to see how long this has been happening for yet. > > Thanks > > Yeah I'm getting this too. Here Freenet stops (crashes) every 2-4 hours because it consumes all memory it is allowed to use and when it restarts I get these messages. Takes a while before freenet is restarted. Greetings
Re: [freenet-support] Odd startup errors
On Saturday 06 September 2008 17:49:07 Mr. Flibble wrote: I'm seeing the following (just by accident - I haven't really had time to use freenet since the last update): INFO | jvm 5 | 2008/09/06 16:34:33 | Key 4745216/5346530 OK (308 dupes, 0 failures) snip loglines Should I be concerned about this? What does it mean exactly? I haven't had chance to see how long this has been happening for yet. Thanks Yeah I'm getting this too. Here Freenet stops (crashes) every 2-4 hours because it consumes all memory it is allowed to use and when it restarts I get these messages. Takes a while before freenet is restarted. Greetings ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Odd startup errors
On Saturday 06 September 2008 18:56:41 Peter J. wrote: On Saturday 06 September 2008 17:49:07 Mr. Flibble wrote: I'm seeing the following (just by accident - I haven't really had time to use freenet since the last update): INFO | jvm 5 | 2008/09/06 16:34:33 | Key 4745216/5346530 OK (308 dupes, 0 failures) snip loglines Should I be concerned about this? What does it mean exactly? I haven't had chance to see how long this has been happening for yet. Thanks Yeah I'm getting this too. Here Freenet stops (crashes) every 2-4 hours because it consumes all memory it is allowed to use and when it restarts I get these messages. Takes a while before freenet is restarted. Greetings I'm also getting alot of these messages INFO | jvm 24 | 2008/09/06 19:14:10 | Bogus or unreconstructible key at slot 1019 : freenet.keys.SSKVerifyException: Unknown type byte 0 - lost block 1019 INFO | jvm 24 | 2008/09/06 19:14:10 | Key 1024/8160 OK (0 dupes, 20 failures) ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Installing Freenet with Yum
Hello, I try to install freenet with Yum. = yum install fred.noarch I'm getting the following error messages: = Downloading Packages: = (1/3): fec-1.0.3-2.noarch 100% |=| 93 kB00:00 = (2/3): fred-0.5-5101.noar 100% |=| 3.2 MB00:04 = http://nightwatch.mine.nu/freenet/stable/fred-0.5-5101.noarch.rpm: [Errno = v-1] Package does not match checksum = Trying other mirror. = (3/3): fred-ext-0.2-1.noa 100% |=| 36 kB00:00 = http://nightwatch.mine.nu/freenet/stable/fred-ext-0.2-1.noarch.rpm: [Errno = -1] Package does not match checksum = Trying other mirror. = Error Downloading Packages: = fred-ext - 0.2-1.noarch: failure: fred-ext-0.2-1.noarch.rpm from = = =freenet-stable: [Errno 256] No more mirrors to try. = fred - 0.5-5101.noarch: failure: fred-0.5-5101.noarch.rpm from =freenet-stable: [Errno 256] No more mirrors to try. Is the problem on my side or on the nightwatch.mine.nu site side? pgpYFfOdzgQKj.pgp Description: PGP signature ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
