[freenet-support] Node won't connect to peers 1167/68
On Monday 03 November 2008 14:44, Jeff Isaac wrote: > Hello all! > I have recently stumbled across a problem with my node. I noticed that Frost > was having trouble communicating the other day even though the node was > running. Sure enough, the node (at the time 1167) was not connecting to any > peers (this after running successfully for a few weeks). I found the warning > about 1168 and upgraded manually, but this still does not help. It took a > while for the node to find 1168 nodes to connect to, and now I'm lucky if it > will connect to one or two busy ones. I am not sure what it means, but often > the one that is supposedly connected is highlighted in a yellow bar. I > suspect my ISP is attempting to block my node, but it puzzles me that, if > that be the case, it can still find anyone at all. All of my node's > communication is halted at this point. Would reinstalling with a new node > (and thus a new port) make a difference? Any help or suggestions would be > appreciated! > I have heard similar things on IRC. Are you the same person who reported this on IRC? Did it work with 1166? The changes since 1166 have been really minimal ... -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081103/44ceba62/attachment.pgp>
[freenet-support] upgrading node
robert fallis a ?crit : > I've been away for a few weeks. and I now get a message to upgrade my node. > my node is set to automatic update but it has not worked, How do I > upgrade my node? > help please > bob Depends on your operating system : On Windows, your should have a shortcut to update.cmd. On Linux, go in freenet's directory and run './update.sh' as a normal user (not root). -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081103/9d38c840/attachment.pgp>
[freenet-support] upgrading node
On Mon, 03 Nov 2008 18:49:02 -, Julien Cornuwel wrote: >Depends on your operating system : > On Windows, your should have a shortcut to update.cmd. > On Linux, go in freenet's directory and run './update.sh' as a normal > user (not root). > thanks, I've run ./update.sh seems a liittle slow it still hasn't loaded my boards bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
[freenet-support] Node won't connect to peers 1167/68
On Monday 03 November 2008 15.44.10 Jeff Isaac wrote: > Hello all! > I have recently stumbled across a problem with my node. I noticed that > Frost was having trouble communicating the other day even though the node > was running. Sure enough, the node (at the time 1167) was not connecting to > any peers (this after running successfully for a few weeks). I found the > warning about 1168 and upgraded manually, but this still does not help. It > took a while for the node to find 1168 nodes to connect to, and now I'm > lucky if it will connect to one or two busy ones. I am not sure what it > means, but often the one that is supposedly connected is highlighted in a > yellow bar. I suspect my ISP is attempting to block my node, but it puzzles > me that, if that be the case, it can still find anyone at all. All of my > node's communication is halted at this point. Would reinstalling with a new > node (and thus a new port) make a difference? Any help or suggestions would > be appreciated! I have almost the same problem - my freenet continues to shut down several times a day, and I have to restart and get connected to open net peers. I am using: Build #1168 r23201 and -ext Build #24 r 23199
[freenet-support] Throttling isp crashes my freenet node
My freenet node keeps crashing on me. The wrapper.log file simply says... "Restarting node: MessageCore froze for 3 minutes!" ...at which point it begins to cleanly close the databases/datastores and does finally say a clean "Goodbye from freenet.node.Node at asdf (USM deadlock)". This term "deadlock" came up a couple of times. The phrase "PacketSender deadlock" also came up in the wrapper log file. Not coincidentally, I'm sure, in my freenet log files I get *tonnes* of PacketSender errors. I'm talking about thousands of these ERROR messages logged a minute, over a hundred per second. My freenet-previous.log file was 27MB! Pretty much exclusively messages like: "(freenet.node.KeyTracker, PacketSender thread for 12345, ERROR): Packet 72390 sent over 1719253ms ago and still not acked on freenet.node.KeyTracker at blabla" My ISP is notorious for throttling p2p traffic, including blindly shaping all encrypted traffic, so I'm pretty confident that the PacketSender errors are a result of this. But this is no reason to freeze the MessageCore. I'm guessing all these rejected packets are overflowing a buffer or something, and thus freezing "MessageCore"?
[freenet-support] Node won't connect to peers 1167/68
Hello all! I have recently stumbled across a problem with my node. I noticed that Frost was having trouble communicating the other day even though the node was running. Sure enough, the node (at the time 1167) was not connecting to any peers (this after running successfully for a few weeks). I found the warning about 1168 and upgraded manually, but this still does not help. It took a while for the node to find 1168 nodes to connect to, and now I'm lucky if it will connect to one or two busy ones. I am not sure what it means, but often the one that is supposedly connected is highlighted in a yellow bar. I suspect my ISP is attempting to block my node, but it puzzles me that, if that be the case, it can still find anyone at all. All of my node's communication is halted at this point. Would reinstalling with a new node (and thus a new port) make a difference? Any help or suggestions would be appreciated! -- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081103/36c68059/attachment.html>
[freenet-support] upgrading node
robert fallis wrote: > I've been away for a few weeks. and I now get a message to upgrade my node. > my node is set to automatic update but it has not worked, How do I > upgrade my node? > help please > bob > On Windows you can open Command Prompt and go to the folder where freenet is and type: update.cmd (i think that's what it's called there now) On *nix you go to the directory where you have installed Freenet and type: ./update.sh - Volodya -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut "None of us are free until all of us are free."~ Mihail Bakunin
[freenet-support] upgrading node
I've been away for a few weeks. and I now get a message to upgrade my node. my node is set to automatic update but it has not worked, How do I upgrade my node? help please bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
[freenet-support] upgrading node
I've been away for a few weeks. and I now get a message to upgrade my node. my node is set to automatic update but it has not worked, How do I upgrade my node? help please bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ 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] upgrading node
robert fallis wrote: I've been away for a few weeks. and I now get a message to upgrade my node. my node is set to automatic update but it has not worked, How do I upgrade my node? help please bob On Windows you can open Command Prompt and go to the folder where freenet is and type: update.cmd (i think that's what it's called there now) On *nix you go to the directory where you have installed Freenet and type: ./update.sh - Volodya -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast http://eng.anarchopedia.org/ Anarchopedia, A Free Knowledge Portal http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut None of us are free until all of us are free.~ Mihail Bakunin ___ 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]
[freenet-support] Node won't connect to peers 1167/68
Hello all! I have recently stumbled across a problem with my node. I noticed that Frost was having trouble communicating the other day even though the node was running. Sure enough, the node (at the time 1167) was not connecting to any peers (this after running successfully for a few weeks). I found the warning about 1168 and upgraded manually, but this still does not help. It took a while for the node to find 1168 nodes to connect to, and now I'm lucky if it will connect to one or two busy ones. I am not sure what it means, but often the one that is supposedly connected is highlighted in a yellow bar. I suspect my ISP is attempting to block my node, but it puzzles me that, if that be the case, it can still find anyone at all. All of my node's communication is halted at this point. Would reinstalling with a new node (and thus a new port) make a difference? Any help or suggestions would be appreciated! ___ 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]
[freenet-support] Throttling isp crashes my freenet node
My freenet node keeps crashing on me. The wrapper.log file simply says... Restarting node: MessageCore froze for 3 minutes! ...at which point it begins to cleanly close the databases/datastores and does finally say a clean Goodbye from [EMAIL PROTECTED] (USM deadlock). This term deadlock came up a couple of times. The phrase PacketSender deadlock also came up in the wrapper log file. Not coincidentally, I'm sure, in my freenet log files I get *tonnes* of PacketSender errors. I'm talking about thousands of these ERROR messages logged a minute, over a hundred per second. My freenet-previous.log file was 27MB! Pretty much exclusively messages like: (freenet.node.KeyTracker, PacketSender thread for 12345, ERROR): Packet 72390 sent over 1719253ms ago and still not acked on [EMAIL PROTECTED] My ISP is notorious for throttling p2p traffic, including blindly shaping all encrypted traffic, so I'm pretty confident that the PacketSender errors are a result of this. But this is no reason to freeze the MessageCore. I'm guessing all these rejected packets are overflowing a buffer or something, and thus freezing MessageCore? ___ 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] Node won't connect to peers 1167/68
On Monday 03 November 2008 15.44.10 Jeff Isaac wrote: Hello all! I have recently stumbled across a problem with my node. I noticed that Frost was having trouble communicating the other day even though the node was running. Sure enough, the node (at the time 1167) was not connecting to any peers (this after running successfully for a few weeks). I found the warning about 1168 and upgraded manually, but this still does not help. It took a while for the node to find 1168 nodes to connect to, and now I'm lucky if it will connect to one or two busy ones. I am not sure what it means, but often the one that is supposedly connected is highlighted in a yellow bar. I suspect my ISP is attempting to block my node, but it puzzles me that, if that be the case, it can still find anyone at all. All of my node's communication is halted at this point. Would reinstalling with a new node (and thus a new port) make a difference? Any help or suggestions would be appreciated! I have almost the same problem - my freenet continues to shut down several times a day, and I have to restart and get connected to open net peers. I am using: Build #1168 r23201 and -ext Build #24 r 23199 ___ 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] upgrading node
robert fallis a écrit : I've been away for a few weeks. and I now get a message to upgrade my node. my node is set to automatic update but it has not worked, How do I upgrade my node? help please bob Depends on your operating system : On Windows, your should have a shortcut to update.cmd. On Linux, go in freenet's directory and run './update.sh' as a normal user (not root). signature.asc Description: OpenPGP digital signature ___ 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] upgrading node
On Mon, 03 Nov 2008 18:49:02 -, Julien Cornuwel [EMAIL PROTECTED] wrote: Depends on your operating system : On Windows, your should have a shortcut to update.cmd. On Linux, go in freenet's directory and run './update.sh' as a normal user (not root). thanks, I've run ./update.sh seems a liittle slow it still hasn't loaded my boards bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ 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] Node won't connect to peers 1167/68
On Monday 03 November 2008 14:44, Jeff Isaac wrote: Hello all! I have recently stumbled across a problem with my node. I noticed that Frost was having trouble communicating the other day even though the node was running. Sure enough, the node (at the time 1167) was not connecting to any peers (this after running successfully for a few weeks). I found the warning about 1168 and upgraded manually, but this still does not help. It took a while for the node to find 1168 nodes to connect to, and now I'm lucky if it will connect to one or two busy ones. I am not sure what it means, but often the one that is supposedly connected is highlighted in a yellow bar. I suspect my ISP is attempting to block my node, but it puzzles me that, if that be the case, it can still find anyone at all. All of my node's communication is halted at this point. Would reinstalling with a new node (and thus a new port) make a difference? Any help or suggestions would be appreciated! I have heard similar things on IRC. Are you the same person who reported this on IRC? Did it work with 1166? The changes since 1166 have been really minimal ... pgpfMSnIPflcy.pgp Description: PGP signature ___ 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]
