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 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 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:
>>> >>>
>>> >>> * 80.67.126.33:48685
>>> >>> * 91.114.90.176:50370
>>> >>> * 70.252.130.137:62819
>>> >>> * 74.192.11.111:1030
>>> >>> * 68.164.92.215:5510
>>> >>> * 88.115.66.96:8421
>>> >>>
>>> >>> Freenet 0.7 Build #1191 r24115M
>>> >>> Freenet-ext Build #26 r23771
>>> >>>
>>> >>> May be from #1190. Build #1191 appeared within the last 10 hours.
>>>
>> > >>> --
>>
>>> >>> Mel Charters
>>> >> Have you restarted your node since Saturday at midnight?
>>> >
>>> > Unfortunately that's now Tuesday...
>>>
>>> I just got the same thing. I repeat, the bug is still there (although not
>>> as
>>> dominant as before).
>>>
>> "Just" ? Did you or did you not restart your node after midnight GMT on
>> Tuesday?
>>
>>
> The bug is still there and I restarted at 12:15 GMT Tuesday morning. Details:
> 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
> 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:
>
> * 87.96.165.16:12938
> * 211.31.2.118:32782
> * 83.99.52.101:2587
> * 88.175.188.50:10394
> * 211.31.2.118:32768
> * 92.132.225.163:38644
>
> Freenet 0.7 Build #1191 r24115M
> Freenet-ext Build #26 r23771
>
>
This one is still seen in build 1192, although it seems to appear less
often (had sometimes around 12 forcibly disconnected with build 1190).
Freenet 0.7 Build #1192 r24161M
Freenet-ext Build #26 r23771
Stacktrace for one of the latest:
at freenet.node.PeerNode.disconnected(PeerNode.java:1139)
at freenet.node.PeerNode.onRemove(PeerNode.java:3554)
at freenet.node.OpennetPeerNode.onRemove(OpennetPeerNode.java:66)
at freenet.node.PeerManager.removePeer(PeerManager.java:338)
at freenet.node.PeerManager.disconnect(PeerManager.java:523)
at freenet.node.OpennetManager.wantPeer(OpennetManager.java:377)
at
freenet.node.OpennetManager.addNewOpennetNode(OpennetManager.java:249)
at freenet.node.Node.addNewOpennetNode(Node.java:3662)
at freenet.node.RequestSender.finishOpennet(RequestSender.java:1135)
at freenet.node.RequestSender.finish(RequestSender.java:1082)
at freenet.node.RequestSender.realRun(RequestSender.java:785)
at freenet.node.RequestSender.run(RequestSender.java:169)
at freenet.support.PooledExecutor$MyThread.run(PooledExecutor.java:190)
Greetz,
AncoL
