[freenet-support] Freenet 0.7 build 1173, 1172 and 1171
> On Sat, 8 Nov 2008 22:09:42 -0500, > Dennis Nezic wrote: > > In this last 2min test of mine, all of the errors came from my 1173 > opennet peers. Only one of them was listed as "BACKED OFF" (I > was/am connected to him for 4h49m)--the other two were (and still are) > "CONNECTED" (for 48m and 1h21m). They have varying overload > probability percentages, 14% 16% 42% respectively. They have varying > congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They > have varying RTT times, 263ms 138233ms 71006ms. They have varying > overloaded percentages, the "backed off" one was "99.8% > 7974/10800/AcceptedTimeout" but the other two were 3% and 28%, both > with 0/1/ForwardRejectedOverload. With just one of those opennet peers, who is still "CONNECTED", In those 2min I got about 5000 of these ERROR messages!... many times just under 200/s. 40% of my traffic with this peer is having to be resent. (according to the strangers stats page.)
[freenet-support] Freenet 0.7 build 1173, 1172 and 1171
> On Sun, 9 Nov 2008 00:22:11 +, > Matthew Toseland wrote: > > Freenet 0.7 build 1173 is now available. It is still using much more of (my 1.2GHz) cpu than I would like. It regularly hovers at 100% for a few minutes, then calms down, then repeats. And, probably not unrelated, it is still producing LOTS of PacketSender ERRORs in the freenet logfiles. (I am forced to disable logging, otherwise it could /easily/ grow out of control.) For example, just now I enabled logging for /less/ than 2 minutes, and it grew to over 2MB, *ENTIRELY* composed of freenet.node.KeyTracker, PacketSender thread, Packet bla sent over blams ago still not acked ERRORs. It has been brought up on IRC a number of times today, most notably by mkan--but I forget if a reason/solution was given. It may not be isp throttling as I originally guessed, since mkan lives in a different part of the world, and is experiencing the same thing--as I think many others are as well. In this last 2min test of mine, all of the errors came from my 1173 opennet peers. Only one of them was listed as "BACKED OFF" (I was/am connected to him for 4h49m)--the other two were (and still are) "CONNECTED" (for 48m and 1h21m). They have varying overload probability percentages, 14% 16% 42% respectively. They have varying congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They have varying RTT times, 263ms 138233ms 71006ms. They have varying overloaded percentages, the "backed off" one was "99.8% 7974/10800/AcceptedTimeout" but the other two were 3% and 28%, both with 0/1/ForwardRejectedOverload.
[freenet-support] Urgent: Do not run the wizard on 1170!
1170 will ask you to go through the wizard again. This is on the theory that most of our users are oldtimers and may not have set the security levels. DO NOT GO THROUGH THE WIZARD if your node is running 1170. Click on "I will configure the node manually". If you do go through the wizard, it will reset your datastore size and bandwidth limits to the defaults. :< On 1171, it will ask you what you want to set these settings to, with the default being the current value - but if your node updates to 1170 it may take a considerable time to update to 1171, so you may be running 1170 ... Sorry! (Yes it hurts me more than it hurts you...) -- 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/20081108/238041d2/attachment.pgp>
[freenet-support] Freenet 0.7 build 1170
Freenet 0.7 build 1170 is now available, please upgrade! There are many changes, built over the time since 1166 - the last 3 builds have been critical bugfixes only. The most important changes: - New compression formats: Files are compressed with gzip, bzip2 or lzma, whichever gives best compression. This should give a significant saving for many files, and the increased compression time is likely offset by the reduced insertion time. - New container format: Freesites are packed into tar files, rather than zip files. These tar files are then compressed as above. For HTML, plain text etc, if it fits into the container, we should expect a substantial gain (50% seems plausible) in the number of blocks needed to insert a site, and therefore how long it takes to fetch it; please reinsert your freesites. - Make sure the user goes through the first-time wizard - if they haven't, open it on connecting to fproxy. The purpose here is to avoid problems with newbies with unconfigured nodes because of various failures. If you have your settings exactly as you want them, please click on "I am not a newbie". - A new blue theme by Dieppe, and some minor fixes to the web interface. - Warn the user if their IP address is not detected and there are no IP detection plugins loaded. Also some minor fixes to IP detection. - Don't drop a plugin just because it didn't load this time, try it again on next startup unless the user tells us not to. Minor changes to plugin loading. - Fix a bug causing us to leak file handles (fd's). - Lots of bug fixes and internal refactoring. - And the usual translation updates. There has also been lots of work on the installer, the web site, the firefox profile, the UPnP plugin (which you should reload if you use it), the db4o branch, the Web of Trust and Freetalk (formerly FMS) plugins (which p0s has been working hard on for some time and will be ready for initial testing very soon), and jSite 0.6.2 is out (bombe). Credits (for the node/website/profile/UPnP): bombe dieppe j16sdiz luke771 nextgens smar toad tommy xor yongjhen Please let me know if you have any difficulty with the auto-update mechanism, and please report any bugs you find to 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/20081108/08116be5/attachment.pgp>
[freenet-support] Freenet 0.7 build 1169
> On Fri, 7 Nov 2008 17:02:55 +, > Matthew Toseland wrote: > > Would you mind trying a recent testing build? update.sh testing / > update.cmd testing ? The bugs in trunk have been largely fixed... Yes--things seem to be running a lot better as of r23371--the jvm hasn't hung yet after almost a day of uptime.
Re: [freenet-support] Freenet 0.7 build 1169
On Fri, 7 Nov 2008 17:02:55 +, Matthew Toseland [EMAIL PROTECTED] wrote: Would you mind trying a recent testing build? update.sh testing / update.cmd testing ? The bugs in trunk have been largely fixed... Yes--things seem to be running a lot better as of r23371--the jvm hasn't hung yet after almost a day of uptime. ___ 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 1170
Freenet 0.7 build 1170 is now available, please upgrade! There are many changes, built over the time since 1166 - the last 3 builds have been critical bugfixes only. The most important changes: - New compression formats: Files are compressed with gzip, bzip2 or lzma, whichever gives best compression. This should give a significant saving for many files, and the increased compression time is likely offset by the reduced insertion time. - New container format: Freesites are packed into tar files, rather than zip files. These tar files are then compressed as above. For HTML, plain text etc, if it fits into the container, we should expect a substantial gain (50% seems plausible) in the number of blocks needed to insert a site, and therefore how long it takes to fetch it; please reinsert your freesites. - Make sure the user goes through the first-time wizard - if they haven't, open it on connecting to fproxy. The purpose here is to avoid problems with newbies with unconfigured nodes because of various failures. If you have your settings exactly as you want them, please click on I am not a newbie. - A new blue theme by Dieppe, and some minor fixes to the web interface. - Warn the user if their IP address is not detected and there are no IP detection plugins loaded. Also some minor fixes to IP detection. - Don't drop a plugin just because it didn't load this time, try it again on next startup unless the user tells us not to. Minor changes to plugin loading. - Fix a bug causing us to leak file handles (fd's). - Lots of bug fixes and internal refactoring. - And the usual translation updates. There has also been lots of work on the installer, the web site, the firefox profile, the UPnP plugin (which you should reload if you use it), the db4o branch, the Web of Trust and Freetalk (formerly FMS) plugins (which p0s has been working hard on for some time and will be ready for initial testing very soon), and jSite 0.6.2 is out (bombe). Credits (for the node/website/profile/UPnP): bombe dieppe j16sdiz luke771 nextgens smar toad tommy xor yongjhen Please let me know if you have any difficulty with the auto-update mechanism, and please report any bugs you find to the bug tracker: https://bugs.freenetproject.org/ Thanks. pgpZKWtjj0Jt0.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] Urgent: Do not run the wizard on 1170!
1170 will ask you to go through the wizard again. This is on the theory that most of our users are oldtimers and may not have set the security levels. DO NOT GO THROUGH THE WIZARD if your node is running 1170. Click on I will configure the node manually. If you do go through the wizard, it will reset your datastore size and bandwidth limits to the defaults. : On 1171, it will ask you what you want to set these settings to, with the default being the current value - but if your node updates to 1170 it may take a considerable time to update to 1171, so you may be running 1170 ... Sorry! (Yes it hurts me more than it hurts you...) pgpWw7SmCNzAT.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 1173, 1172 and 1171
Freenet 0.7 build 1173 is now available. This build is self-mandatory i.e. it only talks to nodes running at least 1173. Freenet should be able to upgrade itself automatically using Update over Mandatory, pulling the data from nodes that are TOO NEW. If it doesn't, please upgrade manually using update.sh / update.cmd. We have had a node running build 1151 upgrade itself successfully via Update over Mandatory; but builds prior to 1173 had some serious bugs that would prevent a successful update until it was mandatory. So we made it mandatory immediately, so all nodes would update. This may cause some temporary network disruption, sorry folks... Also if you are running a node prior to 1165, upgrading to 1170 or later will automatically migrate your datastore to salted-hash. This is not intended, but we only started writing the store type to disk in 1165 (6 weeks ago). I apologise for the self-mandatory build, and for the 4 builds in a day. It was necessary because of a series of rather serious bugs. Most serious were the updating bugs fixed in 1173: 1171: - In1170, all users were forced to go through the first-time wizard again (or click on the I-am-not-a-newbie option). Partly this is to ensure that nodes get configured even if the user installs and then forgets about it, and comes back and finds it doesn't work. But this also affects existing nodes. The idea behind this was that most nodes on the network are probably old-timers who may not have set trust levels. Unfortunately, the wizard overwrites your bandwidth limits and datastore size, without telling you if it manages to autodetect them! In 1171, we ensure that if you use the wizard after having configured your node, it always shows the bandwidth and datastore selection pages, and defaults them to your current settings. 1172: - Don't force all users to go through the wizard. Only redirect to the wizard if it hasn't been visited before, AND the node has no peers and/or has opennet disabled. Hence it will be shown on a new node install that the user has forgotten about (which was the real concern), but not on most nodes. - Fix Update over Mandatory triggering instantly on seeing a new build on nodes that have been online for more than 3 hours. Unfortunately, fixing this greatly exacerbated the other updating bugs - the node would not update at all until a build was mandatory. - Fix a bug causing very small freesite and file inserts to be decompressed more than once and therefore fail. - Faster and simpler LZMA decompression (came up while debugging the above issue, greatly reduces the number of lines, simple copy/paste from third party code; low risk). 1173: - Major bugfix to Update over Mandatory (it was only working when the build was mandatory, and not falling back to it if Update over Freenet failed, which it was doing because of the next bug). - Major bugfix to Update over Freenet (the normal updating process, which is much less disruptive to the network than UOM). pgp2CC2Qd3Kou.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 1173, 1172 and 1171
On Sat, 8 Nov 2008 22:09:42 -0500, Dennis Nezic [EMAIL PROTECTED] wrote: In this last 2min test of mine, all of the errors came from my 1173 opennet peers. Only one of them was listed as BACKED OFF (I was/am connected to him for 4h49m)--the other two were (and still are) CONNECTED (for 48m and 1h21m). They have varying overload probability percentages, 14% 16% 42% respectively. They have varying congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They have varying RTT times, 263ms 138233ms 71006ms. They have varying overloaded percentages, the backed off one was 99.8% 7974/10800/AcceptedTimeout but the other two were 3% and 28%, both with 0/1/ForwardRejectedOverload. With just one of those opennet peers, who is still CONNECTED, In those 2min I got about 5000 of these ERROR messages!... many times just under 200/s. 40% of my traffic with this peer is having to be resent. (according to the strangers stats page.) ___ 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 1173, 1172 and 1171
On Sun, 9 Nov 2008 00:22:11 +, Matthew Toseland [EMAIL PROTECTED] wrote: Freenet 0.7 build 1173 is now available. It is still using much more of (my 1.2GHz) cpu than I would like. It regularly hovers at 100% for a few minutes, then calms down, then repeats. And, probably not unrelated, it is still producing LOTS of PacketSender ERRORs in the freenet logfiles. (I am forced to disable logging, otherwise it could /easily/ grow out of control.) For example, just now I enabled logging for /less/ than 2 minutes, and it grew to over 2MB, *ENTIRELY* composed of freenet.node.KeyTracker, PacketSender thread, Packet bla sent over blams ago still not acked ERRORs. It has been brought up on IRC a number of times today, most notably by mkan--but I forget if a reason/solution was given. It may not be isp throttling as I originally guessed, since mkan lives in a different part of the world, and is experiencing the same thing--as I think many others are as well. In this last 2min test of mine, all of the errors came from my 1173 opennet peers. Only one of them was listed as BACKED OFF (I was/am connected to him for 4h49m)--the other two were (and still are) CONNECTED (for 48m and 1h21m). They have varying overload probability percentages, 14% 16% 42% respectively. They have varying congestion control rates, 1MB/s 1MB/s 17Bytes/s respectively. They have varying RTT times, 263ms 138233ms 71006ms. They have varying overloaded percentages, the backed off one was 99.8% 7974/10800/AcceptedTimeout but the other two were 3% and 28%, both with 0/1/ForwardRejectedOverload. ___ 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]
