Re: [freenet-support] Off FN

2011-02-15 Thread Dsoslglece 

Le 15/02/11 17:52, Jep a écrit :
After several days of v1352, all connections to strangers dropped and 
my node is offline once more for the whole night and day.
With as only known, possible recipe: a complete reinstall of FN from 
scratch. New port numbers, the entire config anew.


This is not usual, normally the connection problem only appears when 
updating or at system reboot. This time all connections disappeared by 
themselves.


There is something unusual going on.
This is the latest snip from the wrapper log, so while off FN:


feb 15, 2011 16:38:00:406 (freenet.node.PeerManager, Scheduled job: 
freenet.node.PacketSender$2@127ff0d(20), NORMAL): Connected: 0  
Routing Backed Off: 0  Too New: 0  Too Old: 0  Disconnected: 36  Never 
Connected: 16  Disabled: 0  Bursting: 0  Listening: 0  Listen Only: 0 
Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
feb 15, 2011 16:38:00:906 (freenet.node.RequestTag, 
RequestStarter$SenderThread for 
freenet.client.async.TransientChosenBlock@c62333(20), NORMAL): 
Unlocking freenet.node.RequestTag@9bc5f9:-2509779670402383326 
(unlocked handler)

java.lang.Exception: debug
at freenet.node.UIDTag.mustUnlock(UIDTag.java:245)
at freenet.node.RequestTag.mustUnlock(RequestTag.java:62)
at freenet.node.UIDTag.unlockHandler(UIDTag.java:256)
at freenet.node.UIDTag.unlockHandler(UIDTag.java:266)
at freenet.node.NodeClientCore.realGetSSK(NodeClientCore.java:1232)
at freenet.node.NodeClientCore.realGetKey(NodeClientCore.java:983)
at 
freenet.node.SendableGetRequestSender.send(SendableGetRequestSender.java:44)

at freenet.client.async.ChosenBlock.send(ChosenBlock.java:66)
at 
freenet.node.RequestStarter$SenderThread.run(RequestStarter.java:251)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227)

at freenet.support.io.NativeThread.run(NativeThread.java:130)
feb 15, 2011 16:38:01:359 (freenet.io.comm.UdpSocketHandler, 
PacketSender thread for [*], NORMAL): Error while sending packet 
to IPv6 address: 2001:0:4137:9e76:38de:544:b382:a8a8:14871: 
java.net.SocketException: Protocol not allowed
feb 15, 2011 16:38:03:671 (freenet.io.comm.UdpSocketHandler, 
PacketSender thread for [*], NORMAL): Error while sending packet 
to IPv6 address: 2002:411d:20e5:0:0:0:411d:20e5:60919: 
java.net.SocketException: Protocol not allowed
feb 15, 2011 16:38:05:281 (freenet.io.comm.UdpSocketHandler, 
PacketSender thread for [*], NORMAL): Error while sending packet 
to IPv6 address: 2001:0:4137:9e76:2c16:e0e:345e:c435:35487: 
java.net.SocketException: Protocol not allowed
feb 15, 2011 16:38:05:781 (freenet.io.comm.UdpSocketHandler, 
PacketSender thread for [*], NORMAL): Error while sending packet 
to IPv6 address: 2001:0:4137:9e76:247b:3fd6:ad13:a072:10032: 
java.net.SocketException: Protocol not allowed



Normally it only gives rows of 'trying to connect to some seednodes'.

___
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


Well, got the same problem since yesterday…
will now reinstall it from scrach and just copy the temporaries etc into 
the new install… and see what the hell it does…
___
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] Off FN

2011-02-15 Thread Jan 

Dennis Nezic schreef:

On Tue, 15 Feb 2011 17:52:57 +0100, Jep wrote:

After several days of v1352, all connections to strangers dropped and
my node is offline once more for the whole night and day.
With as only known, possible recipe: a complete reinstall of FN from 
scratch. New port numbers, the entire config anew.


This is not usual, normally the connection problem only appears when 
updating or at system reboot. This time all connections disappeared

by themselves.

[...]
(freenet.io.comm.UdpSocketHandler, PacketSender thread for [*],
NORMAL): Error while sending packet to IPv6 address: ***:
java.net.SocketException: Protocol not allowed
[...]


Looks like some kind of ipv6 issue/bug. Maybe you can try adding:

   wrapper.java.additional.4=-Djava.net.preferIPv4Stack=true

to your wrapper config file, or somehow to freenet's command line, to
try to avoid using ipv6?


Thanks for your reply, Dennis.
Before wiping it all again, I tried a restart w/o nodedb4o and also a 
manual update.
The update to the not yet announced here 1355 brought my node back, but 
if I run into the same problem I'll try your suggestion.


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

2011-02-15 Thread Matthew Toseland 
On Tuesday 15 Feb 2011 19:41:51 Jan wrote:
 Dennis Nezic schreef:
  On Tue, 15 Feb 2011 17:52:57 +0100, Jep wrote:
  After several days of v1352, all connections to strangers dropped and
  my node is offline once more for the whole night and day.
  With as only known, possible recipe: a complete reinstall of FN from 
  scratch. New port numbers, the entire config anew.
 
  This is not usual, normally the connection problem only appears when 
  updating or at system reboot. This time all connections disappeared
  by themselves.
 
  [...]
  (freenet.io.comm.UdpSocketHandler, PacketSender thread for [*],
  NORMAL): Error while sending packet to IPv6 address: ***:
  java.net.SocketException: Protocol not allowed
  [...]
  
  Looks like some kind of ipv6 issue/bug. Maybe you can try adding:
  
 wrapper.java.additional.4=-Djava.net.preferIPv4Stack=true
  
  to your wrapper config file, or somehow to freenet's command line, to
  try to avoid using ipv6?
 
 Thanks for your reply, Dennis.
 Before wiping it all again, I tried a restart w/o nodedb4o and also a 
 manual update.
 The update to the not yet announced here 1355 brought my node back, but 
 if I run into the same problem I'll try your suggestion.

Glad to hear that, thanks for reporting the issue. What about other people? 
Dsoslglece?

I seriously doubt that the IPv6 issues are anything to worry about.


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