[freenet-support] ARKs USKs and SSKs (from Frost)
needed, and since I suspect we have overcapacity in SSKs, that should greatly improve ARKs' reliability. 2. It is hard to find the latest version of a USK when you've lost your place. IMHO the simplest, fastest, and most reliable solution to this is date-based hierarchical pointers (which would simply include the latest edition at a given time). Hence: USK at blah/site/12 -> SSK at blah/site-12 // the actual content But we also insert SSK at blah/site-___DATE___-2008 SSK at blah/site-___DATE___-2008-11 SSK at blah/site-___DATE___-2008-11-14 All of which contain the current edition number, "12". > > == End == > > -- > 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 -- 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/20081114/8c4089cf/attachment.pgp>
[freenet-support] Some downloads failing since updating to 1178
Argh. Are these simple downloads (CHK at .../filename), or parts of freesites (mutliple slashes, maybe USKs)?? On Friday 14 November 2008 22:01, Victor Denisov wrote: > Several downloads from my download queue failed to start after my node > autoupgraded to 1178 (some *did* restart normally). Error messages > (Reason column in the "Failed downloads") in the web interface vary: > > Temporary files error: invalid stored block lengths > Temporary files error: Corrupt GZIP trailer > Temporary files error: invalid literal/length code > Temporary files error: invalid distance code > Temporary files error: invalid block type > > The node gives me two options: Remove and Restart. If I click on > restart, the item fails almost immediately with the same error it had > before. > > I've migrated to salted-hash store when 1175 went out. I tried > restarting the node again and cleaning up ./tmp - not helped any. I have > plenty of disk space. Log files don't seem to contain anything related > to the issue I'm experiencing. > > Running on Windows XP x64 with Java 1.6.0_06, 64 bit. > > Regards, > Victor Denisov. > ___ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -- 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/20081114/3398909f/attachment.pgp>
[freenet-support] Former mail "Can't open again" is out of date. Need Friends.
On Friday 14 November 2008 14:56, Markus Hahn wrote: > Dear Supporters, > > the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some "friends". > But still I don't know how to operate it from the command line (bash or dash). Thanks. Most basic functions of Freenet are controlled from the web interface (http://127.0.0.1:/). You might have to forward (ssh -L) port and 9481 to another machine, although in theory it should work with lynx/links. There are third party command line tools available for tasks such as inserting data... -- 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/20081114/3d7fd332/attachment.pgp>
[freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)
On Friday 14 November 2008 23:21, Dennis Nezic wrote: > On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland > wrote: > > > Freenet 0.7 build 1178 is now available. > > Wow! What a difference. 1178 is like a totally different program, with > respect to both cpu and memory usage. THANK YOU! It's no longer peaking > for minutes at a time. It's consistently low. My 15minute load average > is below 1 now! Hurray. Memory use also seems much lower. > > Regarding the "not acked packets" problem, I have alrady been alerted > about 5 peers with "severe" problems, one of which is a darknet peer. 2 > of the others are listed as CONNECTED. And the other 2 are listed as > BACKED OFF. All of them are running 1178. > > Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED > to me both in opennet and darknet. That's to be expected. We kill the connection, and purge the trackers etc, but we can reconnect afterwards. Also, it's quite possible that those peers were running an earlier version when they actually broke. However, it's also possible that we still have the underlying bug... I've not made much headway with finding it, next week we should know whether it's still active, since 1178 is mandatory on Sunday... > > All in all, though, 1178 is a HUGE improvement! -- 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/20081114/b328baca/attachment.pgp>
[freenet-support] Freenet 0.7 build 1175
On Friday 14 November 2008 17:40, Dennis Nezic wrote: > On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland > wrote: > > > Freenet 0.7 build 1175 is now available. Please upgrade. Changes: > > - Handle the "Packet X sent Yms ago and still not acked" bug better. > > Don't complain in the log until 10 minutes, then disconnect from the > > peer and log the fact. We can then reconnect, but we will do so > > cleanly, so hopefully not get it again for a while. It seems that > > most of the disruption caused by this bug was caused by the logging > > on every resend and not the bug itself... Of course we will need to > > fix the bug too. > > State Of The (My) 1175... It "feels" like it's running smoother, > although it's cpu profile here hasn't changed substantially. Perhaps > just a bit, due to better logging. The log files are finally usable! > (Usually under 100K per hour now :) It still has 100% CPU most of the time then? Apparently resulting from Freenet itself rather than downloads etc? Try 1178 ... and then wait until say Wednesday ... hopefully once everyone has 1178, it will be much better. > > So, in one random 1 hour sample, here are the main ones that I get: > > 4 "Forcing disconnect" PacketSender ERRORs, both from opennet and > darknet peers, "because packets not acked after 10 minutes!". Does this > mean that NO packets have been received from these peers, or just a big > bunch of them? (I'm pretty sure my ISP doesn't kill connections, but > just drops a fraction of the packets.) For some reason, these error > messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) > netPeerNode. This is caused by the bugs we're chasing at the moment. Hopefully next week it will have gone away, or be very rare. It means that we are still connected to the node, it's still sending us packets, but it apparently doesn't understand some of the packets we send it. > > 40 MessageCore ERRORs "from RequestSender waitFor _unclaimed iteration > took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit" or > "from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize > of 596 for matched: true" > > 24 freenet.io.xfer.BlockTransmitter.sendAsync(), "Terminated send > -123413232423 ... as we haven't heard from receiver in 1m54s." > > 4 freenet.io.xferPacketThrottle, Blocktransmitter: "Unable to send > throttled message, waited 60100ms" > > 6 freenet.io.comm.MessageCore Scheduled job ERRORS > "removeTimedOutFilters took 4000ms" Hopefully these are related to the current bugs. If so they should greatly reduce. On the other hand, they may not be ... > > 4 freenet.node.KeyTracker PacketSender "Packet 1234 sent over 600600ms > ago and still not acked". (THEY STILL EXIST!?! ;) Yes, we log them at the same time as the disconnections. > > 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet > and opennet), "processing packet took 4000ms" .. with times ranging > from 3000ms to 6600ms. > > 8 freenet.node.FNPPacketMangler "Message[1..4] timeout error: > Processing packet for freenetnode.tld:1234" > > Also, in this log, I have noticed that the port number, in the > @ip:port@ portion of the error message does NOT match the port number > listed on the /friends/ web page. Why is that? It can be different, usually because of NATs, occasionally because you are connected both to the darknet and opennet nodes on that IP (which is a bug, shouldn't happen unless you have some wierd configs set). > (What happens, by the > way, if a darknet peer does change his port, by the way--we'd have to > re-add his node reference?) Probably yes. -- 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/20081114/973c40ee/attachment.pgp>
[freenet-support] Wrapper does not start
On Friday 14 November 2008 01:09, freenet at chello.at wrote: > Since last update on 13.11. Freenet fails to start. > I get the following Message in wrapper.log: You let freenet auto-update itself, or you used update.sh/update.cmd? If you let Freenet auto-update itself, then please send me your wrapper.log, as this is a serious bug we've been trying to gather more info on ... You can get your node back by running update.sh/update.cmd. > > STATUS | wrapper | 2008/11/14 02:01:01 | Launching a JVM... > INFO | jvm 5| 2008/11/14 02:01:01 | java.lang.NoClassDefFoundError: freenet/node/NodeStarter > INFO | jvm 5| 2008/11/14 02:01:01 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter > INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader$1.run(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | at java.security.AccessController.doPrivileged(Native Method) > INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader.findClass(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClassInternal(Unknown Source) > INFO | jvm 5| 2008/11/14 02:01:01 | Exception in thread "main" > ERROR | wrapper | 2008/11/14 02:01:01 | JVM exited while loading the application. > FATAL | wrapper | 2008/11/14 02:01:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. > FATAL | wrapper | 2008/11/14 02:01:01 | There may be a configuration problem: please check the logs. > STATUS | wrapper | 2008/11/14 02:01:01 | <-- Wrapper Stopped > > I already included "wrapper.restart.delay=15" to wrapper.conf - but that only delays the hangup. > > My OS is WinXP pro SP3 > > ___ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -- 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/20081114/f872a408/attachment.pgp>
[freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)
Freenet 0.7 build 1178 is now available. Please upgrade. Sorry I accidentally released 1176, then had some bugfixes in 1177 and 1178. Anyway, the main changes relative to 1175: - Try to prevent both sides of a connection attempting to rekey at the same time, by having the receiver start 2.5 minutes early. This seems to have been the root cause of many of the recent problems. It may not be completely fixed, but should happen much less often. - When we disconnect from a peer because of it not acknowledging our packets, tell the user via a useralert as well as logging an error. - Get rid of WouldBlockException errors as well: If we cannot send a packet to a peer because there are too many packets in flight and none are being acknowledged, don't busy-loop and spam the logs, wait for it to become un-blocked again. If it doesn't become un-blocked in 10 minutes, log an error and tell the user via a useralert. - Change the default log rotation period to 10 minutes rather than 1 hour to save disk space. - Clarify the config option for packet padding: Turning off packet padding is BAD. Packet padding is essential against a passive attacker. In the next few days you may see the "Probably a bug" errors on the web interface. Hopefully once this build is mandatory (on Monday) these will go away. If you still see these from Tuesday onwards, let us know. Please update, and let us know how it works out. Hopefully this build will fix most of the recent network problems, oversized log files and high CPU usage when not doing anything. If you find any bugs, please report them on the bug tracker: https://bugs.freenetproject.org/ . Thanks. -- 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/20081114/ca5614f9/attachment.pgp>
[freenet-support] connecting
On Thursday 13 November 2008 22:47, Lorraine Martineau wrote: > I thought that I had downloaded all the requirements for registering with Freenet . I was however stumped by the userid question and didn't fill it . I probably should have entered "lorraine". > Can you see this application and tell me how to retrieve it, or do I start over. > Thank you for your assistance. > I wish to disconnect from Cyberus. Is that the first thing to do...I didn't know how I could connect to Freenet without a server. > Lorraine Martineau > lmartineau at freenet.ca I hope!!! I really think you've got the wrong Freenet here ... This mailing list is for http://freenetproject.org/ : a censorship resistant peer to peer network: == What is Freenet? Freenet is free software which lets you publish and obtain information on the Internet without fear of censorship. To achieve this freedom, the network is entirely decentralized and publishers and consumers of information are anonymous. Without anonymity there can never be true freedom of speech, and without decentralization the network will be vulnerable to attack. Communications by Freenet nodes are encrypted and are "routed-through" other nodes to make it extremely difficult to determine who is requesting the information and what its content is. Users contribute to the network by giving bandwidth and a portion of their hard drive (called the "data store") for storing files. Unlike other peer-to-peer file sharing networks, Freenet does not let the user control what is stored in the data store. Instead, files are kept or deleted depending on how popular they are, with the least popular being discarded to make way for newer or more popular content. Files in the data store are encrypted to reduce the likelihood of prosecution by persons wishing to censor Freenet content. The network can be used in a number of different ways and isn't restricted to just sharing files like other peer-to-peer networks. It acts more like an Internet within an Internet. For example Freenet can be used for: * Publishing websites or 'freesites' * Communicating via message boards * Content distribution * Sending email messages Unlike many cutting edge projects, Freenet long ago escaped the science lab, it has been downloaded by over 2 million users since the project started, and it is used for the distribution of censored information all over the world including countries such as China and the Middle East. Ideas and concepts pioneered in Freenet have had a significant impact in the academic world. Our 2000 paper "Freenet: A Distributed Anonymous Information Storage and Retrieval System" was the most cited computer science paper of 2000 according to Citeseer, and Freenet has also inspired papers in the worlds of law and philosophy. Ian Clarke, Freenet's creator and project coordinator, was selected as one of the top 100 innovators of 2003 by MIT's Technology Review magazine. -- 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/20081114/0a6c8f67/attachment.pgp>
[freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)
On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland wrote: > Freenet 0.7 build 1178 is now available. Wow! What a difference. 1178 is like a totally different program, with respect to both cpu and memory usage. THANK YOU! It's no longer peaking for minutes at a time. It's consistently low. My 15minute load average is below 1 now! Hurray. Memory use also seems much lower. Regarding the "not acked packets" problem, I have alrady been alerted about 5 peers with "severe" problems, one of which is a darknet peer. 2 of the others are listed as CONNECTED. And the other 2 are listed as BACKED OFF. All of them are running 1178. Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED to me both in opennet and darknet. All in all, though, 1178 is a HUGE improvement!
[freenet-support] Former mail "Can't open again" is out of date. Need Friends.
On Fri, 14 Nov 2008 14:56:25 + (GMT), Markus Hahn wrote: > Dear Supporters, > > the question I have sent to you some hours ago is obsolete. I have > found the button to start it again. Freenet is running properly. Now > I should try to find some "friends". But still I don't know how to > operate it from the command line (bash or dash). Thanks. Out of curiosity, what kinds of things were you looking to do via the command line? There is, by the way, a telnet interface that lets you do quite a bit, which is disabled by default. There are also some command line tools that interface with freenet, such as pyFreenet, that might be useful, if they work :).
[freenet-support] Freenet 0.7 build 1175
On Fri, 14 Nov 2008 19:52:46 +, Matthew Toseland wrote: > It still has 100% CPU most of the time then? Apparently resulting > from Freenet itself rather than downloads etc? Well, it's not /so/ serious that it stays at 100% all the time. It jumps up for a few minutes, then calms down to almost nothing for a few minutes. (The valleys are longer than the peaks.) And keeps repeating this. I'm running another process that steadily uses on average 25% of the (1.2GHz) cpu, and my 15minute load time is consistently around 3. Maybe the threads are all triggered to run at the same time, and should be staggered? > > Also, in this log, I have noticed that the port number, in the > > @ip:port@ portion of the error message does NOT match the port > > number listed on the /friends/ web page. Why is that? > > It can be different, usually because of NATs, occasionally because > you are connected both to the darknet and opennet nodes on that IP > (which is a bug, shouldn't happen unless you have some wierd configs > set). Actually, the logs do say that I was connected to this same ip address both in opennet and darknet :|. (And the opennet port is properly listed in the strangers page. (It seems unlikely that his darknet port would be routed in a NAT, but not his opennet port :|.)
[freenet-support] Former mail "Can't open again" is out of date. Need Friends.
Dear Supporters, the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some "friends". But still I don't know how to operate it from the command line (bash or dash). Thanks. -- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081114/4e5fae5d/attachment.html>
[freenet-support] Freenet 0.7 build 1175
On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland wrote: > Freenet 0.7 build 1175 is now available. Please upgrade. Changes: > - Handle the "Packet X sent Yms ago and still not acked" bug better. > Don't complain in the log until 10 minutes, then disconnect from the > peer and log the fact. We can then reconnect, but we will do so > cleanly, so hopefully not get it again for a while. It seems that > most of the disruption caused by this bug was caused by the logging > on every resend and not the bug itself... Of course we will need to > fix the bug too. State Of The (My) 1175... It "feels" like it's running smoother, although it's cpu profile here hasn't changed substantially. Perhaps just a bit, due to better logging. The log files are finally usable! (Usually under 100K per hour now :) So, in one random 1 hour sample, here are the main ones that I get: 4 "Forcing disconnect" PacketSender ERRORs, both from opennet and darknet peers, "because packets not acked after 10 minutes!". Does this mean that NO packets have been received from these peers, or just a big bunch of them? (I'm pretty sure my ISP doesn't kill connections, but just drops a fraction of the packets.) For some reason, these error messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) netPeerNode. 40 MessageCore ERRORs "from RequestSender waitFor _unclaimed iteration took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit" or "from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize of 596 for matched: true" 24 freenet.io.xfer.BlockTransmitter.sendAsync(), "Terminated send -123413232423 ... as we haven't heard from receiver in 1m54s." 4 freenet.io.xferPacketThrottle, Blocktransmitter: "Unable to send throttled message, waited 60100ms" 6 freenet.io.comm.MessageCore Scheduled job ERRORS "removeTimedOutFilters took 4000ms" 4 freenet.node.KeyTracker PacketSender "Packet 1234 sent over 600600ms ago and still not acked". (THEY STILL EXIST!?! ;) 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet and opennet), "processing packet took 4000ms" .. with times ranging from 3000ms to 6600ms. 8 freenet.node.FNPPacketMangler "Message[1..4] timeout error: Processing packet for freenetnode.tld:1234" Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? (What happens, by the way, if a darknet peer does change his port, by the way--we'd have to re-add his node reference?)
[freenet-support] ARKs USKs and SSKs (from Frost)
Somebody has asked me to send this (i will post the original in Russian and then the translation done by me) (please note that i don't really think that all of this makes sense, i'm an interpreter) == Original == ? USK ??? ?? ARK ? ? ??. ?? ???: ??? ?? ? IP, ??? ? ?? ??? ??? ? ?, ? ?? ARK ?? ?, ??? ?? ???, ?? ?? ?? ?? - ? ??? ? "???" ?? , ? ??? ?? . ? ??, ??, ?? ? ?? "" ? ?? ?? ARK ?? ? 4 ??, ??? ??? ?? ??? USK - ? ? "???" ARK ??? ??. ??? ? ??? , ?? ?? ? ? ??? IP. ? ??? ? ?? ?? ARK ?? ??, ?? ??? ? ??? ?? ? ??? ?? ?? ?? 5 ?? 100 ?? ? ? ? (??? ? ??? ?? ???, ? ?? ??). ??? ?? ? ?? ?? 4, ? 44 ??? ??. ?? ??? ?? USK/SSK ?? ? ?? ? ??? ? ?? ? ?? SSK, ? ?? ?? ???. ??? ??? , ??? ?? ? SSK ? ??? ? ???, ? ? ??? ? ?? ?. ? ?, _???_ ? ??? , ??? ?? ??? ??? ? , ? ??? ?? ? ?? ?? ?? ?. ? ?? (?? ?) ?? ??? ?? ?? ?? ? ? ??? SSK. ?? ?? ?? ? ? ? ?? SSK ? ?? ?? ? ? ??? ? ??? ??? ? ???, ? ? ? ?? SSK. ??? ?? ? ?? ? ?? ?? ?. ? ?, ??? ??? ?? ?? ??, ? ? ?? ? ?? SSK - ? ?? ??? ? ???. ? ??? ? ??? ?? ? ?? ? ?? SSK ?? ? ?? ? ? ? ??? ? ? ? ? ???, ??? ??? ? ??. ??? ?? ???, ? ? ? ??? ? ?? ??? : ? ?? (??? ? ?? ???), ? (?? , ? ?? ? ? ? ?? ? ? ???) ??? ?? ? ??? ? ?? SSK, ?? ?? ? SSK ? ?? ?? ?? ??? ?? ? ?? ?? - ?? ? ??? ??? ?? ? ??? (??? ?? ??? ? ?? ?? ??? ??? ??). ??? ? ? ??? ?? ARK, ? ? ? ??? ? ?? ?? ARK, ?? ??? ?? ? ?, ??? ? ?? ? ? . ? ? ??? ?? ?, ?? ?? ?? ?? ?: ?? ARK ?? ? ??? ? "???" ?? , ?? ??? ? ?? ??? ? - ? ??? ??? ??, ?? ? ? IP, ?? ?? ARK. == Translation == Using of USK for the implimentation of ARK has obvious downfalls. One of them is that during the rapid change of IP, for example during the change of the version of the node or during the repeated connection loss, number of ARK increases rapidly, and during this process there is no attempt to check if previous versions are still accessible; and they can "fall out" from the network, if almost instantaneously other nodes are restarting. As a result, as it seems, quite often "breaks" in the sequence of ARK appear with the length of more than 4 versions, which is a requirement for the working of normal USK; this leads to the search for the "new" ARK number giving no results. This is especially important for the nodes working less than 24 hours a day and having a dynamic IP. One solution may be a request for ARK far ahead, say a few times with the random increase of a version number from 5 to 100 related to the existing one (of course distributed not equally, but maybe as a reverse exponent). Or a dumb request for 44 rather than 4 following versions. Another bug problem of USK/SSK is related to the algorithm of attempting repeat write to the existing SSK, when a specific version is provided. Node after finding that another programme attempts to write SSK with the already existing version immediately interrupts the request and notifies the programme. Unfortunately _ALL_ the programmes after that assume that information is already on the network, and if no new information exists do
[freenet-support] Wrapper does not start
Since last update on 13.11. Freenet fails to start. I get the following Message in wrapper.log: STATUS | wrapper | 2008/11/14 02:01:01 | Launching a JVM... INFO | jvm 5| 2008/11/14 02:01:01 | java.lang.NoClassDefFoundError: freenet/node/NodeStarter INFO | jvm 5| 2008/11/14 02:01:01 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader$1.run(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader.findClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClassInternal(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | Exception in thread "main" ERROR | wrapper | 2008/11/14 02:01:01 | JVM exited while loading the application. FATAL | wrapper | 2008/11/14 02:01:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2008/11/14 02:01:01 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2008/11/14 02:01:01 | <-- Wrapper Stopped I already included "wrapper.restart.delay=15" to wrapper.conf - but that only delays the hangup. My OS is WinXP pro SP3
[freenet-support] ARKs USKs and SSKs (from Frost)
Somebody has asked me to send this (i will post the original in Russian and then the translation done by me) (please note that i don't really think that all of this makes sense, i'm an interpreter) == Original == Использование USK для реализации ARK имеет явные недостатки. Один из них: при частой смене IP, например при изменении версий узла или при повторяющихся разрывах связи, номер версии ARK быстро увеличивается, при этом не проверяется, являются ли доступными предыдущие версии - а они могут выпасть из сети, если почти одновременно перезагружаются другие узлы. В результате, похоже, достаточно часто появляются пропуски в последовательности версий ARK длиной более 4 номера, необходимых для работы обычных USK - и поиск свежего значения ARK оказывается безуспешен. Это особенно важно для улов, работающих не круглосуточно и имеющих динамический IP. Вариантом решения может быть запрос версий ARK далеко вперёд, скажем ещё несколько раз со случайным увеличением номера версии от 5 до 100 по сравнению с имеющимся (естественно распределение вероятности не равномерное, а например по обратной экспоненте). Или просто тупой запрос не 4, а 44 последующих версий. Другой крупный недостаток USK/SSK связан с алгоритмом обработки попыток повторной записи имеющейся версии SSK, когда конкретная версия указана. Узел при обнаружении того, что другая программа пытается записать SSK с уже имеющейся версией, сразу прерывает обаботку запроса и сообщает об этом программе. К сожалению, _ВСЕ_ программы при этом полагают, что информация уже имеется в сети, и при отсутствии новой информации ничего не предпринимают. В лучшем (но неоптимальном) случае они пытаются записать ту же информацию с новой версией SSK. Правильным поведением программ было бы запросить у узла имеющуюся версию SSK в полном объёме и проверить полноту и тождественность полученного с тем, чтобы исключить появление нечитаемых SSK. При ошибке получения данных необходимость перезаписи становится очевидной. К сожалению, даже если заранее известно что записываемые данные не изменились, программы вынуждены записывать новую версию SSK - иначе узел просто повторно прервёт обработку запроса. Вариантом решения может быть или выполнение узлом операции перезаписи имеющейся версии SSK до успешного завершения и лишь затем новый вариант ответного сообщения программе о том, что была успешно перезаписана имеющаяся версия. Или введение нового запроса, когда программа указывает узлу как поступать если версия уже есть: повторить запись (как в первом решении), проконтролировать идентичность (то есть узлу, а не программе запросить имеющуюся информацию и сравнить с поступившей) или просто проверить доступность имеющейся версии SSK, то есть попытаться прочитать SSK в полном объёме но без вывода и сохранения данных - только проверить что все данные в наличии (или по крайней мере сохранившихся блоков достаточно для полного восстановления). Это важно и для работы ARK, поскольку часто после перезагрузки узла нет необходимости менять версию ARK, но при этом необходимо регулярно проверить, что имеющаяся версия действительно доступна в сети. Иначе могут отключаться даже соседи узлов, непрерывно работающих на постоянном адесе: неизменный ARK такого узла с течением времени может выпасть из сети, но сам узел этого не заметит даже после перезагрузки - а вот его соседи, за время перезагрузки сменившие IP, не смогут получить этот ARK. == Translation == Using of USK for the implimentation of ARK has obvious downfalls. One of them is that during the rapid change of IP, for example during the change of the version of the node or during the repeated connection loss, number of ARK increases rapidly, and during this process there is no attempt to check if previous versions are still accessible; and they can fall out from the network, if almost instantaneously other nodes are restarting. As a result, as it seems, quite often breaks in the sequence of ARK appear with the length of more than 4 versions, which is a requirement for the working of normal USK; this leads to the search for the new ARK number giving no results. This is especially important for the nodes working less than 24 hours a day and having a dynamic IP. One solution may be a request for ARK far ahead, say a few times with the random increase of a version number from 5 to 100 related to the existing one (of course distributed not equally, but maybe as a reverse exponent). Or a dumb request for 44 rather than 4 following versions. Another bug problem of USK/SSK is related to the algorithm of attempting repeat write to the existing SSK, when a specific version is provided. Node after finding that another programme attempts to write SSK with the already existing version immediately interrupts the request and notifies the programme. Unfortunately _ALL_ the programmes after that assume that information is already on the network, and if no new information exists do nothing. In the
Re: [freenet-support] Freenet 0.7 build 1175
On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1175 is now available. Please upgrade. Changes: - Handle the Packet X sent Yms ago and still not acked bug better. Don't complain in the log until 10 minutes, then disconnect from the peer and log the fact. We can then reconnect, but we will do so cleanly, so hopefully not get it again for a while. It seems that most of the disruption caused by this bug was caused by the logging on every resend and not the bug itself... Of course we will need to fix the bug too. State Of The (My) 1175... It feels like it's running smoother, although it's cpu profile here hasn't changed substantially. Perhaps just a bit, due to better logging. The log files are finally usable! (Usually under 100K per hour now :) So, in one random 1 hour sample, here are the main ones that I get: 4 Forcing disconnect PacketSender ERRORs, both from opennet and darknet peers, because packets not acked after 10 minutes!. Does this mean that NO packets have been received from these peers, or just a big bunch of them? (I'm pretty sure my ISP doesn't kill connections, but just drops a fraction of the packets.) For some reason, these error messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) netPeerNode. 40 MessageCore ERRORs from RequestSender waitFor _unclaimed iteration took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit or from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize of 596 for matched: true 24 freenet.io.xfer.BlockTransmitter.sendAsync(), Terminated send -123413232423 ... as we haven't heard from receiver in 1m54s. 4 freenet.io.xferPacketThrottle, Blocktransmitter: Unable to send throttled message, waited 60100ms 6 freenet.io.comm.MessageCore Scheduled job ERRORS removeTimedOutFilters took 4000ms 4 freenet.node.KeyTracker PacketSender Packet 1234 sent over 600600ms ago and still not acked. (THEY STILL EXIST!?! ;) 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet and opennet), processing packet took 4000ms .. with times ranging from 3000ms to 6600ms. 8 freenet.node.FNPPacketMangler Message[1..4] timeout error: Processing packet for freenetnode.tld:1234 Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? (What happens, by the way, if a darknet peer does change his port, by the way--we'd have to re-add his node reference?) ___ 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] connecting
I thought that I had downloaded all the requirements for registering with Freenet . I was however stumped by the userid question and didn't fill it . I probably should have entered lorraine. Can you see this application and tell me how to retrieve it, or do I start over. Thank you for your assistance. I wish to disconnect from Cyberus. Is that the first thing to do...I didn't know how I could connect to Freenet without a server. Lorraine Martineau [EMAIL PROTECTED] I hope!!!___ 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] Former mail Can't open again is out of date. Need Friends.
Dear Supporters, the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some friends. But still I don't know how to operate it from the command line (bash or dash). Thanks. ___ 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] connecting
On Thursday 13 November 2008 22:47, Lorraine Martineau wrote: I thought that I had downloaded all the requirements for registering with Freenet . I was however stumped by the userid question and didn't fill it . I probably should have entered lorraine. Can you see this application and tell me how to retrieve it, or do I start over. Thank you for your assistance. I wish to disconnect from Cyberus. Is that the first thing to do...I didn't know how I could connect to Freenet without a server. Lorraine Martineau [EMAIL PROTECTED] I hope!!! I really think you've got the wrong Freenet here ... This mailing list is for http://freenetproject.org/ : a censorship resistant peer to peer network: == What is Freenet? Freenet is free software which lets you publish and obtain information on the Internet without fear of censorship. To achieve this freedom, the network is entirely decentralized and publishers and consumers of information are anonymous. Without anonymity there can never be true freedom of speech, and without decentralization the network will be vulnerable to attack. Communications by Freenet nodes are encrypted and are routed-through other nodes to make it extremely difficult to determine who is requesting the information and what its content is. Users contribute to the network by giving bandwidth and a portion of their hard drive (called the data store) for storing files. Unlike other peer-to-peer file sharing networks, Freenet does not let the user control what is stored in the data store. Instead, files are kept or deleted depending on how popular they are, with the least popular being discarded to make way for newer or more popular content. Files in the data store are encrypted to reduce the likelihood of prosecution by persons wishing to censor Freenet content. The network can be used in a number of different ways and isn't restricted to just sharing files like other peer-to-peer networks. It acts more like an Internet within an Internet. For example Freenet can be used for: * Publishing websites or 'freesites' * Communicating via message boards * Content distribution * Sending email messages Unlike many cutting edge projects, Freenet long ago escaped the science lab, it has been downloaded by over 2 million users since the project started, and it is used for the distribution of censored information all over the world including countries such as China and the Middle East. Ideas and concepts pioneered in Freenet have had a significant impact in the academic world. Our 2000 paper Freenet: A Distributed Anonymous Information Storage and Retrieval System was the most cited computer science paper of 2000 according to Citeseer, and Freenet has also inspired papers in the worlds of law and philosophy. Ian Clarke, Freenet's creator and project coordinator, was selected as one of the top 100 innovators of 2003 by MIT's Technology Review magazine. pgpq2AreoX2eW.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]
[freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)
Freenet 0.7 build 1178 is now available. Please upgrade. Sorry I accidentally released 1176, then had some bugfixes in 1177 and 1178. Anyway, the main changes relative to 1175: - Try to prevent both sides of a connection attempting to rekey at the same time, by having the receiver start 2.5 minutes early. This seems to have been the root cause of many of the recent problems. It may not be completely fixed, but should happen much less often. - When we disconnect from a peer because of it not acknowledging our packets, tell the user via a useralert as well as logging an error. - Get rid of WouldBlockException errors as well: If we cannot send a packet to a peer because there are too many packets in flight and none are being acknowledged, don't busy-loop and spam the logs, wait for it to become un-blocked again. If it doesn't become un-blocked in 10 minutes, log an error and tell the user via a useralert. - Change the default log rotation period to 10 minutes rather than 1 hour to save disk space. - Clarify the config option for packet padding: Turning off packet padding is BAD. Packet padding is essential against a passive attacker. In the next few days you may see the Probably a bug errors on the web interface. Hopefully once this build is mandatory (on Monday) these will go away. If you still see these from Tuesday onwards, let us know. Please update, and let us know how it works out. Hopefully this build will fix most of the recent network problems, oversized log files and high CPU usage when not doing anything. If you find any bugs, please report them on the bug tracker: https://bugs.freenetproject.org/ . Thanks. pgpREOBv5UTIk.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]
Re: [freenet-support] Wrapper does not start
On Friday 14 November 2008 01:09, [EMAIL PROTECTED] wrote: Since last update on 13.11. Freenet fails to start. I get the following Message in wrapper.log: You let freenet auto-update itself, or you used update.sh/update.cmd? If you let Freenet auto-update itself, then please send me your wrapper.log, as this is a serious bug we've been trying to gather more info on ... You can get your node back by running update.sh/update.cmd. STATUS | wrapper | 2008/11/14 02:01:01 | Launching a JVM... INFO | jvm 5| 2008/11/14 02:01:01 | java.lang.NoClassDefFoundError: freenet/node/NodeStarter INFO | jvm 5| 2008/11/14 02:01:01 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader$1.run(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 5| 2008/11/14 02:01:01 | at java.net.URLClassLoader.findClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClass(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | at java.lang.ClassLoader.loadClassInternal(Unknown Source) INFO | jvm 5| 2008/11/14 02:01:01 | Exception in thread main ERROR | wrapper | 2008/11/14 02:01:01 | JVM exited while loading the application. FATAL | wrapper | 2008/11/14 02:01:01 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2008/11/14 02:01:01 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2008/11/14 02:01:01 | -- Wrapper Stopped I already included wrapper.restart.delay=15 to wrapper.conf - but that only delays the hangup. My OS is WinXP pro SP3 ___ 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] pgpYX2x9tiQW0.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]
Re: [freenet-support] Freenet 0.7 build 1175
On Friday 14 November 2008 17:40, Dennis Nezic wrote: On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1175 is now available. Please upgrade. Changes: - Handle the Packet X sent Yms ago and still not acked bug better. Don't complain in the log until 10 minutes, then disconnect from the peer and log the fact. We can then reconnect, but we will do so cleanly, so hopefully not get it again for a while. It seems that most of the disruption caused by this bug was caused by the logging on every resend and not the bug itself... Of course we will need to fix the bug too. State Of The (My) 1175... It feels like it's running smoother, although it's cpu profile here hasn't changed substantially. Perhaps just a bit, due to better logging. The log files are finally usable! (Usually under 100K per hour now :) It still has 100% CPU most of the time then? Apparently resulting from Freenet itself rather than downloads etc? Try 1178 ... and then wait until say Wednesday ... hopefully once everyone has 1178, it will be much better. So, in one random 1 hour sample, here are the main ones that I get: 4 Forcing disconnect PacketSender ERRORs, both from opennet and darknet peers, because packets not acked after 10 minutes!. Does this mean that NO packets have been received from these peers, or just a big bunch of them? (I'm pretty sure my ISP doesn't kill connections, but just drops a fraction of the packets.) For some reason, these error messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) netPeerNode. This is caused by the bugs we're chasing at the moment. Hopefully next week it will have gone away, or be very rare. It means that we are still connected to the node, it's still sending us packets, but it apparently doesn't understand some of the packets we send it. 40 MessageCore ERRORs from RequestSender waitFor _unclaimed iteration took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit or from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize of 596 for matched: true 24 freenet.io.xfer.BlockTransmitter.sendAsync(), Terminated send -123413232423 ... as we haven't heard from receiver in 1m54s. 4 freenet.io.xferPacketThrottle, Blocktransmitter: Unable to send throttled message, waited 60100ms 6 freenet.io.comm.MessageCore Scheduled job ERRORS removeTimedOutFilters took 4000ms Hopefully these are related to the current bugs. If so they should greatly reduce. On the other hand, they may not be ... 4 freenet.node.KeyTracker PacketSender Packet 1234 sent over 600600ms ago and still not acked. (THEY STILL EXIST!?! ;) Yes, we log them at the same time as the disconnections. 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet and opennet), processing packet took 4000ms .. with times ranging from 3000ms to 6600ms. 8 freenet.node.FNPPacketMangler Message[1..4] timeout error: Processing packet for freenetnode.tld:1234 Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? It can be different, usually because of NATs, occasionally because you are connected both to the darknet and opennet nodes on that IP (which is a bug, shouldn't happen unless you have some wierd configs set). (What happens, by the way, if a darknet peer does change his port, by the way--we'd have to re-add his node reference?) Probably yes. pgpSwGcvJVVsB.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]
Re: [freenet-support] Freenet 0.7 build 1175
Please tell me, one way or the other, whether the problem is solved or whether Freenet continues to use lots of CPU etc etc. Thanks. On Friday 14 November 2008 19:52, Matthew Toseland wrote: On Friday 14 November 2008 17:40, Dennis Nezic wrote: On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1175 is now available. Please upgrade. Changes: - Handle the Packet X sent Yms ago and still not acked bug better. Don't complain in the log until 10 minutes, then disconnect from the peer and log the fact. We can then reconnect, but we will do so cleanly, so hopefully not get it again for a while. It seems that most of the disruption caused by this bug was caused by the logging on every resend and not the bug itself... Of course we will need to fix the bug too. State Of The (My) 1175... It feels like it's running smoother, although it's cpu profile here hasn't changed substantially. Perhaps just a bit, due to better logging. The log files are finally usable! (Usually under 100K per hour now :) It still has 100% CPU most of the time then? Apparently resulting from Freenet itself rather than downloads etc? Try 1178 ... and then wait until say Wednesday ... hopefully once everyone has 1178, it will be much better. So, in one random 1 hour sample, here are the main ones that I get: 4 Forcing disconnect PacketSender ERRORs, both from opennet and darknet peers, because packets not acked after 10 minutes!. Does this mean that NO packets have been received from these peers, or just a big bunch of them? (I'm pretty sure my ISP doesn't kill connections, but just drops a fraction of the packets.) For some reason, these error messages come in pairs, first by FNPPacketMangler, then by (Dark|Open) netPeerNode. This is caused by the bugs we're chasing at the moment. Hopefully next week it will have gone away, or be very rare. It means that we are still connected to the node, it's still sending us packets, but it apparently doesn't understand some of the packets we send it. 40 MessageCore ERRORs from RequestSender waitFor _unclaimed iteration took 3428ms with unclaimedFIFOSize of 533 for ret of packetTransmit or from UdpSocketHandler checkFilters took 6260ms with unclaimedFIFOSize of 596 for matched: true 24 freenet.io.xfer.BlockTransmitter.sendAsync(), Terminated send -123413232423 ... as we haven't heard from receiver in 1m54s. 4 freenet.io.xferPacketThrottle, Blocktransmitter: Unable to send throttled message, waited 60100ms 6 freenet.io.comm.MessageCore Scheduled job ERRORS removeTimedOutFilters took 4000ms Hopefully these are related to the current bugs. If so they should greatly reduce. On the other hand, they may not be ... 4 freenet.node.KeyTracker PacketSender Packet 1234 sent over 600600ms ago and still not acked. (THEY STILL EXIST!?! ;) Yes, we log them at the same time as the disconnections. 19 freenet.io.comm.UdpSocketHandler ERROR messages (from both darknet and opennet), processing packet took 4000ms .. with times ranging from 3000ms to 6600ms. 8 freenet.node.FNPPacketMangler Message[1..4] timeout error: Processing packet for freenetnode.tld:1234 Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? It can be different, usually because of NATs, occasionally because you are connected both to the darknet and opennet nodes on that IP (which is a bug, shouldn't happen unless you have some wierd configs set). (What happens, by the way, if a darknet peer does change his port, by the way--we'd have to re-add his node reference?) Probably yes. pgpJKAp7pRaAF.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]
Re: [freenet-support] Freenet 0.7 build 1175
On Fri, 14 Nov 2008 19:52:46 +, Matthew Toseland [EMAIL PROTECTED] wrote: It still has 100% CPU most of the time then? Apparently resulting from Freenet itself rather than downloads etc? Well, it's not /so/ serious that it stays at 100% all the time. It jumps up for a few minutes, then calms down to almost nothing for a few minutes. (The valleys are longer than the peaks.) And keeps repeating this. I'm running another process that steadily uses on average 25% of the (1.2GHz) cpu, and my 15minute load time is consistently around 3. Maybe the threads are all triggered to run at the same time, and should be staggered? Also, in this log, I have noticed that the port number, in the @ip:port@ portion of the error message does NOT match the port number listed on the /friends/ web page. Why is that? It can be different, usually because of NATs, occasionally because you are connected both to the darknet and opennet nodes on that IP (which is a bug, shouldn't happen unless you have some wierd configs set). Actually, the logs do say that I was connected to this same ip address both in opennet and darknet :|. (And the opennet port is properly listed in the strangers page. (It seems unlikely that his darknet port would be routed in a NAT, but not his opennet port :|.) ___ 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] Former mail Can't open again is out of date. Need Friends.
On Fri, 14 Nov 2008 14:56:25 + (GMT), Markus Hahn [EMAIL PROTECTED] wrote: Dear Supporters, the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some friends. But still I don't know how to operate it from the command line (bash or dash). Thanks. Out of curiosity, what kinds of things were you looking to do via the command line? There is, by the way, a telnet interface that lets you do quite a bit, which is disabled by default. There are also some command line tools that interface with freenet, such as pyFreenet, that might be useful, if they work :). ___ 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] Some downloads failing since updating to 1178
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Several downloads from my download queue failed to start after my node autoupgraded to 1178 (some *did* restart normally). Error messages (Reason column in the Failed downloads) in the web interface vary: Temporary files error: invalid stored block lengths Temporary files error: Corrupt GZIP trailer Temporary files error: invalid literal/length code Temporary files error: invalid distance code Temporary files error: invalid block type The node gives me two options: Remove and Restart. If I click on restart, the item fails almost immediately with the same error it had before. I've migrated to salted-hash store when 1175 went out. I tried restarting the node again and cleaning up ./tmp - not helped any. I have plenty of disk space. Log files don't seem to contain anything related to the issue I'm experiencing. Running on Windows XP x64 with Java 1.6.0_06, 64 bit. Regards, Victor Denisov. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHfU31O5++4rTuI0RAhAFAKDFwm8VLevPNMI3v/+ArCgrIkAs0wCgp7kX rcAT4OtPrWEnOiMuRGKSz68= =YYIA -END 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]
Re: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)
On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1178 is now available. Wow! What a difference. 1178 is like a totally different program, with respect to both cpu and memory usage. THANK YOU! It's no longer peaking for minutes at a time. It's consistently low. My 15minute load average is below 1 now! Hurray. Memory use also seems much lower. Regarding the not acked packets problem, I have alrady been alerted about 5 peers with severe problems, one of which is a darknet peer. 2 of the others are listed as CONNECTED. And the other 2 are listed as BACKED OFF. All of them are running 1178. Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED to me both in opennet and darknet. All in all, though, 1178 is a HUGE improvement! ___ 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] Freenet 0.7 build 1178 (and 1176, 1177)
On Friday 14 November 2008 23:21, Dennis Nezic wrote: On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1178 is now available. Wow! What a difference. 1178 is like a totally different program, with respect to both cpu and memory usage. THANK YOU! It's no longer peaking for minutes at a time. It's consistently low. My 15minute load average is below 1 now! Hurray. Memory use also seems much lower. Regarding the not acked packets problem, I have alrady been alerted about 5 peers with severe problems, one of which is a darknet peer. 2 of the others are listed as CONNECTED. And the other 2 are listed as BACKED OFF. All of them are running 1178. Also, I should repeat ;), One of my peers (ip addresses) is CONNECTED to me both in opennet and darknet. That's to be expected. We kill the connection, and purge the trackers etc, but we can reconnect afterwards. Also, it's quite possible that those peers were running an earlier version when they actually broke. However, it's also possible that we still have the underlying bug... I've not made much headway with finding it, next week we should know whether it's still active, since 1178 is mandatory on Sunday... All in all, though, 1178 is a HUGE improvement! pgpRpMyPP1lGK.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]
Re: [freenet-support] Some downloads failing since updating to 1178
Argh. Are these simple downloads ([EMAIL PROTECTED]/filename), or parts of freesites (mutliple slashes, maybe USKs)?? On Friday 14 November 2008 22:01, Victor Denisov wrote: Several downloads from my download queue failed to start after my node autoupgraded to 1178 (some *did* restart normally). Error messages (Reason column in the Failed downloads) in the web interface vary: Temporary files error: invalid stored block lengths Temporary files error: Corrupt GZIP trailer Temporary files error: invalid literal/length code Temporary files error: invalid distance code Temporary files error: invalid block type The node gives me two options: Remove and Restart. If I click on restart, the item fails almost immediately with the same error it had before. I've migrated to salted-hash store when 1175 went out. I tried restarting the node again and cleaning up ./tmp - not helped any. I have plenty of disk space. Log files don't seem to contain anything related to the issue I'm experiencing. Running on Windows XP x64 with Java 1.6.0_06, 64 bit. Regards, Victor Denisov. ___ 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] pgp0FdkmaBpXR.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]
Re: [freenet-support] Former mail Can't open again is out of date. Need Friends.
On Friday 14 November 2008 14:56, Markus Hahn wrote: Dear Supporters, the question I have sent to you some hours ago is obsolete. I have found the button to start it again. Freenet is running properly. Now I should try to find some friends. But still I don't know how to operate it from the command line (bash or dash). Thanks. Most basic functions of Freenet are controlled from the web interface (http://127.0.0.1:/). You might have to forward (ssh -L) port and 9481 to another machine, although in theory it should work with lynx/links. There are third party command line tools available for tasks such as inserting data... pgpP8AJk0SZB3.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]
Re: [freenet-support] ARKs USKs and SSKs (from Frost)
On Friday 14 November 2008 10:04, Volodya wrote: Somebody has asked me to send this (i will post the original in Russian and then the translation done by me) (please note that i don't really think that all of this makes sense, i'm an interpreter) == Translation == Using of USK for the implimentation of ARK has obvious downfalls. One of them is that during the rapid change of IP, for example during the change of the version of the node or during the repeated connection loss, number of ARK increases rapidly, and during this process there is no attempt to check if previous versions are still accessible; and they can fall out from the network, if almost instantaneously other nodes are restarting. As a result, as it seems, quite often breaks in the sequence of ARK appear with the length of more than 4 versions, which is a requirement for the working of normal USK; this leads to the search for the new ARK number giving no results. This is especially important for the nodes working less than 24 hours a day and having a dynamic IP. One solution may be a request for ARK far ahead, say a few times with the random increase of a version number from 5 to 100 related to the existing one (of course distributed not equally, but maybe as a reverse exponent). Or a dumb request for 44 rather than 4 following versions. IMHO this is a weakness in USKs themselves, rather than a specific issue for ARKs. Solutions have been proposed but not yet implemented. IIRC we do look further ahead, but we throttle it increasingly heavily, so it takes a long time. Another bug problem of USK/SSK is related to the algorithm of attempting repeat write to the existing SSK, when a specific version is provided. Node after finding that another programme attempts to write SSK with the already existing version immediately interrupts the request and notifies the programme. We attempt to find the data (via a USK fetcher). If it is already there and identical, we don't reinsert it. So it could be in the node's datastore and not on the network. Unfortunately _ALL_ the programmes after that assume that information is already on the network, and if no new information exists do nothing. In the best (but not optimal) case they attempt to write the same information to the new version of SSK. Correct behaviour of the programmes would be to ask the node for the existing version of SSK in full and check the completeness and correctness of the received, to exclude the existence of the unreadable SSK. In case of an problem with the fetch of the data the need for the reinsert becomes clear. Unfortunately even if one knows ahead of the time that the data has not changed, programmes are forced to write a new version of SSK, or the node will once again interrupt the request. One optional solution may be the node allowing the rewrite of the current version of SSK until it finishes successfully and only after letting the programme know that the write has been successful as a rewrite of the data. Or beginning of the new request when programme asks the node how to behave if the version already exists: repeat write (as the first solution), check the match (the node, not the programme, asks for the current version and compares)or only check the fetchability of the existing version of SSK (attempt to read SSK in the full but without providing the data or writing it anywhere) - only check the existence (or at least that there are enough blocks for full reconstruction). ARKs don't occupy lots of blocks. Having said that they do occupy one more block than necessary - for some reason we insert them with a text/plain mime type, they should be inserted with no MIME type. This is important also for the working of ARK, as often restart of the node is not a reason to reinsert the ARK version, but it is important that the existing version is still in the network. Otherwise even neighbours working constantly on the constant address: unchanged ARK of such a node can fall off the network, but the node itself will not notice that even after the restart; but the neighbours during the restart after changing IP will be unable to get that ARK. So basically, what you want is for the node to reinsert the ARK (at the old key) even if it is identical to the existing data. I dunno, maybe that's a good idea. It probably wouldn't get very far most of the time, because it would be terminated at the first node to have the data in its store... Anyone have a view? Other issues with ARKs and USKs: 1. ARKs are currently inserted with a MIME type, resulting in them occupying an SSK and a CHK. An SSK is all that is needed, and since I suspect we have overcapacity in SSKs, that should greatly improve ARKs' reliability. 2. It is hard to find the latest version of a USK when you've lost your place. IMHO the simplest, fastest, and most reliable solution to this is
Re: [freenet-support] Some downloads failing since updating to 1178
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Argh. Are these simple downloads ([EMAIL PROTECTED]/filename), or parts of freesites (mutliple slashes, maybe USKs)?? All simple CHKs, inserted with Frost (judging by the redirects). Regards, Victor Denisov. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHhUA1O5++4rTuI0RAuaSAKCknxRlhjs1GXrec8vXKCNpzNMo5ACdHk8U IZ3SQUslfl4EZprfUVpF6r0= =PMOs -END 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]
[freenet-support] (no subject)
2 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL PROTECTED] Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: My Node * Freenet 0.7 Build #1178 r23592M * Freenet-ext Build #24 r23199 ___ 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] Wrapper does not start
Matthew Toseland [EMAIL PROTECTED] schrieb: On Friday 14 November 2008 01:09, [EMAIL PROTECTED] wrote: Since last update on 13.11. Freenet fails to start. I get the following Message in wrapper.log: You let freenet auto-update itself, or you used update.sh/update.cmd? I used update.cmd If you let Freenet auto-update itself, then please send me your wrapper.log, as this is a serious bug we've been trying to gather more info on ... You can get your node back by running update.sh/update.cmd. I did it, but then the same error happens again. :( Is there no rollback for updates? ___ 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]
