Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Saturday 10 April 2010 21:53:24 freenet wrote: Matthew, I don't monitor the node that closely. The reason for the crashes varies. It seems to usually be a null pointer exception. Usually this isn't fatal. It would be interesting to see the logs. I assume this is shown in wrapper.log? Other times it just crashes out with no warning. Other times it runs out of disk space. When that happens the entire Freenet installation virtually self destructs, corrupting key files, mostly the persistent temp files and the .db4o database. I have to totally wipe those to recover the node. The datastore seems to survive all crashes ok. Freenet really should handle running out of disk space better than this. Until Java 1.6 we don't even know how much disk space is available. And most embedded databases (thankfully not the one we use) corrupt themselves unrecoverably on out of disk space. Just pointing out that it's not as easy a problem as you might think. Really the solution is for the user to set a sensible space limit, rather than filling up the entire partition with datastore and then using even more for downloads. And we do try to help the user there, by suggesting a fraction of the detected disk size in the installer. So I've turned the log level down to minimum to help prevent runaway disk usage. Hence I no longer see much info on what might have made the node crash. I did manage to increase the size of the partition that Freenet runs from by about 2GBytes and decrease the size of the datastore by 1GByte. So far no more running out of disk space. Ah, so it's THE LOG FILES that fill up the disk? Freenet rotates log files once an hour, and there is a limit on the total size of the log files, defaulting to 128MB - but unfortunately this only includes the compressed rotated log files, not the live log files. In any case if we are using 500MB+ for one hour's logs something is seriously wrong - I suggest in that case you shut down the node, if necessary delete everything else, and send me as much of the compressed logfile as you can. Paul On Apr 8, 2010, at 8:20 AM, Matthew Toseland wrote: On Saturday 03 April 2010 03:09:47 freenet wrote: Matthew, The connectivity problem went away a while ago, just after you added the automatic update to the seednodes.fref file. Freenet has been running ok since. It runs fairly reliably now. It crashes about once every 3-4 weeks. Better than ever before when the best uptime was 7 days. Cool. Can you give me some idea of how/why it crashes when it does crash? Paul On Apr 2, 2010, at 11:48 AM, Matthew Toseland wrote: On Thursday 17 September 2009 06:37:52 freenet wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet .io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java: 839) ? ? ? at freenet .node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java: 247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at
Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Wed, Apr 14, 2010 at 1:16 PM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Saturday 10 April 2010 21:53:24 freenet wrote: Matthew, I don't monitor the node that closely. The reason for the crashes varies. It seems to usually be a null pointer exception. Usually this isn't fatal. It would be interesting to see the logs. I assume this is shown in wrapper.log? Other times it just crashes out with no warning. Other times it runs out of disk space. When that happens the entire Freenet installation virtually self destructs, corrupting key files, mostly the persistent temp files and the .db4o database. I have to totally wipe those to recover the node. The datastore seems to survive all crashes ok. Freenet really should handle running out of disk space better than this. Until Java 1.6 we don't even know how much disk space is available. And most embedded databases (thankfully not the one we use) corrupt themselves unrecoverably on out of disk space. Just pointing out that it's not as easy a problem as you might think. Really the solution is for the user to set a sensible space limit, rather than filling up the entire partition with datastore and then using even more for downloads. And we do try to help the user there, by suggesting a fraction of the detected disk size in the installer. So I've turned the log level down to minimum to help prevent runaway disk usage. Hence I no longer see much info on what might have made the node crash. I did manage to increase the size of the partition that Freenet runs from by about 2GBytes and decrease the size of the datastore by 1GByte. So far no more running out of disk space. Ah, so it's THE LOG FILES that fill up the disk? Freenet rotates log files once an hour, and there is a limit on the total size of the log files, defaulting to 128MB - but unfortunately this only includes the compressed rotated log files, not the live log files. In any case if we are using 500MB+ for one hour's logs something is seriously wrong - I suggest in that case you shut down the node, if necessary delete everything else, and send me as much of the compressed logfile as you can. Well, there's another issue as well: Freenet uses more space for the datastore than configured, by about 2-3%. https://bugs.freenetproject.org/view.php?id=3689 Evan Daniel ___ 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] Support Digest, Vol 48, Issue 12
Evan and Matthew, Like I said, I don't have the time to monitor the node that closely. When it's down, I clear the logs if they have gotten out of control, restart the node, and pray that nothing corrupted. I have turned the log level down to error and limited the logs to 8MB to try and control them. But even then I've seen the current log file explode to over 1.5GBytes. Of course the node crashed when disk space ran out. I've setup the node on special drive partitions. I set it up with 3GBytes extra. That was not enough as I discovered weeks later. I expanded the partition by 3GBytes more, but that was the limit. To go higher I need to move the large partitions around between multiple hard drives. That takes too much time. Maybe some day. It would be nice if the node would not let the current log file get out of control. Put the limits on all log files, including the wrapper logs (those get quite large too). Then fail out gracefully when disk space runs out. Then when the node restarts, put up a message and interface that lets the user stop a few downloads to free up some space before the node fully starts up. Without this, the node will just fail out again before it gets fully up. Paul On Apr 14, 2010, at 10:25 AM, Evan Daniel wrote: On Wed, Apr 14, 2010 at 1:16 PM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Saturday 10 April 2010 21:53:24 freenet wrote: Matthew, I don't monitor the node that closely. The reason for the crashes varies. It seems to usually be a null pointer exception. Usually this isn't fatal. It would be interesting to see the logs. I assume this is shown in wrapper.log? Other times it just crashes out with no warning. Other times it runs out of disk space. When that happens the entire Freenet installation virtually self destructs, corrupting key files, mostly the persistent temp files and the .db4o database. I have to totally wipe those to recover the node. The datastore seems to survive all crashes ok. Freenet really should handle running out of disk space better than this. Until Java 1.6 we don't even know how much disk space is available. And most embedded databases (thankfully not the one we use) corrupt themselves unrecoverably on out of disk space. Just pointing out that it's not as easy a problem as you might think. Really the solution is for the user to set a sensible space limit, rather than filling up the entire partition with datastore and then using even more for downloads. And we do try to help the user there, by suggesting a fraction of the detected disk size in the installer. So I've turned the log level down to minimum to help prevent runaway disk usage. Hence I no longer see much info on what might have made the node crash. I did manage to increase the size of the partition that Freenet runs from by about 2GBytes and decrease the size of the datastore by 1GByte. So far no more running out of disk space. Ah, so it's THE LOG FILES that fill up the disk? Freenet rotates log files once an hour, and there is a limit on the total size of the log files, defaulting to 128MB - but unfortunately this only includes the compressed rotated log files, not the live log files. In any case if we are using 500MB+ for one hour's logs something is seriously wrong - I suggest in that case you shut down the node, if necessary delete everything else, and send me as much of the compressed logfile as you can. Well, there's another issue as well: Freenet uses more space for the datastore than configured, by about 2-3%. https://bugs.freenetproject.org/view.php?id=3689 Evan Daniel ___ 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] Support Digest, Vol 48, Issue 12
Matthew, I don't monitor the node that closely. The reason for the crashes varies. It seems to usually be a null pointer exception. Other times it just crashes out with no warning. Other times it runs out of disk space. When that happens the entire Freenet installation virtually self destructs, corrupting key files, mostly the persistent temp files and the .db4o database. I have to totally wipe those to recover the node. The datastore seems to survive all crashes ok. Freenet really should handle running out of disk space better than this. So I've turned the log level down to minimum to help prevent runaway disk usage. Hence I no longer see much info on what might have made the node crash. I did manage to increase the size of the partition that Freenet runs from by about 2GBytes and decrease the size of the datastore by 1GByte. So far no more running out of disk space. Paul On Apr 8, 2010, at 8:20 AM, Matthew Toseland wrote: On Saturday 03 April 2010 03:09:47 freenet wrote: Matthew, The connectivity problem went away a while ago, just after you added the automatic update to the seednodes.fref file. Freenet has been running ok since. It runs fairly reliably now. It crashes about once every 3-4 weeks. Better than ever before when the best uptime was 7 days. Cool. Can you give me some idea of how/why it crashes when it does crash? Paul On Apr 2, 2010, at 11:48 AM, Matthew Toseland wrote: On Thursday 17 September 2009 06:37:52 freenet wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet .io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java: 839) ? ? ? at freenet .node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java: 247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java: 100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ? Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet .io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java: 839) ? ? ? at freenet .node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java: 247) ? ? ? at
Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Saturday 03 April 2010 03:09:47 freenet wrote: Matthew, The connectivity problem went away a while ago, just after you added the automatic update to the seednodes.fref file. Freenet has been running ok since. It runs fairly reliably now. It crashes about once every 3-4 weeks. Better than ever before when the best uptime was 7 days. Cool. Can you give me some idea of how/why it crashes when it does crash? Paul On Apr 2, 2010, at 11:48 AM, Matthew Toseland wrote: On Thursday 17 September 2009 06:37:52 freenet wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java: 100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ? Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java: 100) My Internet connection is working fine. Those two IP addresses are not reachable and the node is stuck in a loop trying to get to them. One other temporary fix was to edit the seednodes.fref file and remove the nodes with the unreachable IP addresses. Freenet 0.7.5 Build #1233 build01233 Freenet-ext Build #26 r23771 # Java Version: 1.6.0_15 # JVM Vendor: Apple Inc. # JVM Version: 14.1-b02-92 # OS Name: Mac OS X # OS Version: 10.5.8 # OS Architecture: x86_64 Sure seems like a serious bug to me. Sounds like a serious bug in your internet connection. We do indeed repeatedly send
Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Thursday 17 September 2009 06:37:52 freenet wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ?Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) My Internet connection is working fine. Those two IP addresses are not reachable and the node is stuck in a loop trying to get to them. One other temporary fix was to edit the seednodes.fref file and remove the nodes with the unreachable IP addresses. Freenet 0.7.5 Build #1233 build01233 Freenet-ext Build #26 r23771 # Java Version: 1.6.0_15 # JVM Vendor: Apple Inc. # JVM Version: 14.1-b02-92 # OS Name: Mac OS X # OS Version: 10.5.8 # OS Architecture: x86_64 Sure seems like a serious bug to me. Sounds like a serious bug in your internet connection. We do indeed repeatedly send handshaking packets to all our peers' IP addresses and this is normal and expected behaviour if two of them have invalid addresses. The first of those IP addresses listed looks like my node. I'm not sure why it made that one public; it should be using evanbd.dyndns.org. That IP is indeed not routable to the outside world; apparently my noderef is from when I was running on my father's strangely configured network (something about needing to be able to VPN into networks that
Re: [freenet-support] Support Digest, Vol 48, Issue 12
Matthew, The connectivity problem went away a while ago, just after you added the automatic update to the seednodes.fref file. Freenet has been running ok since. It runs fairly reliably now. It crashes about once every 3-4 weeks. Better than ever before when the best uptime was 7 days. Paul On Apr 2, 2010, at 11:48 AM, Matthew Toseland wrote: On Thursday 17 September 2009 06:37:52 freenet wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java: 100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ? Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java: 1794) ? ? ? at freenet .node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java: 100) My Internet connection is working fine. Those two IP addresses are not reachable and the node is stuck in a loop trying to get to them. One other temporary fix was to edit the seednodes.fref file and remove the nodes with the unreachable IP addresses. Freenet 0.7.5 Build #1233 build01233 Freenet-ext Build #26 r23771 # Java Version: 1.6.0_15 # JVM Vendor: Apple Inc. # JVM Version: 14.1-b02-92 # OS Name: Mac OS X # OS Version: 10.5.8 # OS Architecture: x86_64 Sure seems like a serious bug to me. Sounds like a serious bug in your internet connection. We do indeed repeatedly send handshaking packets to all our peers' IP addresses and this is normal and expected behaviour if two of them have invalid addresses. The first of those IP addresses listed looks like my node. I'm not sure why it made that one public; it should be using evanbd.dyndns.org. That IP is indeed not routable to the outside world; apparently my noderef is
Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Thu, Sep 17, 2009 at 1:37 AM, freenet free...@pacbell.net wrote: On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ?Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) My Internet connection is working fine. Those two IP addresses are not reachable and the node is stuck in a loop trying to get to them. One other temporary fix was to edit the seednodes.fref file and remove the nodes with the unreachable IP addresses. Freenet 0.7.5 Build #1233 build01233 Freenet-ext Build #26 r23771 # Java Version: 1.6.0_15 # JVM Vendor: Apple Inc. # JVM Version: 14.1-b02-92 # OS Name: Mac OS X # OS Version: 10.5.8 # OS Architecture: x86_64 Sure seems like a serious bug to me. Sounds like a serious bug in your internet connection. We do indeed repeatedly send handshaking packets to all our peers' IP addresses and this is normal and expected behaviour if two of them have invalid addresses. The first of those IP addresses listed looks like my node. I'm not sure why it made that one public; it should be using evanbd.dyndns.org. That IP is indeed not routable to the outside world; apparently my noderef is from when I was running on my father's strangely configured network (something about needing to be able to VPN into networks that collectively used all the various reserved-for-private nets address spaces, so he chose something unreserved that he knew to be unroutable). My updated
Re: [freenet-support] Support Digest, Vol 48, Issue 12
On Sep 16, 2009, at 10:25 AM, Evan Daniel eva...@gmail.com wrote: Message: 6 Date: Wed, 16 Sep 2009 12:46:22 -0400 From: Evan Daniel eva...@gmail.com Subject: Re: [freenet-support] My node keeps loosing all it's opennet connections To: support@freenetproject.org Message-ID: 4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland t...@amphibian.dyndns.org wrote: On Tuesday 15 September 2009 15:15:47 freenet wrote: Every few days my node just looses all it's connections. Restarting the node does not solve the problem. Usually I have to shut the node down completely for about two days. When I restart it, after about 10 minutes it starts getting connections. One time I downloaded a new seednodes.fref file and that seemed to get the connections started again. I think there is a bug where the node keeps trying to contact one or two nodes on IP addresses that are no longer valid. For example, this time I see the following two errors over and over and over and over again in the logs: Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 128.222.3.103:18143: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ?Too New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? Disabled: 0 Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 Connection Problem: 0 ?Disconnecting: 0 Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, PacketSender thread for 60973, ERROR): Error while sending packet to 5.4.174.104:60115: java.io.IOException: No route to host java.io.IOException: No route to host ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) ? ? ? at freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: 247) ? ? ? at freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) ? ? ? at freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: 1781) ? ? ? at freenet .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: 1739) ? ? ? at freenet .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) ? ? ? at freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: 2876) ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) ? ? ? at java.lang.Thread.run(Thread.java:637) ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) My Internet connection is working fine. Those two IP addresses are not reachable and the node is stuck in a loop trying to get to them. One other temporary fix was to edit the seednodes.fref file and remove the nodes with the unreachable IP addresses. Freenet 0.7.5 Build #1233 build01233 Freenet-ext Build #26 r23771 # Java Version: 1.6.0_15 # JVM Vendor: Apple Inc. # JVM Version: 14.1-b02-92 # OS Name: Mac OS X # OS Version: 10.5.8 # OS Architecture: x86_64 Sure seems like a serious bug to me. Sounds like a serious bug in your internet connection. We do indeed repeatedly send handshaking packets to all our peers' IP addresses and this is normal and expected behaviour if two of them have invalid addresses. The first of those IP addresses listed looks like my node. I'm not sure why it made that one public; it should be using evanbd.dyndns.org. That IP is indeed not routable to the outside world; apparently my noderef is from when I was running on my father's strangely configured network (something about needing to be able to VPN into networks that collectively used all the various reserved-for-private nets address spaces, so he chose something unreserved that he knew to be unroutable). My updated noderef is below. I've
