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
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
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.
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
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
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
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.
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.
>
>
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 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 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
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
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 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
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/
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
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
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
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
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
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
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
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
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 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 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
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
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
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
___
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
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
___
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
(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
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
Sometimes I get this error message on stable build 5068 (and the builds
before). I think client programs fetching keys via fcp stall , untill the
socket timeouts (If set). I use linux and sun jvm 1.4.1_03-b02.
Caught java.lang.IllegalStateException: Not sending a trailer running
maintenance
Hello,
I'm using build 5065 on GNU/Linux on i386, with j2sdk1.4.0_02.
I got the following messages. Generally, whenever I leave my
freenet node running a few hours, it ends up running out of memory
(I have 256Mo And 500Mo swap), using a lot of CPU (I have a P3 700 and a
512/128kbps DSL
Hi:
Using build 6441, and fred said:
Waited more than 200ms to dequeue, 15 in queue, 6701 millis since enqueued
last item, 291589 maximum waits so far - could indicate serious JVM bug.
Please report to [EMAIL PROTECTED] along with JVM and OS/kernel.
Waited more than 200ms to dequeue, 6 in
Hi:
Using build 6440, just downloaded n' fred said:
Waited more than 200ms to dequeue, 6 in queue, 4401 millis since enqueued last
item, 2057 maximum waits so far - could indicate serious JVM bug. Please
report to [EMAIL PROTECTED] along with JVM and OS/kernel.
java version 1.4.2
Java(TM) 2
38 matches
Mail list logo
