Re: [freenet-support] bug in run.sh
On Monday 28 Jan 2013 22:08:43 Ken T Takusagawa wrote: run.sh for Linux has if test $DIST_OS == macosx This should be a single = sign, not == to be POSIX compliant. (Bug discovered using Debian's default dash instead of bash as /bin/sh.) It might be best to post a pull request? I can do this fix manually but if there are going to be more ... ? signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug: 'There is a missing line in the http:/...'
On Thursday 19 November 2009 15:28:48 UserVoice wrote: jee...@gmail.com wrote: There is a missing line in the http://freenetproject.org/download.html [http://freenetproject.org/download.html] headless install description. After freenet07.tar.gz is unpacked, ./bin/1run.sh should be executed On http://freenetproject.org/download.html [http://freenetproject.org/download.html] Using Mozilla/5.0 (X11; U; Linux x86_64; lt; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5 I disagree, run.sh automatically runs 1run.sh, doesn't it? Anyway, I've filed a bug. signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug: 'Running * Freenet 0.7.5 Build #12...'
On Saturday 23 January 2010 06:29:22 UserVoice wrote: thorns...@yahoo.com wrote: Running * Freenet 0.7.5 Build #1239 build01239 * Freenet-ext Build #26 r23771 Win XP sp3 all patches installed Java - Sun version 6 update 16 build 1.6.0_16b01 In sun Virtual Box 3.08 OSE R53138 Header from VB Log: 00:00:07.273 VirtualBox 3.0.8_OSE r53138 linux.amd64 (Oct 15 2009 05:04:01) release log 00:00:07.273 Log opened 2010-01-19T16:49:13.448194000Z 00:00:07.273 OS Product: Linux 00:00:07.273 OS Release: 2.6.31-17-generic 00:00:07.273 OS Version: #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 00:00:07.273 Host RAM: 3962MB RAM, available: 3567MB VM memory available ~ 1.5GB Virtual Drive 90GB, formated fat32, encrypted with Truecrypt Attempted to see Get latest node's logfile from the stats page. Error: Internal error: please report java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringEncoder.encode(Unknown Source) at java.lang.StringCoding.encode(Unknown Source) at java.lang.String.getBytes(Unknown Source) at freenet.clients.http.Toadlet.writeReply(Toadlet.java:193) at freenet.clients.http.Toadlet.writeHTMLReply(Toadlet.java:177) at freenet.clients.http.WelcomeToadlet.handleMethodGET(WelcomeToadlet.java:317) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at freenet.clients.http.ToadletContextImpl.handle(ToadletContextImpl.java:504) at freenet.clients.http.SimpleToadletServer$SocketHandler.run(SimpleToadletServer.java:751) at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227) at freenet.support.io.NativeThread.run(NativeThread.java:101) Thaw reports node memory bouncing from 160-180MB/190MB * Used Java memory: 175 MiB * Allocated Java memory: 190 MiB * Maximum Java memory: 190 MiB * Running threads: 130/500 * Available CPUs: 1 * Java Version: 1.6.0_16 * JVM Vendor: Sun Microsystems Inc. * JVM Version: 14.2-b01 * OS Name: Windows XP * OS Version: 5.1 * OS Architecture: x86 On http://data.freenetproject.org/alpha/installer/linux [http://data.freenetproject.org/alpha/installer/linux] Using Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.7 Hi! Sorry for the long delay in answering the bug report! How many downloads and uploads (total GB) did you have queued? Which plugins did you have loaded? Have you tried increasing the node's memory limit? (Shut down, edit wrapper.conf, set the max memory to 512 or so)? Are there any other symptoms - high CPU usage, heavy disk access, general system unresponsiveness? signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] bug
On Tuesday 29 December 2009 21:58:28 thibaud gaiguant wrote: Viewing Issue Simple Details [ Jump to Noteshttps://bugs.freenetproject.org/view.php?id=2692#bugnotes ] [ View Advancedhttps://bugs.freenetproject.org/bug_view_advanced_page.php?bug_id=2692 ] [ Issue Historyhttps://bugs.freenetproject.org/bug_view_page.php?bug_id=2692history=1#history ] [ Print https://bugs.freenetproject.org/print_bug_page.php?bug_id=2692 ] ID Category Severity Reproducibility Date Submitted Last Update 0002692 [Freenet] fred minor N/A 2008-11-14 20:59 2009-12-24 08:24 Reporter Artefact2 View Status publicAssigned To Priority high Resolution openStatus new Product Version 0.7 Summary 0002692: peers forcibly disconnected due to not acknowledging packets Description 1 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/ [^ https://bugs.freenetproject.org/] or at supp...@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.171.218.217:61620 Additional Information * Freenet 0.7 Build 0001178 https://bugs.freenetproject.org/view.php?id=1178 r23592 * Freenet-ext Build 024https://bugs.freenetproject.org/view.php?id=24r23199 Tags No tags attached. milestone 0.8 svn-revision 23592 Sorry, known bug, will be fixed when we get around to it, new versiions of Freenet no longer bug users about it. signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug Tracker
On Sunday 07 March 2010 09:31:39 davide...@riseup.net wrote: Failure to confirm receipt of packets by N. 1 peer, possibly caused by a 'bug' (defect) in the program, my freenet version is 0.7.5. I don't think Freenet reports this any more. Sorry for wasting your time (and for your email getting so severely delayed). If you get it again please tell us. signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug: 'A IOException occred'
Sorry it has taken so long to get back to you. Did you ever get Freenet working? There were some temporary problems with downloading around Christmas. They should be fixed now. Please let us know if you have any more problems. Thanks for trying Freenet! On Tuesday 08 December 2009 06:35:14 UserVoice wrote: bibinsu...@macfast.org wrote: A IOException occred On http://freenetproject.org/ [http://freenetproject.org/] Using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5 signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug: 'Freenet Starter ErrorFreenet Starte...'
You tried to install Freenet in November. Sorry we haven't been able to get back to you. Anyway, the bug may be fixed by the current installer; please try again and let us know whether it works. Thanks for trying Freenet! On Thursday 26 November 2009 22:35:11 UserVoice wrote: paladin_squ...@live.com wrote: Freenet Starter Error Freenet Starter was unable to control the Freenet System Service. Reason: Service did not respond to signal. If the problem keeps occurring, try reinstalling Freenet or report this error message to the developers. Installed the program three times, got this error during installation once and each time running the program. Running XP Pro SP3 on 1ghz 1gb RAM laptop, 54mpbs wireless internet. Feedback would be appreciated. On http://freenetproject.org/download.html [http://freenetproject.org/download.html] Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 (.NET CLR 3.5.30729) signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug: 'Freenet Starter ErrorFreenet Starte...'
On Friday 27 November 2009 07:18:36 a...@amitm.com wrote: i tried four times under different conditions and NADA the same result over and over again Please try again - uninstall and get the new exe from the website. There is a reasonable chance that recent versions of the installer have fixed this bug. Sorry it took so long to get back to you. Please let me/us know what happens. Thanks. UserVoice wrote: paladin_squ...@live.com wrote: Freenet Starter Error Freenet Starter was unable to control the Freenet System Service. Reason: Service did not respond to signal. If the problem keeps occurring, try reinstalling Freenet or report this error message to the developers. Installed the program three times, got this error during installation once and each time running the program. Running XP Pro SP3 on 1ghz 1gb RAM laptop, 54mpbs wireless internet. Feedback would be appreciated. On http://freenetproject.org/download.html Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 (.NET CLR 3.5.30729) powered by UserVoice ___ 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 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.83/2526 - Release Date: 11/25/09 19:43:00 -- Amit Mendelsohn - Creative IT -- 21 Impass moreau, 13013, Marseille, France 23 yishai st., Jerusalem 93544, Israel Tel: +33-6-42483552 Skype: amitm123 a...@amitm.com a...@cvide.com -- Cvideos production http://www.cvide.com Company site: http://www.amitm.com TV portal: http://www.videowebgate.com ___ 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 signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
Evan Daniel wrote: Persistent-temp is not part of the datastore, and is not expected to stay within the datastore size limit. It's used to hold data from partially completed downloads. In theory, it will only grow to be slightly larger than your total queue size. However, there appear to be some bugs that make it leak space slowly. If it grows beyond your total queue size rapidly, though, that's not something I've seen. I can live with some additional disk-space use for downloaded files in transit; if it cleans up after the downloads are complete. (I planned a few gigs for downloads I configured Freenet.) Yet, presistent-temp grew over the weeks to achieve 11 GB... with several wrapper-induced shutdowns of Freenet. (The db4o implementation for downloads can get pretty unresponsive at times.) But with 17GB datastore (15 GB configured) PLUS 11GB in persistent-temp Freenet eats the best part of a 30 GB partition... Reclaiming ~9GB in unused temp files would make quite a difference. ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
On Sun, Dec 27, 2009 at 10:34 AM, SmallSister development smallsis...@xs4all.nl wrote: Evan Daniel wrote: Persistent-temp is not part of the datastore, and is not expected to stay within the datastore size limit. It's used to hold data from partially completed downloads. In theory, it will only grow to be slightly larger than your total queue size. However, there appear to be some bugs that make it leak space slowly. If it grows beyond your total queue size rapidly, though, that's not something I've seen. I can live with some additional disk-space use for downloaded files in transit; if it cleans up after the downloads are complete. (I planned a few gigs for downloads I configured Freenet.) Yet, presistent-temp grew over the weeks to achieve 11 GB... with several wrapper-induced shutdowns of Freenet. (The db4o implementation for downloads can get pretty unresponsive at times.) But with 17GB datastore (15 GB configured) PLUS 11GB in persistent-temp Freenet eats the best part of a 30 GB partition... Reclaiming ~9GB in unused temp files would make quite a difference. The workaround for persistent-temp is to shut down the node, then delete node.db4o and persistent-temp-*/ and restart the node. Warning, this will remove all in-progress uploads/downloads, so let those complete first. Evan Daniel ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
Dennis Nezic wrote: On Thu, 24 Dec 2009 23:03:25 +0100, SmallSister development wrote: Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. Interesting. Come to think of it, I also run pretty low on free diskspace ... 99% disk usage (of over 1tb) not being uncommon ... although that should still leave several gigs free. But, it's also interesting that you didn't have to delete your node.db4o file to get rid of the Internal error. And the Internal error reappeared after Freenet filled up the partition again overnight. persistent-temp had grown to 11 GB, which is a significant chunk of a 30 GB partition. ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
On Fri, Dec 25, 2009 at 7:18 AM, SmallSister development smallsis...@xs4all.nl wrote: Dennis Nezic wrote: On Thu, 24 Dec 2009 23:03:25 +0100, SmallSister development wrote: Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. Interesting. Come to think of it, I also run pretty low on free diskspace ... 99% disk usage (of over 1tb) not being uncommon ... although that should still leave several gigs free. But, it's also interesting that you didn't have to delete your node.db4o file to get rid of the Internal error. And the Internal error reappeared after Freenet filled up the partition again overnight. persistent-temp had grown to 11 GB, which is a significant chunk of a 30 GB partition. Persistent-temp is not part of the datastore, and is not expected to stay within the datastore size limit. It's used to hold data from partially completed downloads. In theory, it will only grow to be slightly larger than your total queue size. However, there appear to be some bugs that make it leak space slowly. If it grows beyond your total queue size rapidly, though, that's not something I've seen. Evan Daniel ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. ___ 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
Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
On Thu, 24 Dec 2009 23:03:25 +0100, SmallSister development wrote: Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. Interesting. Come to think of it, I also run pretty low on free diskspace ... 99% disk usage (of over 1tb) not being uncommon ... although that should still leave several gigs free. But, it's also interesting that you didn't have to delete your node.db4o file to get rid of the Internal error. ___ 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
Re: [freenet-support] Bug: 'Freenet Download button is not func...'
On Thu, Dec 10, 2009 at 12:26 AM, UserVoice supp...@uservoice.com wrote: manojmast...@aol.com wrote: Freenet Download button is not functioning. I am being redirected next page, displaying some code error. On http://freenetproject.org/index.html Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 This should be fixed now. Please try again, and let us know if you experience any difficulties. Evan Daniel ___ 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
Re: [freenet-support] Bug: 'I can't download (0.7.5 for Windows).'
On Wed, Dec 9, 2009 at 7:52 AM, UserVoice supp...@uservoice.com wrote: davide.min...@gmail.com wrote: I can't download (0.7.5 for Windows). On http://freenetproject.org/ Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.33 Safari/532.0 This should be fixed now. If you have any further problems, let us know. Evan Daniel ___ 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
Re: [freenet-support] Bug: 'cannot get freenet to work on mac G5 ...'
UserVoice a écrit : frankay...@yahoo.co.uk wrote: cannot get freenet to work on mac G5 and safari 4. just does not want to open after installation what am I doing wrong? On http://freenetproject.org/whatis.html Using Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 powered by UserVoice ___ 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 Well, what version of freenet are you using ? I know the last ones are working fine on Intel Leopard, and I know that earlier versions (only 6 month ago) worked fine on PPC Tiger... ___ 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
Re: [freenet-support] Bug: 'Freenet Starter ErrorFreenet Starte...'
i tried four times under different conditions and NADA the same result over and over again UserVoice wrote: paladin_squ...@live.com wrote: Freenet Starter Error Freenet Starter was unable to control the Freenet System Service. Reason: Service did not respond to signal. If the problem keeps occurring, try reinstalling Freenet or report this error message to the developers. Installed the program three times, got this error during installation once and each time running the program. Running XP Pro SP3 on 1ghz 1gb RAM laptop, 54mpbs wireless internet. Feedback would be appreciated. Onhttp://freenetproject.org/download.html Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 (.NET CLR 3.5.30729) powered by UserVoice ___ 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 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.83/2526 - Release Date: 11/25/09 19:43:00 -- Amit Mendelsohn - Creative IT -- 21 Impass moreau, 13013, Marseille, France 23 yishai st., Jerusalem 93544, Israel Tel: +33-6-42483552 Skype: amitm123 a...@amitm.com a...@cvide.com -- Cvideos production http://www.cvide.com Company site: http://www.amitm.com TV portal: http://www.videowebgate.com ___ 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
Re: [freenet-support] Bug in HTTP socket handler in 1208?
On Sat, 30 May 2009 22:14:32 +0100, Matthew Toseland wrote: On Sunday 10 May 2009 15:51:39 Dennis Nezic wrote: On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote: I have seen a couple times my node stall due to exceeding the thread limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread usage). (My node's thread limit is 300). I believe this is caused by my browser (dillo) making too many connections to fproxy. But, nevertheless, shouldn't these threads / sockets die after a few minutes? They were all still alive after more than 10mins of stalling my node, after which I had to restart to get things flowing again. The problem still exists in 1209. (If my Dillo browser opens a page with hundreds of thumbnails and no limit to the number of connections made to the server/fproxy (It probably relies on http server response codes?), the number of HTTP socket handlers will sky-rocket above the limit, and stay there. Again, how long are these threads supposed to last for and why are they even allowed to exist (can't fproxy throttle the number of incoming connections?). There still do remain a couple Pooled threads awaiting work, but the node effectively shuts down -- cpu drops to almost nothing, and all traffic seems to stop. Does it happen in 1212/1213? Are you sure that all these connections have fetched data and are no longer active? A thread dump of the node in this condition would be helpful. Still happens with the latest builds. Loading a page with lots of images, like: u...@qd-hk0vhyg7yvk2bqsjmcud5qsf0tdkgnnf6lnwuh0g,xTFOV9ddCQQk6vQ6G~jfL6IzRUgmfMcZJ6nuySu~NUc,AQACAAE/activelink-index/106/ ... in a browser that apparently doesn't limit the number of connections that it makes to fproxy, causes the number of threads to skyrocket well above the thread limit, stalling all traffic with the node -- although the fproxy interface still works. I did a thread dump, which includes all the hundreds of HTTP socket handler threads, which are all in a WAITING state. All locked. Here's the full thread dump: http://dennisn.dyndns.org/guest/uploads/tmp/stalled-httpsocket-dump.log.bz2 Either way, how is the thread limit even able to be exceeded? And why aren't these threads dying? ___ 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
Re: [freenet-support] Bug in HTTP socket handler in 1208?
On Sunday 10 May 2009 15:51:39 Dennis Nezic wrote: On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote: I have seen a couple times my node stall due to exceeding the thread limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread usage). (My node's thread limit is 300). I believe this is caused by my browser (dillo) making too many connections to fproxy. But, nevertheless, shouldn't these threads / sockets die after a few minutes? They were all still alive after more than 10mins of stalling my node, after which I had to restart to get things flowing again. The problem still exists in 1209. (If my Dillo browser opens a page with hundreds of thumbnails and no limit to the number of connections made to the server/fproxy (It probably relies on http server response codes?), the number of HTTP socket handlers will sky-rocket above the limit, and stay there. Again, how long are these threads supposed to last for and why are they even allowed to exist (can't fproxy throttle the number of incoming connections?). There still do remain a couple Pooled threads awaiting work, but the node effectively shuts down -- cpu drops to almost nothing, and all traffic seems to stop. Does it happen in 1212/1213? Are you sure that all these connections have fetched data and are no longer active? A thread dump of the node in this condition would be helpful. signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets
On Sunday 17 May 2009 21:30:28 Juiceman wrote: On Fri, May 15, 2009 at 2:38 PM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Saturday 02 May 2009 11:09:37 theymos wrote: Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209 rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few hours ago. I updated using update.cmd because the built-in update wasn't working. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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 to the support mailing list supp...@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: I might just have fixed this in git... Nope, still there. Running #1210 build01210 (this is after -pre4 I guess?) I only get them once a day or so. Wait until 1210 is mandatory. signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets
On Fri, May 15, 2009 at 2:38 PM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Saturday 02 May 2009 11:09:37 theymos wrote: Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209 rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few hours ago. I updated using update.cmd because the built-in update wasn't working. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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 to the support mailing list supp...@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: I might just have fixed this in git... Nope, still there. Running #1210 build01210 (this is after -pre4 I guess?) I only get them once a day or so. ___ 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
Re: [freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets
On Saturday 02 May 2009 11:09:37 theymos wrote: Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209 rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few hours ago. I updated using update.cmd because the built-in update wasn't working. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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 to the support mailing list supp...@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: I might just have fixed this in git... signature.asc Description: This is a digitally signed message part. ___ 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
Re: [freenet-support] Bug in HTTP socket handler in 1208?
On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote: I have seen a couple times my node stall due to exceeding the thread limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread usage). (My node's thread limit is 300). I believe this is caused by my browser (dillo) making too many connections to fproxy. But, nevertheless, shouldn't these threads / sockets die after a few minutes? They were all still alive after more than 10mins of stalling my node, after which I had to restart to get things flowing again. The problem still exists in 1209. (If my Dillo browser opens a page with hundreds of thumbnails and no limit to the number of connections made to the server/fproxy (It probably relies on http server response codes?), the number of HTTP socket handlers will sky-rocket above the limit, and stay there. Again, how long are these threads supposed to last for and why are they even allowed to exist (can't fproxy throttle the number of incoming connections?). There still do remain a couple Pooled threads awaiting work, but the node effectively shuts down -- cpu drops to almost nothing, and all traffic seems to stop. ___ 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
Re: [freenet-support] Bug?
1192 will be mandatory tomorrow. Please wait until tomorrow, restart your node, and report whether it still happens. Thanks. On Wednesday 10 December 2008 20:49, Ancoron Luciferis wrote: Mel Charters wrote: Content-Type: multipart/signed; boundary=nextPart1983121.TrFsbus4oi; protocol=application/pgp-signature; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit On Tuesday 09 December 2008 10:43, Volodya wrote: Matthew Toseland wrote: On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... I just got the same thing. I repeat, the bug is still there (although not as dominant as before). Just ? Did you or did you not restart your node after midnight GMT on Tuesday? The bug is still there and I restarted at 12:15 GMT Tuesday morning. Details: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 87.96.165.16:12938 * 211.31.2.118:32782 * 83.99.52.101:2587 * 88.175.188.50:10394 * 211.31.2.118:32768 * 92.132.225.163:38644 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 This one is still seen in build 1192, although it seems to appear less often (had sometimes around 12 forcibly disconnected with build 1190). Freenet 0.7 Build #1192 r24161M Freenet-ext Build #26 r23771 Stacktrace for one of the latest: at freenet.node.PeerNode.disconnected(PeerNode.java:1139) at freenet.node.PeerNode.onRemove(PeerNode.java:3554) at freenet.node.OpennetPeerNode.onRemove(OpennetPeerNode.java:66) at freenet.node.PeerManager.removePeer(PeerManager.java:338) at freenet.node.PeerManager.disconnect(PeerManager.java:523) at freenet.node.OpennetManager.wantPeer(OpennetManager.java:377) at freenet.node.OpennetManager.addNewOpennetNode(OpennetManager.java:249) at freenet.node.Node.addNewOpennetNode(Node.java:3662) at freenet.node.RequestSender.finishOpennet(RequestSender.java:1135) at freenet.node.RequestSender.finish(RequestSender.java:1082) at freenet.node.RequestSender.realRun(RequestSender.java:785) at freenet.node.RequestSender.run(RequestSender.java:169) at freenet.support.PooledExecutor$MyThread.run(PooledExecutor.java:190) Greetz, AncoL ___ 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] pgp9EH4dztaU0.pgp Description: PGP signature ___ 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] Bug?
Mel Charters wrote: Content-Type: multipart/signed; boundary=nextPart1983121.TrFsbus4oi; protocol=application/pgp-signature; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit On Tuesday 09 December 2008 10:43, Volodya wrote: Matthew Toseland wrote: On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... I just got the same thing. I repeat, the bug is still there (although not as dominant as before). Just ? Did you or did you not restart your node after midnight GMT on Tuesday? The bug is still there and I restarted at 12:15 GMT Tuesday morning. Details: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 87.96.165.16:12938 * 211.31.2.118:32782 * 83.99.52.101:2587 * 88.175.188.50:10394 * 211.31.2.118:32768 * 92.132.225.163:38644 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 This one is still seen in build 1192, although it seems to appear less often (had sometimes around 12 forcibly disconnected with build 1190). Freenet 0.7 Build #1192 r24161M Freenet-ext Build #26 r23771 Stacktrace for one of the latest: at freenet.node.PeerNode.disconnected(PeerNode.java:1139) at freenet.node.PeerNode.onRemove(PeerNode.java:3554) at freenet.node.OpennetPeerNode.onRemove(OpennetPeerNode.java:66) at freenet.node.PeerManager.removePeer(PeerManager.java:338) at freenet.node.PeerManager.disconnect(PeerManager.java:523) at freenet.node.OpennetManager.wantPeer(OpennetManager.java:377) at freenet.node.OpennetManager.addNewOpennetNode(OpennetManager.java:249) at freenet.node.Node.addNewOpennetNode(Node.java:3662) at freenet.node.RequestSender.finishOpennet(RequestSender.java:1135) at freenet.node.RequestSender.finish(RequestSender.java:1082) at freenet.node.RequestSender.realRun(RequestSender.java:785) at freenet.node.RequestSender.run(RequestSender.java:169) at freenet.support.PooledExecutor$MyThread.run(PooledExecutor.java:190) Greetz, AncoL ___ 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] Bug?
Matthew Toseland wrote: On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... I just got the same thing. I repeat, the bug is still there (although not as dominant as before). - Volodya -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut None of us are free until all of us are free.~ Mihail Bakunin ___ 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] Bug?
On Tuesday 09 December 2008 10:43, Volodya wrote: Matthew Toseland wrote: On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... I just got the same thing. I repeat, the bug is still there (although not as dominant as before). Just ? Did you or did you not restart your node after midnight GMT on Tuesday? pgpUFFWqb1Jj8.pgp Description: PGP signature ___ 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] Bug?
Content-Type: multipart/signed; boundary=nextPart1983121.TrFsbus4oi; protocol=application/pgp-signature; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit On Tuesday 09 December 2008 10:43, Volodya wrote: Matthew Toseland wrote: On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... I just got the same thing. I repeat, the bug is still there (although not as dominant as before). Just ? Did you or did you not restart your node after midnight GMT on Tuesday? The bug is still there and I restarted at 12:15 GMT Tuesday morning. Details: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 87.96.165.16:12938 * 211.31.2.118:32782 * 83.99.52.101:2587 * 88.175.188.50:10394 * 211.31.2.118:32768 * 92.132.225.163:38644 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 -- Mel Charters ___ 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] Bug?
On Sunday 07 December 2008 14:57, Volodya wrote: Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? Unfortunately that's now Tuesday... pgpqaUztN3Vsf.pgp Description: PGP signature ___ 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] Bug?
Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut None of us are free until all of us are free.~ Mihail Bakunin ___ 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] Bug?
Mel Charters wrote: Probably a bug: please report: 6 peers forcibly disconnected due to not acknowledging packets. 6 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 to the support mailing list [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: * 80.67.126.33:48685 * 91.114.90.176:50370 * 70.252.130.137:62819 * 74.192.11.111:1030 * 68.164.92.215:5510 * 88.115.66.96:8421 Freenet 0.7 Build #1191 r24115M Freenet-ext Build #26 r23771 May be from #1190. Build #1191 appeared within the last 10 hours. -- Mel Charters Have you restarted your node since Saturday at midnight? I restarted Sunday about 4 am GMT. At that time I received #1190 update. Some time later auto update to #1191 -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut None of us are free until all of us are free.~ Mihail Bakunin ___ 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] -- Mel Charters ___ 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] Bug report
On Thursday 27 November 2008 17:42, [EMAIL PROTECTED] wrote: 4 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: * 129.16.197.194:27790 * 62.225.45.102:6352 * 98.227.214.171:53740 * 84.30.40.171:26687 Freenet 0.7 Build #1184 r23907 Freenet-ext Build #26 r23771 Thanks for your bug report. Hopefully we will be able to fix this soon, however there have been a number of more urgent problems lately. We make the node report it because we need to hear about it if it happens ... we had thought it was fixed. Please wait until we release a build which we claim has fixed the problem, and then report the bug if it continues to happen. Thanks. Hi, If you wish to receive bug reports it might be a good idea to enable the support address to receive messages. My last one is being held up for a moderator to view. I shall not bother in future if I don't think helpful reports are being attended to. Given the amount of spam we get, which would be rebroadcast to everyone trying to help other users or trying to solve a problem of their own, it would be utterly idiotic to not moderate non-subscriber spam: it would simply result in everyone leaving the list. Well wisher pgpD34KYFnKwv.pgp Description: PGP signature ___ 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] [Bug report?] NullPointerException in PacketSender
On Monday 27 October 2008 23.49.18 Dan Stevens wrote: Freenet 0.7 Build #1165 r22843M Freenet-ext Build #22 r22506 After running seemingly just fine for several weeks, I suddenly ran out of disk space. The problem turned out to be my freenet log, which was expanding at about a megabyte per second, full of message like this: Oct 27, 2008 22:00:01:275 (freenet.node.PacketSender, PacketSender thread for 4282, ERROR): Caught in PacketSender: java.lang.NullPointerException java.lang.NullPointerException at freenet.support.transport.ip.IPUtil.isValidAddress(IPUtil.java:13) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3915) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3909) at freenet.node.PacketSender.realRun(PacketSender.java:230) at freenet.node.PacketSender.run(PacketSender.java:168) at java.lang.Thread.run(Unknown Source) at freenet.support.io.NativeThread.run(NativeThread.java:99) I tried to re-start the node, but I think hitting the restart button didn't actually work. Shutting down didn't work, either. I had to use the Windows service manager and shut it down from there. Other than that, all seemed well. The connections to my peers were 'connected' as usual. I started the node up again (from Windows service manager), it seemed fine for a while, but my freenet-latest.log is now, once again, expanding at ~1 MB/s :P I can browse freenet OK, though. ___ 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] Try to update to 1166, which is released just 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] Bug report : update scripts are empty
On Tue, May 02, 2006 at 11:33:57AM +0200, Julien Cornuwel wrote: Hi, I don't know if it's a known bug but this morning, when I tried to update my 0.7 node, I found that both update.sh and update2.sh were empty ! Could someone put them on downloads.freenetproject.org so I can retreive them safely ? http://emu.freenetproject.org/cgi-bin/viewcvs.cgi/trunk/apps/installer/installclasspath/linux/?rev=8599 Regards -- 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 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] Bug found in 5077
In einer eMail vom Di, 27. Apr. 2004 15:44 MEZ schreibt Toad [EMAIL PROTECTED]: On Sun, Apr 25, 2004 at 01:57:41PM +0200, Rama Jagerman wrote: Current upstream bandwidth usage 164677 bytes/second (164.7%) [...] average out to no more than the target. HOWEVER, there is a hard limit of 140% of the stated limit. The reason we have two limits is that there are two limiting mechanisms. If you get this sort of transfer [...] If I did not miss something, then that output transfer speed is over the hard limit and that seems a little bit wrong to me. ___ 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] Bug found in 5077
On Sun, Apr 25, 2004 at 01:57:41PM +0200, Rama Jagerman wrote: Hi, First of all, congratulations with the new stable version of Freenet. At this moment I am almost sure that there is a bug in Freenet, please see the next line, that I copied from Performance -- General Information: Current upstream bandwidth usage 164677 bytes/second (164.7%) Note that the upstream bandwidth usage is indeed this amount of b/s, and that it should be limited to 100.000 bytes/second. It's not a hard limit. It's a target. Over a period of hours, it should average out to no more than the target. HOWEVER, there is a hard limit of 140% of the stated limit. The reason we have two limits is that there are two limiting mechanisms. If you get this sort of transfer rate consistently over hours (check your outputBytes stats), that is a bug. If you only get spikes that are a little over the absolute limit, that's fine, just reduce outputBytes a bit. I am already donating a lot of bandwith I think, but I really can't donate more than 100.000 bytes/second because of upload limits. Hopefully there can be a quick fix, so that Freenet respects the limits. Thanks and good luck! Rama Jagerman p.s. If you need more information, please let me know. -- 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]
Re: [freenet-support] Bug Report - win32 - freenet.exe - logFile=*path*not handled
Oops, that may well be a very old bug. That shouldn't be too hard to fix, I'll crack one out tonight. I have changed the logFile option in the freenet.ini file to an other path. But when I click on View Logfile ... in the context menu of the blue freenet symbol, freenet.exe still shows me the old unused freenet.log in the freenet directory. Rudi ___ 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]
Re: [freenet-support] Bug Report - win32 - freenet.exe - logFile=*path*not handled
(fwiw it sounds like it isn't querying the ini file each time you click View Logfile - I think it's probably just querying once at startup) Oops, that may well be a very old bug. That shouldn't be too hard to fix, I'll crack one out tonight. I have changed the logFile option in the freenet.ini file to an other path. But when I click on View Logfile ... in the context menu of the blue freenet symbol, freenet.exe still shows me the old unused freenet.log in the freenet directory. Rudi ___ 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] ___ 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] Bug Report - win32 - freenet.exe - logFile=*path*not handled
Ur, or maybe I hardcoded freenet.log in the viewer and never fixed it... my bad. (fwiw it sounds like it isn't querying the ini file each time you click View Logfile - I think it's probably just querying once at startup) Oops, that may well be a very old bug. That shouldn't be too hard to fix, I'll crack one out tonight. I have changed the logFile option in the freenet.ini file to an other path. But when I click on View Logfile ... in the context menu of the blue freenet symbol, freenet.exe still shows me the old unused freenet.log in the freenet directory. Rudi ___ 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] ___ 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]
Re: [freenet-support] bug in 6430
On Thu, Jan 08, 2004 at 12:10:36PM -0500, Edward J. Huff wrote: On Thu, 2004-01-08 at 11:16, [EMAIL PROTECTED] wrote: I just do not know, where to report this, (probably it was noticed already anyway...), but the bandwith limiting in unstable version 6430 seems to be broken: Current upstream bandwidth usage 14576 bytes/second (145,8%) And the node is not QueryRejecting or something like that and the load is on 82% right now... Hope it is fixed soon, since this bug blocks your internet connection, by using the whole available upload bandwith :/ Change outputBandwidthLimit to about 1/4 of what you had before. Should help a little. I have the problem too. Presently the low level bandwidth limiting is off, and Freenet seems to be working better as a result. The high level bandwidth limiting is not very accurate, because it relies on rejecting queries to cause bandwidth usage to drop. Yes, but is the high level limiting working for what it is supposed to do? -- Ed Huff ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support -- 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
Re: [freenet-support] Bug or Feature?
On Fri, 2004-01-02 at 12:14, Rudolf Krist wrote: Hello, after I have upgraded my node to the Build 6415, the routing table only contained nodes with the Build Nr. = 6415. Is that a new feature? Or was it not intended? Yes, users of the unstable build are expected to upgrade daily. -- Ed Huff signature.asc Description: This is a digitally signed message part ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support
Re: [freenet-support] bug? Can't set storeSize in human-readable format
On Thu, Oct 31, 2002 at 07:16:02AM -0600, GeckoX wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tried setting my storeSize in 0.5.0.3 to 2G and fred wouldn't start. Here's what I tried to do in freenet.conf: storeSize=2G This is only supported in the development/unstable branch of fred. Use a plain number in bytes. Here's the log: Oct 31, 2002 7:10:43 AM (freenet.support.io.Bandwidth, main): new Bandwidth(10,0,BOTH) Oct 31, 2002 7:10:43 AM (freenet.node.Main, main): Unexpected Exception: java.lang.ClassCastException java.lang.ClassCastException at freenet.config.Params.getLong(Params.java:258) at freenet.node.Node.init(Node.java:922) at freenet.node.Main.main(Main.java:222) When I reset freenet.conf to this: storeSize=268435456 Fred started just fine and dandy. Apparently Fred doesn't understand gigabytes yet? Thanks. :GeckoX -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9wS0PSMrcfZpjDKERAjvmAJwJNLT2ho+YL9fL9ku7xDwosjekzQCeO4Tg 4yGoQl+x+BnjZVBxxs2ZZyE= =6LAf -END PGP SIGNATURE- ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support -- Matthew Toseland [EMAIL PROTECTED] [EMAIL PROTECTED] Freenet/Coldstore open source hacker. Employed full time by Freenet Project Inc. from 11/9/02 to 11/11/02. http://freenetproject.org/ msg01859/pgp0.pgp Description: PGP signature
Re: [freenet-support] Bug...
Visit the sun site _again_ ... this time following all the links that point to the Java 2 Runtime Environment for Windows. You will end up here: http://java.sun.com/j2se/1.3/jre/download-windows.html Download it. - Original Message - From: Marcus Berns To: [EMAIL PROTECTED] Sent: Thursday, June 07, 2001 1:15 PM Subject: [freenet-support] Bug... Hi, there, I tried to install Freenet on an Win 2000 Notebook. I get the error, that there is no java environment on the computer and the address of Sun. I visited the Sun-Site, but there is nothing for download. What can I do? Regards, Marcus ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
