[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 > >>> 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: > >>> > >>> * 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? -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081209/66161867/attachment.pgp>
[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 >>> 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: >>> >>> * 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
[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 >> >>> 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: >> >>> >> >>> * 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 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: * 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
[freenet-support] Some thoughts and suggestions
How do you know, there are no Tibetans or Iranians using the freenet - who told you that? There are other ways, than what you suggest, to use freenet! And freenet is under steady development. But good to get some suggestions, that's what makes the world "rock". *smile* On Tue, 2008-12-09 at 00:32 +0100, Repu Blica wrote: > Here follows some random thoughts and suggestions from a non technical > perspective. > > >
[freenet-support] Java 1.4 no longer supported
Try running "update-java-alternatives" on a console/terminal ... The most likely explanation is that you have GIJ/GCJ installed as well as the Sun JVM, and your distribution is defaulting to it for some reason. On Sunday 07 December 2008 03:16, jdaviestx at tx.rr.com wrote: > I was just looking at the "alerts" section of my status page, and I saw this: > > Java 1.4 no longer supported > You are running Freenet on a 1.4 version of Java. Please upgrade to at least java 1.5. Auto-update has been temporarily disabled as future builds may not load at all. > > The problem is... I don't have JDK 1.4 installed. The only version of java I have installed is jdk1.6.0_03: > > debian:logs$ which java > /usr/java/jdk1.6.0_03/bin/java > debian:logs$ java -version > java version "1.6.0_03" > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode) > > I'm trying to figure out where Freenet is looking to find the JVM, but it's not clear from the configuration page. I can see that it kicked off with a "wrapper-linux-x86-32" binary, but that's not a script, so I can't go into it to see where it's looking for its JVM: > > debian:Freenet$ ps -few | grep Free > jdavies 3097 1 0 20:42 ? 00:00:00 /home/jdavies/Freenet/./bin/wrapper-linux-x86-32 /home/jdavies/Freenet/./wrapper.conf wrapper.syslog.ident=Freenet wrapper.pidfile=/home/jdavies/Freenet/./Freenet.pid wrapper.daemonize=TRUE wrapper.anchorfile=/home/jdavies/Freenet/./Freenet.anchor wrapper.ignore_signals=TRUE wrapper.lockfile=/home/jdavies/Freenet/Freenet > > This is preventing Freenet from autoupdating: > > Build too old > This node's software is older than the oldest version (Build #1188) allowed by the newest peers we try to connect to. Please update your node as soon as possible as you will not be able to connect to peers labeled "TOO NEW" until you do. (Freenet may leave your node in the dust of the past if you don't upgrade.) > > So Freenet isn't working for me until I get this resolved. Can anybody help me figure out where Freenet is finding this JDK 1.4? > ___ > 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 > > -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081209/7f68a30d/attachment.pgp>
[freenet-support] Some thoughts and suggestions
ex, which did not have adequate categories, did not have descriptions at all in many cases, and had sites in wrong categories. In particlar it had a child porn site in the Indexes category, without any form of labelling or warning apart from the title which is only understandable by those who know the jargon. We would not have removed it for linking to child porn, any more than we would an index for linking to hate speech or copyrighted materials: We removed it because it was not usable for a new user trying to locate content on some topic, because it was misleading. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081209/b2d9e531/attachment.pgp>
[freenet-support] Some thoughts and suggestions
-- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081209/1a5f84f3/attachment.html>
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]
[freenet-support] Freenet 0.7 build 1190, 1191 and 1192
Sorry for the belated changelogs ... Please upgrade! 1190: - 1189 broke seednodes. Fixed in 1190. 1191: - Fix startup failures due to problems with updater temp files. Delete the old temp files. 1192: - Fix a major unfairness bug in the packet sending scheduler code. This may have caused some nodes to be sent far more traffic than others, likely causing various nasty connectivity bugs possibly including the forced disconnect due to not acking packets bug. 1192 is mandatory on Friday. After that it will be interesting to know whether the forced disconnect due to not acknowledging packets bug is still around - it probably will be, but at least we're down one possible cause... :| If you find any bugs, please let us know, preferably via the bug tracker: https://bugs.freenetproject.org/ Thanks for using Freenet, and apologies for the problems we've had lately. Note that we have additional changes in trunk which have not been released yet; all the above are single-bugfix builds. We always need more trunk testers (update.sh/update.cmd testing), but you need to keep up to date; joining the IRC channel is helpful but not essential. pgpmIsnoHacGO.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]
