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

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

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

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

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

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

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:

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

[freenet-support] Bug Tracker

Dear Davide, As you may know, we currently have a backlog of orders. I am told the most recent batch has already been filled. The next batch will be ready in March. However, please note that there is an average lead time of about 2 months from the date of order. If you have any other

[freenet-support] Bug: 'Running * Freenet 0.7.5 Build #12...'

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

[freenet-support] Bug: 'I get an error message as below.F...'

roy.fitzpatr...@talktalk.net wrote: I get an error message as below. Freenet starter was unable to control the freenet system service. Reason:Service did not respond to signal. On http://freenetproject.org/download.html [http://freenetproject.org/download.html] Using Mozilla/4.0

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

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

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

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

[freenet-support] BUG: Freenet does not respect size limit for datastore

I found that Freenet (Build #1239) happily expands the datastore over the configured size limit. (Disk space is the limit...) This leads to very interesting behaviour when the file system gets full and I would like your help to solve the following two issues: 1) Error message on all pages: The

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

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,

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

[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets.

I'm still getting these messages from time to time: » 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. If this happens a lot, please add your

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

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

[freenet-support] Bug: 'I can't download (0.7.5 for Windows).'

davide.min...@gmail.com wrote: I can't download (0.7.5 for Windows). On http://freenetproject.org/ [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

[freenet-support] Bug: 'Freenet Download button is not func...'

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 [http://freenetproject.org/index.html] Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824

[freenet-support] Bug: 'A IOException occred'

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 ___ Support mailing list

[freenet-support] Bug: 'cannot get freenet to work on mac G5 ...'

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 [http://freenetproject.org/whatis.html] Using Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en)

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)

[freenet-support] Bug: 'This is NOT a bug, but a badly MISSIN...'

vel...@gmail.com wrote: This is NOT a bug, but a badly MISSING upfront statement on the freenetproject.org website. Upon downloading the 0.7.5 OSX freenet file from checksums.freenet.org, I was presented with the Installer dialog, which stated, among other things: Self-signed Certificate;

[freenet-support] Bug: 'Give us an update.. come one no updat...'

dere...@hotmail.com wrote: Give us an update.. come one no update since August. On http://uservoice.com/a/EDt1x [http://uservoice.com/a/EDt1x] Using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)

[freenet-support] Bug: 'There is a missing line in the http:/...'

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

[freenet-support] Bug: 'Freenet Starter ErrorFreenet Starte...'

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

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

[freenet-support] Bug report

Hello, i've had a problem with Freenet, the message is the following: 1 des noeuds auxquels vous êtes connectés ont de sérieux problèmes (données non reconnues même après 10 minutes). Ceci est probablement dû a un bug dans le code. Veuillez svp nous faire un rapport en utilisant le

[freenet-support] bug

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. If this happens a lot, please add your information to the report on the bug tracker at https://bugs.freenetproject.org/view.php?id=2692 or send it to the support

[freenet-support] Bug report

Well, it asked me to send this to you guys so here it is, :) 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.

[freenet-support] [BUG] Report

Voici le message d'erreur (Freenet 0.7.5, téléchargé hier) : « Probablement un bug : veuillez faire le rapport suivant : 1 noeuds ont été déconnecté de force car les données ne sont pas reconnues. 1 des noeuds auxquels vous êtes connectés ont de sérieux problèmes (données non reconnues même

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

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).

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

[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets

On Fri, May 15, 2009 at 2:38 PM, Matthew Toseland 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

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.

[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. > >

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

[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)

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

[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets

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

[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets

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

[freenet-support] Bug in HTTP socket handler in 1208?

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

[freenet-support] Bug in HTTP socket handler in 1208?

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

[freenet-support] bug submission

(translated): 1 peer doesn't report any received packet in 10 minutes , possibly due to an application bug. Please report etc... affected peers are: 82.65.163.185:46187 freenet version: Freenet 0.7 Build 1206 r26118 Freenet-ext Build #26 r23771 hope this helps. feel free to ask for

[freenet-support] bug submission

(translated): 1 peer doesn't report any received packet in 10 minutes , possibly due to an application bug. Please report etc... affected peers are: 82.65.163.185:46187 freenet version: Freenet 0.7 Build 1206 r26118 Freenet-ext Build #26 r23771 hope this helps. feel free to ask for more

[freenet-support] BUG ?

Probablement un bug : veuillez faire le rapport suivant : 3 noeuds ont ?t? d?connect? de force car les donn?es ne sont pas reconnues. 3 des noeuds auxquels vous ?tes connect?s ont de s?rieux probl?mes (donn?es non reconnues m?me apr?s 10 minutes). Ceci est probablement d? a un bug dans le code.

[freenet-support] Bug?

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/http://127.0.0.1:/?_CHECKED_HTTP_=https://bugs.freenetproject.org/or to the

[freenet-support] BUG ?

Probablement un bug : veuillez faire le rapport suivant : 3 noeuds ont été déconnecté de force car les données ne sont pas reconnues. 3 des noeuds auxquels vous êtes connectés ont de sérieux problèmes (données non reconnues même après 10 minutes). Ceci est probablement dû a un bug dans le code.

[freenet-support] Bug?

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 to the

[freenet-support] bug

1 des noeuds auxquels vous êtes connectés ont de sérieux problèmes (données non reconnues même après 10 minutes). Ceci est probablement dû a un bug dans le code. Veuillez svp nous faire un rapport en utilisant le gestionnaire de bug à l'adresse suivante : https://bugs.freenetproject.org/ ou sur

[freenet-support] Bug report, as requested

I still get this error message occasionally (with different peers). I was wondering if this message could be generated because the peer node has been put to sleep, perhaps inadvertently? Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your

[freenet-support] Bug report, as requested

I still get this error message occasionally (with different peers). I was wondering if this message could be generated because the peer node has been put to sleep, perhaps inadvertently? Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your

[freenet-support] bug

1 des noeuds auxquels vous ?tes connect?s ont de s?rieux probl?mes (donn?es non reconnues m?me apr?s 10 minutes). Ceci est probablement d? a un bug dans le code. Veuillez svp nous faire un rapport en utilisant le gestionnaire de bug ? l'adresse suivante : https://bugs.freenetproject.org/ ou sur

[freenet-support] Bug report - 1 peers forcibly disconnected due to not acknowledging packets

Freenet told me to report this to you. I'm on Freenet 0.7 Build #1204 r25209, Freenet-ext Build #26 r23771. I run only on the Opennet; I have no Darknet peers. I can answer any questions you have. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1

[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"; > >>

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;

[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: >>> >

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

[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

[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

[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,

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

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

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

[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

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

[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

[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

[freenet-support] Bug?

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

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

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

[freenet-support] Bug report

On Thursday 27 November 2008 17:42, toadsfriend at hushmail.com 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/

[freenet-support] Bug report

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 support at freenetproject.org. Please include this message and what

[freenet-support] Bug report

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

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

[freenet-support] Bug report

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 at [EMAIL PROTECTED] Please include this message and what version of the

[freenet-support] Bug report

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 at support at freenetproject.org. Please include this message and what

[freenet-support] bug

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

[freenet-support] Bug Report

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

[freenet-support] bug report: 2 peers forcibly disconnected due to not acknowledging packets

Version Information & Node Control Freenet 0.7 Build #1178 r23592M Freenet-ext Build #24 r23199 Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is

[freenet-support] bug?

I send this message as a probable bug seen in the messages page. Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the

[freenet-support] bug report: 2 peers forcibly disconnected due to not acknowledging packets

Version Information Node Control Freenet 0.7 Build #1178 r23592M Freenet-ext Build #24 r23199 Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is

[freenet-support] bug?

I send this message as a probable bug seen in the messages page. Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets. 2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the

[freenet-support] bug

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

[freenet-support] Bug Report

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

[freenet-support] [Bug report?] NullPointerException in PacketSender

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

[freenet-support] [Bug report?] NullPointerException in PacketSender

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

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

[freenet-support] bug in r9081 (.7)

I just upgraded and started it again and got the same problem. Did my datastore get corrupted? Here's the output from the latest. Created log files INFO: Native CPUID library 'freenet/support/CPUInformation/libjcpuid-x86-linux.so' loaded from resource INFO: Optimized native BigInteger library

[freenet-support] bug in r9081 (.7)

I seem to have found a problem when I upgraded to r9081. I cannot start Freenet 0.7 now. Maybe this is related to the fact that I do not have X on this Linux machine (since it's headless), so I had to do a manual install around build 643 or so. Here is what I get when I start freenet:

[freenet-support] Bug report : update scripts are empty

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 ? Regards

[freenet-support] Bug report : update scripts are empty

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 ? Regards ___

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

[freenet-support] Bug

Hello! I believe there may be a problem. I keep getting the following error message:java.io.FileNotFoundException: C:\DOCUME~1\Donald\LOCALS~1\Temp\freenet\tbf_7b3a67 (The system cannot find the path specified) java.io.FileNotFoundException:

  1   2   >