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



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

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

* 84.181.222.55:59685