[freenet-support] Freenet 0.7 build 1180 and freenet-ext.jar #25
Freenet 0.7 build 1180 is now available. Please upgrade. This build, and the associated freenet-ext.jar, fix two major bugs (in buckets and block padding) which we believe to be related to the recent download/browsing problems (bug 2694). 1180 is mandatory on Thursday. Note that one or two freesites may continue to have problems (temporary bucket errors etc). The problem was that we accidentally changed the algorithm for padding the last block in a splitfile for FEC decoding. This caused the whole download to fail whenever the last block was involved in a decode. We have changed the algorithm back, but some recently inserted files and freesites may be broken by the change back (rather than many older files and freesites). Please would site authors reinsert any recently inserted sites with 1180. We have had problems with freenet-ext.jar updates in the past, so please tell us if you have any problems updating; include your wrapper.log. 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/20081118/3603feaf/attachment.pgp>
[freenet-support] Sorry to have to report bad bug in 1180
On Tue, 18 Nov 2008 23:16:21 -0500 (GMT-05:00), vinyl1 wrote: > Node won't start. I did a full manual update with update.cmd, same > result. Java stack points to: java.lang.NoClassDefFoundError: > org/apache/tools/bzip2/CBZip2InputStream. Here is full output from > wrapper log: > > WARNING - The Wrapper jar file currently in use is version "3.3.1" > while the version of the Wrapper which launched this JVM is "3.2.3". That looks strange. > freenet.jar built with freenet-ext.jar Build #25 r23741 > > Initializing Node using Freenet Build #1180 r23746 and freenet-ext > Build #22 r22506 with Sun And that is simply wrong. freenet-ext (whatever that is) should be at #25 now.
[freenet-support] Sorry to have to report bad bug in 1180
Node won't start. I did a full manual update with update.cmd, same result. Java stack points to: java.lang.NoClassDefFoundError: org/apache/tools/bzip2/CBZip2InputStream. Here is full output from wrapper log: STATUS | wrapper | 2008/11/18 23:06:03 | --> Wrapper Started as Service STATUS | wrapper | 2008/11/18 23:06:03 | Launching a JVM... INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: Initializing... INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: WARNING - The Wrapper jar file currently in use is version "3.3.1" INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: while the version of the Wrapper which launched this JVM is INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: "3.2.3". INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: The Wrapper may appear to work correctly but some features may INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: not function correctly. This configuration has not been tested INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: and is not supported. INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: INFO | jvm 1| 2008/11/18 23:06:04 | freenet.jar built with freenet-ext.jar Build #25 r23741 INFO | jvm 1| 2008/11/18 23:06:05 | INFO | jvm 1| 2008/11/18 23:06:05 | Initializing Node using Freenet Build #1180 r23746 and freenet-ext Build #22 r22506 with Sun Microsystems Inc. JVM version 1.5.0_14 running on x86 Windows 2000 5.0 INFO | jvm 1| 2008/11/18 23:06:05 | Starting FProxy on 127.0.0.1,192.168.1.102: INFO | jvm 1| 2008/11/18 23:06:06 | INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO | jvm 1| 2008/11/18 23:06:06 | INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium4.dll' loaded from resource INFO | jvm 1| 2008/11/18 23:06:06 | FNP port created on 0.0.0.0:33991 INFO | jvm 1| 2008/11/18 23:06:07 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 1| 2008/11/18 23:06:07 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 1| 2008/11/18 23:06:07 | In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). INFO | jvm 1| 2008/11/18 23:06:07 | Created log files INFO | jvm 1| 2008/11/18 23:06:07 | Creating PeerManager INFO | jvm 1| 2008/11/18 23:06:07 | FNP port created on 0.0.0.0:47729 INFO | jvm 1| 2008/11/18 23:06:07 | Read 20 opennet peers from .\openpeers-47729 INFO | jvm 1| 2008/11/18 23:06:08 | Read 50 old-opennet-peers from .\openpeers-old-47729 INFO | jvm 1| 2008/11/18 23:06:08 | Starting database... INFO | jvm 1| 2008/11/18 23:06:13 | Initializing CHK Datastore (153444 keys) INFO | jvm 1| 2008/11/18 23:06:13 | Opening database using datastore\chk-33991.store INFO | jvm 1| 2008/11/18 23:06:13 | Opened main database for chk-store- INFO | jvm 1| 2008/11/18 23:06:13 | Opening secondary database: chk-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:13 | Opened secondary database: chk-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:13 | Opening secondary database: chk-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:13 | Opened secondary database: chk-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:13 | Keys in store: db 8875 file 8875 / max 153444 INFO | jvm 1| 2008/11/18 23:06:13 | Initializing CHK Datacache (153444:153444 keys) INFO | jvm 1| 2008/11/18 23:06:13 | Opening database using datastore\chk-33991.cache INFO | jvm 1| 2008/11/18 23:06:13 | Opened main database for chk-cache- INFO | jvm 1| 2008/11/18 23:06:20 | Opening secondary database: chk-cache-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:20 | Opened secondary database: chk-cache-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: chk-cache-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database: chk-cache-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Keys in store: db 153444 file 153444 / max 153444 INFO | jvm 1| 2008/11/18 23:06:21 | Initializing pubKey Datastore INFO | jvm 1| 2008/11/18 23:06:21 | Opening database using datastore\pubkey-33991.store INFO | jvm 1| 2008/11/18 23:06:21 | Opened main database for pubkey-store- INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: pubkey-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database: pubkey-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: pubkey-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database:
[freenet-support] Bad bug?
Probably a bug: please report: 4 peers forcibly disconnected due to not acknowledging packets. 4 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 support at freenetproject.org. 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: * 96.49.25.226:30753 * 71.14.187.17:37439 * 83.150.116.153:22807 * 90.184.228.80:37568 Freenet 0.7 Build #1180 r23746 Freenet-ext Build #25 r23741 -- Mel Charters -- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081118/c2561d7d/attachment.html>
[freenet-support] Version 1179?
Same for me, with 1179 I can retrieve the freesites like before... On Mon, Nov 17, 2008 at 21:04, Peter J. wrote: > On Monday 17 November 2008 20:55:25 bbackde at googlemail.com wrote: >> Another thing: anyone also noticed that starting with 1178 freesites >> like the Frost freesite or Toads blog are not longer retrievable? >> I get a temporary files error ... maybe this is already fixed with 1179. >> > > Yes had that also with 1178 but with 1179 these errors are gone. > > > ___ > 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 > -- __ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __
[freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
Thanks, I was not aware which snapshot version is which release version... Updated manually now. On Tue, Nov 18, 2008 at 13:45, Matthew Toseland wrote: > On Monday 17 November 2008 21:08, Dennis Nezic wrote: >> On Mon, 17 Nov 2008 21:59:20 +0100, bbackde at googlemail.com wrote: >> >> > Of course I'm not sure, I'm not even able to get 1179 ^^ >> >> You should be able to download the snapshot jar from >> http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and >> replace the one you're currently using. > > AFAIK 1179 doesn't do anything that could fix this. > > ___ > 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 > -- __ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __
[freenet-support] (no subject)
On Tuesday 18 November 2008 13.26.01 Luke771 wrote: > On Sat, 15 Nov 2008 23:42:11 + (GMT) > Markus Hahn wrote: > > > > > Sorry if I explain things that you know already, but I don't know what your > general competence level is, so I'll assume you know very little, just in > case (and it may be useful for someone else, too) > > > I am able to reach and open some of the sites I want to, but frequently I > > get the message that a site seems to be unreachable, sometimes concerning > > a site that opens some minutes later. > > This is expected on a newly estabilshed node. The first thing to do to get > a new node to work better is to set the max store size and max memory usage > (both in your config page at http://localhost:/config). > > But first lets talk about uptime quickly: Freenet needs to sun as much as ++ I like your answer, that's the way a lot more stuff of the internet should be explained (better more than less details), in order for ordinary people to learn. Thanks - *smile* (I am the author of www.minihowto.org, and I have tried to make documentation along your "lines" - it's not very easy?)
[freenet-support] (no subject)
On Sat, 15 Nov 2008 23:42:11 + (GMT) Markus Hahn wrote: Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) > I am able to reach and open some of the sites I want to, but frequently I get > the message that a site seems to be unreachable, sometimes concerning a site > that opens some minutes later. This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:/config). But first lets talk about uptime quickly: Freenet needs to sun as much as possible. The optimal would be to let it run 24/7, but morning to night every day is also fairly good. What you DON'T want to do is 'start freenet - visit freesite - shut down freenet'. It won't work. Freesites will take ages to load (when they do) and you'll be damaging the netwrotk. Let freenet run as much as your computer runs, and if you don't have an always-up box, consider letting your computer run just for the sake of freenet. the more Freenet stays up, the better your node will work, and themore it will help the network. Back to configuration; as we said, you should set store size and max memory usage to higher values than the defaults. You may have done that when you went through the Freenet First.time Wizard, but if you kept the defaults your store size and memory usage are very low because the defaults must work for everyone including users running on a junkware boxes in countries where they don't consider 700MhZ and 256MB RAM a low-end machine. The values are different according to your box and the usage you make of it, but the rule of is 'the more the better'. See how much HDD space you can dedicate to Freenet and set your store size to that; some have dedicated Freenet disks 500GB or 1TB in size, others have 250+ GB freenet stores, but 50GB is already fairly good. Remember than the bigger the store the better your node will work, because more stuff will be cached (encrypted) locally and will be fetched way more quickly when request it. As for max memory usage, you can set this even higher than can afford in theory, becuse freenet won't allocate all the memory you give to it. High max mem values are needed in my experience because mem usage will peak sometimes and if it tries to use more memory than it's allowed to use, the node may crash. Those who operate machnes with 3 or more GB of RAM are known to set max memory usage up to 2GB. My node runs on box that only has 1GB of RAM, Freenet is set to use max 770MB of it, and the node works pretty well. I used to run nodes on virtual machines with max memory usage set to 256MB and they worked pretty well as long as I didn't queue too many or too large files for download/upload; therefore, if you are limited by the physical memory installed on your box, (for instance you can't set max mem. usage to anything higher than 256 or even 128MB) you will have to run few downloads/uploads at a time (wait for them to complete, then add more). Remember it's not the number of files, it's the total size. Bandwidth usage settings are kind of relative. If you have a good connection (10MB+ high upload BW) you can set your bandwidth usage as high as your total bandwidth and freenet will never use but a fraction of that, but if your connection is medium-low, you'll need to limit freenet BW usage. In my experience trying to help new users get started, I've seen that the difference between upload and download bandwidth may be a problem. ISP' tout "high speed connections" without ever mentioning anything about upload bandwidth. As an example, a connection that the ISP refers to as '12Mbit/s' never does what the ISP says it should: first of all 12MB/s (1.5MB/s) is a nominal value, the actual bandwidth rarely exceeds 2/3 of the nominal value stated by ISP (more often half of it), and most importnat, the higghly publicized 12Mbit/s is only the download bandwidth. They never say anything about upload speed. If you're lucky you have 2Mbit/s but ,more often 1Mbit/s fot 'high speed' connections and 512 or 256 Kbit/s for medium range connections. So, the point is, find out what your -upload- stream in KB/s is (find out what your ISP say your upstream is, then divide by 8 to get bytes; ISP's always talk about bits). Decide how much bandwidth you can afford to give freenet in upload and set that value under max bandwidth usage in config page. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky that have high upload bandwidths (as high as download), you may want to set the same value for both upload and download. > I am totally new in this subject and all my real-world-friends are no-techies > and no-nerds, so I still
[freenet-support] Wrapper does not start
On Sunday 16 November 2008 18:12, freenet at chello.at wrote: > Since I updated to 1179, it works again. > No problems with up- and downloads or freesites. Good luck. AFAIK nothing changed in 1179 that could possibly have fixed that bug. Also some people are still getting it. -- 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/20081118/9bbbf299/attachment.pgp>
[freenet-support] (no subject)
ge. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky that have high upload bandwidths (as high as download), you may want to set the same value for both upload and download. > > > > I am totally new in this subject and all my real-world-friends are no-techies and no-nerds, so I still have no "firends" in the sense of trustworthy nodes to connect with or in the sense of darknet-members. Might this be the reason why some sites are closed for me? > > No. If you don't know anyone who runs Freenet, you just run Opennet (strangers) without adding anyone to your Daknet (friends). Freenet will work just as fine. > > > Should I try to manipulate the router in order to "forward" > > Yes you should. You can already access the router's web interface; now the point is how to configure a forward. > Interfaces are different for different routers but they're all pretty straightforward if you know what you need to do, and in your case what you need to do is: > > FORWARD: FROM: TO: FOR PROTOCOL: udp only > FORWARD: FROM: TO: FOR PROTOCOL: udp only > > yes, it's two ports, one for darknet (friends) and one for opennet (strangers). The port numbers of the ports you have to forwards are listed at the bottom of your Friends page, under 'ports used by the node', marked 'you may want to forward this port'. > > >or should I turn off the firewall? > > If for firewall you mean one of those annoying software firewalls that are so popular among windows users, that ask you whether to allow a program to connect and/or recieve connections, you want to allow Freenet to both connect to the internet and receive connections from the internet (some fiorewalls call the latter "act as a server") > > Observe that at least on some firewalls, you'll need to allow Java to make/recieve connections and not Freenet itself. (I think the executable that needs the permissions is javaw.exe but I'm not 100% sure, you may want to double check that) > > If you use the kind of firewall that simply open closes ports, you want to: > ALLOW , DIRECTION: both PROTOCOL: udp > > > Or is freenet running properly and the seemingly closed doors seem so due to the restrictions a newbie in darknet with a fresh node has to come around with? > > Freenet seems to be running fine. It should work even without port forwarding nut it would be -MUCH- better if you do configure the port forwarding. > > ___ > 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/20081118/4a69305b/attachment.pgp>
[freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
On Monday 17 November 2008 21:08, Dennis Nezic wrote: > On Mon, 17 Nov 2008 21:59:20 +0100, bbackde at googlemail.com wrote: > > > Of course I'm not sure, I'm not even able to get 1179 ^^ > > You should be able to download the snapshot jar from > http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and > replace the one you're currently using. AFAIK 1179 doesn't do anything that could fix this. -- 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/20081118/b2f286bc/attachment.pgp>
[freenet-support] Wrapper does not start
On Saturday 15 November 2008 01:12, freenet at chello.at wrote: > Matthew Toseland schrieb: > > 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? > > 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? Please try again. I apologise for the long turnaround. If it still doesn't work then send me a directory listing (ls -l / dir /w), a copy of wrapper.conf, and the output of the update script. 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/20081118/8f1b9841/attachment.pgp>
Re: [freenet-support] (no subject)
On Sat, 15 Nov 2008 23:42:11 + (GMT) Markus Hahn [EMAIL PROTECTED] wrote: snip Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:/config). But first lets talk about uptime quickly: Freenet needs to sun as much as possible. The optimal would be to let it run 24/7, but morning to night every day is also fairly good. What you DON'T want to do is 'start freenet - visit freesite - shut down freenet'. It won't work. Freesites will take ages to load (when they do) and you'll be damaging the netwrotk. Let freenet run as much as your computer runs, and if you don't have an always-up box, consider letting your computer run just for the sake of freenet. the more Freenet stays up, the better your node will work, and themore it will help the network. Back to configuration; as we said, you should set store size and max memory usage to higher values than the defaults. You may have done that when you went through the Freenet First.time Wizard, but if you kept the defaults your store size and memory usage are very low because the defaults must work for everyone including users running on a junkware boxes in countries where they don't consider 700MhZ and 256MB RAM a low-end machine. The values are different according to your box and the usage you make of it, but the rule of is 'the more the better'. See how much HDD space you can dedicate to Freenet and set your store size to that; some have dedicated Freenet disks 500GB or 1TB in size, others have 250+ GB freenet stores, but 50GB is already fairly good. Remember than the bigger the store the better your node will work, because more stuff will be cached (encrypted) locally and will be fetched way more quickly when request it. As for max memory usage, you can set this even higher than can afford in theory, becuse freenet won't allocate all the memory you give to it. High max mem values are needed in my experience because mem usage will peak sometimes and if it tries to use more memory than it's allowed to use, the node may crash. Those who operate machnes with 3 or more GB of RAM are known to set max memory usage up to 2GB. My node runs on box that only has 1GB of RAM, Freenet is set to use max 770MB of it, and the node works pretty well. I used to run nodes on virtual machines with max memory usage set to 256MB and they worked pretty well as long as I didn't queue too many or too large files for download/upload; therefore, if you are limited by the physical memory installed on your box, (for instance you can't set max mem. usage to anything higher than 256 or even 128MB) you will have to run few downloads/uploads at a time (wait for them to complete, then add more). Remember it's not the number of files, it's the total size. Bandwidth usage settings are kind of relative. If you have a good connection (10MB+ high upload BW) you can set your bandwidth usage as high as your total bandwidth and freenet will never use but a fraction of that, but if your connection is medium-low, you'll need to limit freenet BW usage. In my experience trying to help new users get started, I've seen that the difference between upload and download bandwidth may be a problem. ISP' tout high speed connections without ever mentioning anything about upload bandwidth. As an example, a connection that the ISP refers to as '12Mbit/s' never does what the ISP says it should: first of all 12MB/s (1.5MB/s) is a nominal value, the actual bandwidth rarely exceeds 2/3 of the nominal value stated by ISP (more often half of it), and most importnat, the higghly publicized 12Mbit/s is only the download bandwidth. They never say anything about upload speed. If you're lucky you have 2Mbit/s but ,more often 1Mbit/s fot 'high speed' connections and 512 or 256 Kbit/s for medium range connections. So, the point is, find out what your -upload- stream in KB/s is (find out what your ISP say your upstream is, then divide by 8 to get bytes; ISP's always talk about bits). Decide how much bandwidth you can afford to give freenet in upload and set that value under max bandwidth usage in config page. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky that have high upload bandwidths (as high as download), you may want to set the same value for both upload and download. I am totally new in this subject and all my real-world-friends are no-techies and no-nerds,
Re: [freenet-support] Wrapper does not start
On Saturday 15 November 2008 01:12, [EMAIL PROTECTED] wrote: 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? Please try again. I apologise for the long turnaround. If it still doesn't work then send me a directory listing (ls -l / dir /w), a copy of wrapper.conf, and the output of the update script. Thanks. pgpo9kmgXJp5M.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] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
On Monday 17 November 2008 21:08, Dennis Nezic wrote: On Mon, 17 Nov 2008 21:59:20 +0100, [EMAIL PROTECTED] wrote: Of course I'm not sure, I'm not even able to get 1179 ^^ You should be able to download the snapshot jar from http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and replace the one you're currently using. AFAIK 1179 doesn't do anything that could fix this. pgpKStgHArCca.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] (no subject)
Please, when replying to newbies, CC them, because they're often not subscribed to the list. I've bounced your message to the poster. On Tuesday 18 November 2008 12:26, Luke771 wrote: On Sat, 15 Nov 2008 23:42:11 + (GMT) Markus Hahn [EMAIL PROTECTED] wrote: snip Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:/config). But first lets talk about uptime quickly: Freenet needs to sun as much as possible. The optimal would be to let it run 24/7, but morning to night every day is also fairly good. What you DON'T want to do is 'start freenet - visit freesite - shut down freenet'. It won't work. Freesites will take ages to load (when they do) and you'll be damaging the netwrotk. Let freenet run as much as your computer runs, and if you don't have an always-up box, consider letting your computer run just for the sake of freenet. the more Freenet stays up, the better your node will work, and themore it will help the network. Back to configuration; as we said, you should set store size and max memory usage to higher values than the defaults. You may have done that when you went through the Freenet First.time Wizard, but if you kept the defaults your store size and memory usage are very low because the defaults must work for everyone including users running on a junkware boxes in countries where they don't consider 700MhZ and 256MB RAM a low-end machine. The values are different according to your box and the usage you make of it, but the rule of is 'the more the better'. See how much HDD space you can dedicate to Freenet and set your store size to that; some have dedicated Freenet disks 500GB or 1TB in size, others have 250+ GB freenet stores, but 50GB is already fairly good. Remember than the bigger the store the better your node will work, because more stuff will be cached (encrypted) locally and will be fetched way more quickly when request it. As for max memory usage, you can set this even higher than can afford in theory, becuse freenet won't allocate all the memory you give to it. High max mem values are needed in my experience because mem usage will peak sometimes and if it tries to use more memory than it's allowed to use, the node may crash. Those who operate machnes with 3 or more GB of RAM are known to set max memory usage up to 2GB. My node runs on box that only has 1GB of RAM, Freenet is set to use max 770MB of it, and the node works pretty well. I used to run nodes on virtual machines with max memory usage set to 256MB and they worked pretty well as long as I didn't queue too many or too large files for download/upload; therefore, if you are limited by the physical memory installed on your box, (for instance you can't set max mem. usage to anything higher than 256 or even 128MB) you will have to run few downloads/uploads at a time (wait for them to complete, then add more). Remember it's not the number of files, it's the total size. Bandwidth usage settings are kind of relative. If you have a good connection (10MB+ high upload BW) you can set your bandwidth usage as high as your total bandwidth and freenet will never use but a fraction of that, but if your connection is medium-low, you'll need to limit freenet BW usage. In my experience trying to help new users get started, I've seen that the difference between upload and download bandwidth may be a problem. ISP' tout high speed connections without ever mentioning anything about upload bandwidth. As an example, a connection that the ISP refers to as '12Mbit/s' never does what the ISP says it should: first of all 12MB/s (1.5MB/s) is a nominal value, the actual bandwidth rarely exceeds 2/3 of the nominal value stated by ISP (more often half of it), and most importnat, the higghly publicized 12Mbit/s is only the download bandwidth. They never say anything about upload speed. If you're lucky you have 2Mbit/s but ,more often 1Mbit/s fot 'high speed' connections and 512 or 256 Kbit/s for medium range connections. So, the point is, find out what your -upload- stream in KB/s is (find out what your ISP say your upstream is, then divide by 8 to get bytes; ISP's always talk about bits). Decide how much bandwidth you can afford to give freenet in upload and set that value under max bandwidth usage in config page. As for download bandwidth you may want to keep the defult -1, meaning 4x the upstream. If you are one of the few lucky
Re: [freenet-support] Wrapper does not start
On Sunday 16 November 2008 18:12, [EMAIL PROTECTED] wrote: Since I updated to 1179, it works again. No problems with up- and downloads or freesites. Good luck. AFAIK nothing changed in 1179 that could possibly have fixed that bug. Also some people are still getting it. pgpkrXNbwIzFN.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] (no subject)
On Tuesday 18 November 2008 13.26.01 Luke771 wrote: On Sat, 15 Nov 2008 23:42:11 + (GMT) Markus Hahn [EMAIL PROTECTED] wrote: snip Sorry if I explain things that you know already, but I don't know what your general competence level is, so I'll assume you know very little, just in case (and it may be useful for someone else, too) I am able to reach and open some of the sites I want to, but frequently I get the message that a site seems to be unreachable, sometimes concerning a site that opens some minutes later. This is expected on a newly estabilshed node. The first thing to do to get a new node to work better is to set the max store size and max memory usage (both in your config page at http://localhost:/config). But first lets talk about uptime quickly: Freenet needs to sun as much as ++ I like your answer, that's the way a lot more stuff of the internet should be explained (better more than less details), in order for ordinary people to learn. Thanks - *smile* (I am the author of www.minihowto.org, and I have tried to make documentation along your lines - it's not very easy?) ___ 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] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
Thanks, I was not aware which snapshot version is which release version... Updated manually now. On Tue, Nov 18, 2008 at 13:45, Matthew Toseland [EMAIL PROTECTED] wrote: On Monday 17 November 2008 21:08, Dennis Nezic wrote: On Mon, 17 Nov 2008 21:59:20 +0100, [EMAIL PROTECTED] wrote: Of course I'm not sure, I'm not even able to get 1179 ^^ You should be able to download the snapshot jar from http://downloads.freenetproject.org/alpha/ ... 1179 = r23606, and replace the one you're currently using. AFAIK 1179 doesn't do anything that could fix this. ___ 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] -- __ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __ ___ 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] Version 1179?
Same for me, with 1179 I can retrieve the freesites like before... On Mon, Nov 17, 2008 at 21:04, Peter J. [EMAIL PROTECTED] wrote: On Monday 17 November 2008 20:55:25 [EMAIL PROTECTED] wrote: Another thing: anyone also noticed that starting with 1178 freesites like the Frost freesite or Toads blog are not longer retrievable? I get a temporary files error ... maybe this is already fixed with 1179. Yes had that also with 1178 but with 1179 these errors are gone. snip ___ 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] -- __ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __ ___ 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 1180 and freenet-ext.jar #25
Freenet 0.7 build 1180 is now available. Please upgrade. This build, and the associated freenet-ext.jar, fix two major bugs (in buckets and block padding) which we believe to be related to the recent download/browsing problems (bug 2694). 1180 is mandatory on Thursday. Note that one or two freesites may continue to have problems (temporary bucket errors etc). The problem was that we accidentally changed the algorithm for padding the last block in a splitfile for FEC decoding. This caused the whole download to fail whenever the last block was involved in a decode. We have changed the algorithm back, but some recently inserted files and freesites may be broken by the change back (rather than many older files and freesites). Please would site authors reinsert any recently inserted sites with 1180. We have had problems with freenet-ext.jar updates in the past, so please tell us if you have any problems updating; include your wrapper.log. Thanks. pgpMh0ClabNFa.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] Sorry to have to report bad bug in 1180
Node won't start. I did a full manual update with update.cmd, same result. Java stack points to: java.lang.NoClassDefFoundError: org/apache/tools/bzip2/CBZip2InputStream. Here is full output from wrapper log: STATUS | wrapper | 2008/11/18 23:06:03 | -- Wrapper Started as Service STATUS | wrapper | 2008/11/18 23:06:03 | Launching a JVM... INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: Initializing... INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: WARNING - The Wrapper jar file currently in use is version 3.3.1 INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: while the version of the Wrapper which launched this JVM is INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: 3.2.3. INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: The Wrapper may appear to work correctly but some features may INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: not function correctly. This configuration has not been tested INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: and is not supported. INFO | jvm 1| 2008/11/18 23:06:04 | WrapperManager: INFO | jvm 1| 2008/11/18 23:06:04 | freenet.jar built with freenet-ext.jar Build #25 r23741 INFO | jvm 1| 2008/11/18 23:06:05 | INFO | jvm 1| 2008/11/18 23:06:05 | Initializing Node using Freenet Build #1180 r23746 and freenet-ext Build #22 r22506 with Sun Microsystems Inc. JVM version 1.5.0_14 running on x86 Windows 2000 5.0 INFO | jvm 1| 2008/11/18 23:06:05 | Starting FProxy on 127.0.0.1,192.168.1.102: INFO | jvm 1| 2008/11/18 23:06:06 | INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO | jvm 1| 2008/11/18 23:06:06 | INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium4.dll' loaded from resource INFO | jvm 1| 2008/11/18 23:06:06 | FNP port created on 0.0.0.0:33991 INFO | jvm 1| 2008/11/18 23:06:07 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 1| 2008/11/18 23:06:07 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 1| 2008/11/18 23:06:07 | In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). INFO | jvm 1| 2008/11/18 23:06:07 | Created log files INFO | jvm 1| 2008/11/18 23:06:07 | Creating PeerManager INFO | jvm 1| 2008/11/18 23:06:07 | FNP port created on 0.0.0.0:47729 INFO | jvm 1| 2008/11/18 23:06:07 | Read 20 opennet peers from .\openpeers-47729 INFO | jvm 1| 2008/11/18 23:06:08 | Read 50 old-opennet-peers from .\openpeers-old-47729 INFO | jvm 1| 2008/11/18 23:06:08 | Starting database... INFO | jvm 1| 2008/11/18 23:06:13 | Initializing CHK Datastore (153444 keys) INFO | jvm 1| 2008/11/18 23:06:13 | Opening database using datastore\chk-33991.store INFO | jvm 1| 2008/11/18 23:06:13 | Opened main database for chk-store- INFO | jvm 1| 2008/11/18 23:06:13 | Opening secondary database: chk-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:13 | Opened secondary database: chk-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:13 | Opening secondary database: chk-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:13 | Opened secondary database: chk-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:13 | Keys in store: db 8875 file 8875 / max 153444 INFO | jvm 1| 2008/11/18 23:06:13 | Initializing CHK Datacache (153444:153444 keys) INFO | jvm 1| 2008/11/18 23:06:13 | Opening database using datastore\chk-33991.cache INFO | jvm 1| 2008/11/18 23:06:13 | Opened main database for chk-cache- INFO | jvm 1| 2008/11/18 23:06:20 | Opening secondary database: chk-cache-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:20 | Opened secondary database: chk-cache-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: chk-cache-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database: chk-cache-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Keys in store: db 153444 file 153444 / max 153444 INFO | jvm 1| 2008/11/18 23:06:21 | Initializing pubKey Datastore INFO | jvm 1| 2008/11/18 23:06:21 | Opening database using datastore\pubkey-33991.store INFO | jvm 1| 2008/11/18 23:06:21 | Opened main database for pubkey-store- INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: pubkey-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database: pubkey-store-CHK_accessTime INFO | jvm 1| 2008/11/18 23:06:21 | Opening secondary database: pubkey-store-CHK_blockNum INFO | jvm 1| 2008/11/18 23:06:21 | Opened secondary database: pubkey-store-CHK_blockNum
Re: [freenet-support] Sorry to have to report bad bug in 1180
On Tue, 18 Nov 2008 23:16:21 -0500 (GMT-05:00), vinyl1 [EMAIL PROTECTED] wrote: Node won't start. I did a full manual update with update.cmd, same result. Java stack points to: java.lang.NoClassDefFoundError: org/apache/tools/bzip2/CBZip2InputStream. Here is full output from wrapper log: WARNING - The Wrapper jar file currently in use is version 3.3.1 while the version of the Wrapper which launched this JVM is 3.2.3. That looks strange. freenet.jar built with freenet-ext.jar Build #25 r23741 Initializing Node using Freenet Build #1180 r23746 and freenet-ext Build #22 r22506 with Sun And that is simply wrong. freenet-ext (whatever that is) should be at #25 now. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Bad bug?
Probably a bug: please report: 4 peers forcibly disconnected due to not acknowledging packets. 4 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: * 96.49.25.226:30753 * 71.14.187.17:37439 * 83.150.116.153:22807 * 90.184.228.80:37568 Freenet 0.7 Build #1180 r23746 Freenet-ext Build #25 r23741 -- Mel Charters___ 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]
