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 supp...@freenetproject.org.
Please include this message and what version
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 in
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 gestionn
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. Ple
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 aprè
On Sunday 17 May 2009 21:30:28 Juiceman wrote:
> 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 jus
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 updat
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 updat
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.
>
> Probabl
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.
>
> Probabl
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 pee
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 pee
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 o
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 o
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/ or
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 versio
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
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
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 node
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 versio
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 yo
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 pro
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 pro
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 o
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
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:27
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
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:27
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
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
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
___
S
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 ha
(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 fr
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
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
__
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 que
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 connexi
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 queu
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
hi, i got this message while trying to request the YoYo frontpage
([EMAIL PROTECTED]/YoYo//) with fcpget from
FCPtools v0.4.7:
Waited more than 200ms to dequeue, 9 in queue, 2599
millis since enqueued last item, 19876 maximum waits so far - could
indicate serious JVM bug. Please report to [EMAIL
Hi, freenet sw asked me to report this, I hope I do the right thing...
[EMAIL PROTECTED] freenet]$ sh start-freenet.sh
Starting Freenet now: Done
[EMAIL PROTECTED] freenet]$ requestIntervalDefault: 1000
requestIntervalQRFactor: 1.05
requestIntervalAcceptedFactor: 0.9523809523809523
---Unexpected E
hi,
freenet lauches but won't open any window, neither the config nore the http://localhost:8081/ one.
i run
Freenet 0.3.9.1
on Win Me
with JRE v 1.3.0_02
Freenet Version: 0.3.9.1
OS: Windows 98
Java Runtime Environment: JRE 1.3
Using latest version of Internet Explorer (with
Fproxy)
I received the "Warning: Executable code or
embedded external links in document" message when attempting to retrieve an html
page with a "http-equiv=" tag. The
> I am about to try freenet. I am installing it on Win2000P. The install
> process has come to a point where I have to chose a "Java
> interpreter".
> There are 5 lines displayed, but some directory names are
you should be happy to learn, then, that the new (.3.9) installer
doesn't behave that
Hi!
I am about to try freenet. I am installing it on Win2000P. The install
process has come to a point where I have to chose a "Java interpreter".
There are 5 lines displayed, but some directory names are long, so I can
not see the file name, only the first 3 directories near the root
directory,
48 matches
Mail list logo
