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

[Jonas Islander]

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 information to the report on the bug tracker at 
https://bugs.freenetproject.org/view.php?id=2692 or send it to the support 
mailing list supp...@freenetproject.org. Please include this message and what 
version of Freenet you are running. The affected peers (you may not want to 
include this in your bug report if they are darknet peers) are:

* 201.41.206.33:41930
«

I'm using Freenet 0.7.5 Version #1239 rbuild01239

-- 
Please send private email to Jonas Islander jonas.islan...@fastmail.fm



signature.asc
Description: OpenPGP 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:support-requ...@freenetproject.org?subject=unsubscribe

[freenet-support] Bug report

[Jérémy Farnaud]

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 gestionnaire de bug à l'adresse suivante : https://bugs.freenetproject.org/ 
 ou sur la mailing de support supp...@freenetproject.org. Veuillez  
indiquer ce message et la version utilisé par votre noeud. Les noeuds  
concernés (vous pouvez ne pas vouloir inclure ceux connectés en  
darknet) sont :

88.107.27.200:31413

./run.sh status returns: Freenet 0.7 is running (10131).

Thank you for Freenet___
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

[freenet-support] Bug report

[Doug Baggett]

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. Please report
it to us at the bug tracker at
https://bugs.freenetproject.org/http://localhost:/?_CHECKED_HTTP_=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:

   - 96.250.41.237:5219


Here is the version I was running.


   - Freenet 0.7.5 Build #1223 build01223-real
   - Freenet-ext Build #26 r23771

-Doug
___
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

[freenet-support] [BUG] Report

[dagrut]

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è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/ 
http://127.0.0.1:/?_CHECKED_HTTP_=https://bugs.freenetproject.org/ 
ou sur la mailing de support supp...@freenetproject.org. Veuillez 
indiquer ce message et la version utilisé par votre noeud. Les noeuds 
concernés (vous pouvez ne pas vouloir inclure ceux connectés en darknet) 
sont :


   * 130.75.236.38:58259

»
___
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

[Matthew Toseland]

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

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

[Juiceman]

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

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

[Juiceman]

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

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

[Matthew Toseland]

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 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:
> 
I might just have fixed this in git...
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: 

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

[Matthew Toseland]

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

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

[theymos]

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

* 122.100.218.13:41232

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

[theymos]

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:

* 122.100.218.13:41232
___
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

[freenet-support] Bug report, as requested

[Mel Charters]

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

 * 69.230.180.60:55001

Freenet 0.7 Build #1204 r25209M
Freenet-ext Build #26 r23771
-- 
Mel Charters

[freenet-support] Bug report, as requested

[Mel Charters]

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

 * 69.230.180.60:55001

Freenet 0.7 Build #1204 r25209M
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:support-requ...@freenetproject.org?subject=unsubscribe

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

[theymos]

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

* 84.181.222.55:59685
___
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

[freenet-support] Bug report

[Matthew Toseland]

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 at 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:
> 
> * 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
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: 

[freenet-support] Bug report

[toadsfri...@hushmail.com]

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

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.

Well wisher

--
Single?
Chat with sexy singles in your area now. Click Here!
http://tagline.hushmail.com/fc/u4MuRdD02WLxg7PokpzHcuvUMdPrc2FX5N2JHD5IA6gzn0nsDXyS5/

[freenet-support] Bug report

[toadsfriend]

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

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.

Well wisher

--
Single?
Chat with sexy singles in your area now. Click Here!
http://tagline.hushmail.com/fc/u4MuRdD02WLxg7PokpzHcuvUMdPrc2FX5N2JHD5IA6gzn0nsDXyS5/

___
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

[Matthew Toseland]

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]

[freenet-support] Bug report

[toadsfriend]

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 you are 
running. The affected peers (you may not want to include this in 
your bug report if they are darknet peers) are: 24.80.101.100:16145

My node:
Freenet 0.7 Build #1181 r23784
Freenet-ext Build #26 r23771

Hope this helps.

--
Single?
Chat with sexy singles in your area now. Click Here!
http://tagline.hushmail.com/fc/u4MuRdD02Vyd5fLrWa8x5TbtidCV9vLzWQQuOVc30M8iFLKpzudc5/

___
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] Bug report

[toadsfri...@hushmail.com]

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 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: 24.80.101.100:16145

My node:
Freenet 0.7 Build #1181 r23784
Freenet-ext Build #26 r23771

Hope this helps.

--
Single?
Chat with sexy singles in your area now. Click Here!
http://tagline.hushmail.com/fc/u4MuRdD02Vyd5fLrWa8x5TbtidCV9vLzWQQuOVc30M8iFLKpzudc5/

[freenet-support] Bug Report

[Ted Hexter]

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 you are running. The affected peers (you may not
want to include this in your bug report if they are darknet peers) are:
* 24.213.86.235:29470
* 217.236.111.120:25601___
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] bug report: 2 peers forcibly disconnected due to not acknowledging packets

[Ulrich Koepping]

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

* 98.197.198.209:60008
* 78.70.60.132:30842

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

[Ulrich Koepping]

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

* 98.197.198.209:60008
* 78.70.60.132:30842




  
___
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] Bug Report

[Ted Hexter]

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 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:
* 24.213.86.235:29470
* 217.236.111.120:25601
-- next part --
An HTML attachment was scrubbed...
URL: 

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

[Dan Stevens]

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.

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

[Dan Stevens]

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]

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

[bqz69]

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]

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

[Julien Cornuwel]

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

[Julien Cornuwel]

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

[Matthew Toseland]

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]

[freenet-support] Bug Report - win32 - freenet.exe - logFile=*path* not handled

[Rudolf Krist]

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]

Re: [freenet-support] Bug Report - win32 - freenet.exe - logFile=*path*not handled

[dave]

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

[dave]

(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

[dave]

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]

[freenet-support] bug report (?)

[Klaus Brüssel]

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 queue
java.lang.IllegalStateException: Not sending a trailer
at 
freenet.ConnectionHandler$TrailerSendState.hasTrailerDataRemaining(ConnectionHandler.java:163)
at freenet.ConnectionHandler.jobDone(ConnectionHandler.java:1251)
at freenet.ConnectionHandler.terminate(ConnectionHandler.java:2413)
at freenet.ConnectionHandler.queuedClose(ConnectionHandler.java:1426)
at 
freenet.transport.AbstractSelectorLoop.queueClose(AbstractSelectorLoop.java:764)
at 
freenet.transport.ThrottledSelectorLoop.queueClose(ThrottledSelectorLoop.java:414)
at 
freenet.transport.AbstractSelectorLoop.queueClose(AbstractSelectorLoop.java:812)
at 
freenet.transport.ReadSelectorLoop.beforeSelect(ReadSelectorLoop.java:168)
at 
freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:661)
at freenet.transport.ReadSelectorLoop.run(ReadSelectorLoop.java:674)
at java.lang.Thread.run(Thread.java:536)
___
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]

[freenet-support] Bug report

[Johnix]

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 connexion), and issuing this type of messages.

Have fun, and tell me if you need more info.

Waited more than 200ms to dequeue, 61 in queue, 2324 millis since enqueued last item, 
852104 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, 12 in queue, 2368 millis since enqueued last item, 
1095740 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, 18 in queue, 2842 millis since enqueued last item, 
1710832 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, 20 in queue, 3340 millis since enqueued last item, 
1242093 maximum waits so far - could indicate serious JVM bug. Please report to [EMAIL 
PROTECTED] along with JVM and OS/kernel.
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.Exception
at freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:729)
at freenet.transport.ReadSelectorLoop.run(ReadSelectorLoop.java:674)
at java.lang.Thread.run(Thread.java:536)
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Could not execute freenet.Message: QueryRejected @[EMAIL PROTECTED] 
MuxConnectionHandler[conn=[tcp/connection: CLOSED,[EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED], identity=[DSA(8c25 c9b8 98c3 1722 faf7  9ee7 369e df35 
a323 e694)], sock=[Socket[addr=/81.169.158.212,port=9340,localport=40097]], 
chan=[java.nio.channels.SocketChannel[closed]], peer=[Peer [DSA(8c25 c9b8 98c3 1722 
faf7  9ee7 369e df35 a323 e694) @ 81.169.158.212:9340 (1/3)]], outbound=[true]] @ 
eb35f6696e67de03: htl=9, reason=Node overloaded @ 1076132849477: 
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Caught a java.lang.OutOfMemoryError, LSL.processConnections failing
java.lang.OutOfMemoryError
java.lang.Exception
at freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:729)
at freenet.transport.ListenSelectorLoop.run(ListenSelectorLoop.java:146)
at java.lang.Thread.run(Thread.java:536)
java.lang.NullPointerException
at 
freenet.transport.AbstractSelectorLoop.mySelect(AbstractSelectorLoop.java:600)
at freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:675)
at freenet.transport.ReadSelectorLoop.run(ReadSelectorLoop.java:674)
at java.lang.Thread.run(Thread.java:536)
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError


-- 
Thomas Tempé 
http://www.alysse.org/tom

So here we are: the few, the proud, the Dvorak keyboard
users.  Let's keep threatening the world with our divisive,
controversial use of letter arrangement in typing.

___
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]

[freenet-support] Bug report

[Victor Hammersley]

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 queue, 2047 millis since enqueued last 
item, 345291 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 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

Linux 2.6.0-0.test5.1mdk #1 Fri Sep 12 05:22:50 CEST 2003 i686 unknown unknown 
GNU/Linux

hope this helps
-- 
Victor Hammersley R.,  vhammer en iname pto com
counter.li.org user #293717
Las armas se deben reservar para el último lugar, donde y cuando
 los otros medios no basten. -- Maquiavelo.
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support

[freenet-support] Bug report

[Victor Hammersley]

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 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

Linux 2.6.0-0.test5.1mdk #1 Fri Sep 12 05:22:50 CEST 2003 i686 unknown unknown 
GNU/Linux

hope this helps
-- 
Victor Hammersley R.,  vhammer en iname pto com
counter.li.org user #293717
Las armas se deben reservar para el último lugar, donde y cuando
 los otros medios no basten. -- Maquiavelo.
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support