[freenet-support] [Bug report?] NullPointerException in PacketSender
Freenet 0.7 Build #1165 r22843M Freenet-ext Build #22 r22506 After running seemingly just fine for several weeks, I suddenly ran out of disk space. The problem turned out to be my freenet log, which was expanding at about a megabyte per second, full of message like this: Oct 27, 2008 22:00:01:275 (freenet.node.PacketSender, PacketSender thread for 4282, ERROR): Caught in PacketSender: java.lang.NullPointerException java.lang.NullPointerException at freenet.support.transport.ip.IPUtil.isValidAddress(IPUtil.java:13) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3915) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3909) at freenet.node.PacketSender.realRun(PacketSender.java:230) at freenet.node.PacketSender.run(PacketSender.java:168) at java.lang.Thread.run(Unknown Source) at freenet.support.io.NativeThread.run(NativeThread.java:99) I tried to re-start the node, but I think hitting the restart button didn't actually work. Shutting down didn't work, either. I had to use the Windows service manager and shut it down from there. Other than that, all seemed well. The connections to my peers were 'connected' as usual. I started the node up again (from Windows service manager), it seemed fine for a while, but my freenet-latest.log is now, once again, expanding at ~1 MB/s :P I can browse freenet OK, though.
[freenet-support] [Bug report?] NullPointerException in PacketSender
Freenet 0.7 Build #1165 r22843M Freenet-ext Build #22 r22506 After running seemingly just fine for several weeks, I suddenly ran out of disk space. The problem turned out to be my freenet log, which was expanding at about a megabyte per second, full of message like this: Oct 27, 2008 22:00:01:275 (freenet.node.PacketSender, PacketSender thread for 4282, ERROR): Caught in PacketSender: java.lang.NullPointerException java.lang.NullPointerException at freenet.support.transport.ip.IPUtil.isValidAddress(IPUtil.java:13) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3915) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3909) at freenet.node.PacketSender.realRun(PacketSender.java:230) at freenet.node.PacketSender.run(PacketSender.java:168) at java.lang.Thread.run(Unknown Source) at freenet.support.io.NativeThread.run(NativeThread.java:99) I tried to re-start the node, but I think hitting the restart button didn't actually work. Shutting down didn't work, either. I had to use the Windows service manager and shut it down from there. Other than that, all seemed well. The connections to my peers were 'connected' as usual. I started the node up again (from Windows service manager), it seemed fine for a while, but my freenet-latest.log is now, once again, expanding at ~1 MB/s :P I can browse freenet OK, though. ___ 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:[EMAIL PROTECTED]
Re: [freenet-support] [Bug report?] NullPointerException in PacketSender
On Monday 27 October 2008 23.49.18 Dan Stevens wrote: Freenet 0.7 Build #1165 r22843M Freenet-ext Build #22 r22506 After running seemingly just fine for several weeks, I suddenly ran out of disk space. The problem turned out to be my freenet log, which was expanding at about a megabyte per second, full of message like this: Oct 27, 2008 22:00:01:275 (freenet.node.PacketSender, PacketSender thread for 4282, ERROR): Caught in PacketSender: java.lang.NullPointerException java.lang.NullPointerException at freenet.support.transport.ip.IPUtil.isValidAddress(IPUtil.java:13) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3915) at freenet.node.PeerNode.shouldThrottle(PeerNode.java:3909) at freenet.node.PacketSender.realRun(PacketSender.java:230) at freenet.node.PacketSender.run(PacketSender.java:168) at java.lang.Thread.run(Unknown Source) at freenet.support.io.NativeThread.run(NativeThread.java:99) I tried to re-start the node, but I think hitting the restart button didn't actually work. Shutting down didn't work, either. I had to use the Windows service manager and shut it down from there. Other than that, all seemed well. The connections to my peers were 'connected' as usual. I started the node up again (from Windows service manager), it seemed fine for a while, but my freenet-latest.log is now, once again, expanding at ~1 MB/s :P I can browse freenet OK, though. ___ 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:[EMAIL PROTECTED] Try to update to 1166, which is released just now. ___ 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:[EMAIL PROTECTED]
