Re: [freenet-support] freenet fails to run 2

2009-06-19 Thread Egbert van der Meer

Yes my node connects to other nodes.
In one earlier message I have sent the wrapper log but the message 
bounced because of oversize.
___
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] freenet fails to run 2

2009-06-19 Thread Matthew Toseland
On Friday 19 June 2009 15:48:05 Egbert van der Meer wrote:
 Yes my node connects to other nodes.
 In one earlier message I have sent the wrapper log but the message 
 bounced because of oversize.
 
How many other nodes? If you click on advanced mode, it will give you totals 
for each connection type (connected, backed off, etc). Please post them here.

(I have approved your wrapper.log message btw, there doesn't seem to be 
anything particularly unusual)

The symptom is that you click on any of the bookmarks on the home page, and it 
never fetches the page? Does the seconds counter increase? Does the progress 
bar ever show more than zero?

Please reply to the list and not to me, as I will be away from tomorrow until 
the next Saturday.


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

Re: [freenet-support] freenet fails to run 2

2009-06-19 Thread Matthew Toseland
On Friday 19 June 2009 20:03:38 Egbert van der Meer wrote:
 At the moment two peers are connected.
 Downloading the page Freenet Applications has been going for 7hours and 
 nothing has come in.
 
Eeek. It should really have failed by now... I dunno what is happening, but 
your wrapper.log might be interesting. Also maybe your logs/freenet-latest.log.

Does the page continue to update? It might be a browser problem - does the time 
counter increase every 2 seconds?


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

Re: [freenet-support] freenet fails to run 2

2009-06-19 Thread Egbert van der Meer

No the page has stopt updating.
I'ts been over 13hours now.
Included freenet latest log.
jun 20, 2009 02:00:00:512 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:04:856 (freenet.node.FNPPacketMangler, UdpSocketHandler for 
port 29778(1), NORMAL): We received an unexpected JFK(2) message from 
jupiter.travisbrown.ca:16145 (time since added: 48859047 time last receive:-1)
jun 20, 2009 02:00:05:575 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:10:637 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:12:106 (freenet.node.FNPPacketMangler, UdpSocketHandler for 
port 29778(1), NORMAL): We received an unexpected JFK(2) message from 
jupiter.travisbrown.ca:16145 (time since added: 48866297 time last receive:-1)
jun 20, 2009 02:00:15:762 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:20:778 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:25:825 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:28:606 (freenet.node.FNPPacketMangler, UdpSocketHandler for 
port 29778(1), NORMAL): We received an unexpected JFK(2) message from 
jupiter.travisbrown.ca:16145 (time since added: 48882797 time last receive:-1)
jun 20, 2009 02:00:30:090 (freenet.node.MemoryChecker, Scheduled job: 
freenet.node.memorychec...@10efd7c(259), NORMAL): Memory in use: 36.0 MiB
jun 20, 2009 02:00:30:840 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:35:871 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:36:934 (freenet.node.FNPPacketMangler, UdpSocketHandler for 
port 29778(1), NORMAL): We received an unexpected JFK(2) message from 
jupiter.travisbrown.ca:16145 (time since added: 48891125 time last receive:-1)
jun 20, 2009 02:00:40:950 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:46:043 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:51:106 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening: 0  
Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
jun 20, 2009 02:00:51:621 (freenet.node.FNPPacketMangler, UdpSocketHandler for 
port 29778(1), NORMAL): We received an unexpected JFK(2) message from 
jupiter.travisbrown.ca:16145 (time since added: 48905812 time last receive:-1)
jun 20, 2009 02:00:56:121 (freenet.node.PeerManager, PacketSender thread for 
10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0  
Disconnected: 1  Never Connected: 15  Disabled: 0  

Re: [freenet-support] freenet fails to run 2

2009-06-19 Thread Evan Daniel
Your node is only connected to one other node.  This suggests to me
that you have problems with your internet connection (misconfigured
router, evil ISP, etc).

Are the opennet and darknet ports are accessible to the outside world
for UDP (forwarded at router, etc)?  Has your node correctly detected
your external IP address?

Evan Daniel

On Fri, Jun 19, 2009 at 10:07 PM, Egbert van der
Meere.vanderm...@wolmail.nl wrote:
 No the page has stopt updating.
 I'ts been over 13hours now.
 Included freenet latest log.

 jun 20, 2009 02:00:00:512 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:04:856 (freenet.node.FNPPacketMangler, UdpSocketHandler
 for port 29778(1), NORMAL): We received an unexpected JFK(2) message from
 jupiter.travisbrown.ca:16145 (time since added: 48859047 time last
 receive:-1)
 jun 20, 2009 02:00:05:575 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:10:637 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:12:106 (freenet.node.FNPPacketMangler, UdpSocketHandler
 for port 29778(1), NORMAL): We received an unexpected JFK(2) message from
 jupiter.travisbrown.ca:16145 (time since added: 48866297 time last
 receive:-1)
 jun 20, 2009 02:00:15:762 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:20:778 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:25:825 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:28:606 (freenet.node.FNPPacketMangler, UdpSocketHandler
 for port 29778(1), NORMAL): We received an unexpected JFK(2) message from
 jupiter.travisbrown.ca:16145 (time since added: 48882797 time last
 receive:-1)
 jun 20, 2009 02:00:30:090 (freenet.node.MemoryChecker, Scheduled job:
 freenet.node.memorychec...@10efd7c(259), NORMAL): Memory in use: 36.0 MiB
 jun 20, 2009 02:00:30:840 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:35:871 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:36:934 (freenet.node.FNPPacketMangler, UdpSocketHandler
 for port 29778(1), NORMAL): We received an unexpected JFK(2) message from
 jupiter.travisbrown.ca:16145 (time since added: 48891125 time last
 receive:-1)
 jun 20, 2009 02:00:40:950 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:46:043 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  Disconnecting: 0
 jun 20, 2009 02:00:51:106 (freenet.node.PeerManager, PacketSender thread for
 10039, NORMAL): Connected: 1  Routing Backed Off: 0  Too New: 0  Too Old: 0
  Disconnected: 1  Never Connected: 15  Disabled: 0  Bursting: 0  Listening:
 0  Listen Only: 0  Clock Problem: 0  Connection Problem: 0  

Re: [freenet-support] freenet fails to run 2

2009-06-19 Thread Egbert van der Meer

After a node restart I am connected to 8 other peers.
Ports are forwarded correctly.
IP is detected correctly.
This makes no difference in node performance however...
Also I am getting error messages from FROST (can not upload message)
___
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