[freenet-support] Sorry to have to report bad bug in 1180
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 22, 2008 at 7:08 PM, Dennis Nezic wrote: > On Sat, 22 Nov 2008 16:54:58 +0100, guido > wrote: > >> Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: >> > >> > 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. >> >> I have got that exact same warning in my logs as well. It has been >> like this for quite some time. > > Well, first of all, all of freenet's dependencies, including this > wrapper utility, are bundled "conveniently" in freenet-ext.jar. So you > likely originally launched it with the "older" 3.2.3 wrapper, and later > one freenet-ext got updated. Restarting the wrapper should get rid of > this message, though I don't think it's anything serious, since my > installation is still using 3.2.3. Actually the installer installs 3.3.1 iirc, but we don't have a way currently to update old installs. I manually did mine. - -- I may disagree with what you have to say, but I shall defend, to the death, your right to say it. - Voltaire Those who would give up Liberty, to purchase temporary Safety, deserve neither Liberty nor Safety. - Ben Franklin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: http://getfiregpg.org iD8DBQFJKMXW4esu1mlKOs8RAocKAJ9pMtx2X9le/pAAxWaB3OL9sUSpbgCfRryk +B5hFfMBpIX6IkwaYjMRSoU= =QH4Y -END PGP SIGNATURE-
[freenet-support] Bug report
1 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: 24.80.101.100:16145 My node: Freenet 0.7 Build #1181 r23784 Freenet-ext Build #26 r23771 Hope this helps. -- Single? Chat with sexy singles in your area now. Click Here! http://tagline.hushmail.com/fc/u4MuRdD02Vyd5fLrWa8x5TbtidCV9vLzWQQuOVc30M8iFLKpzudc5/
[freenet-support] Sorry to have to report bad bug in 1180
On Sat, 22 Nov 2008 16:54:58 +0100, guido wrote: > Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: > > >> > 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. > > I have got that exact same warning in my logs as well. It has been > like this for quite some time. Well, first of all, all of freenet's dependencies, including this wrapper utility, are bundled "conveniently" in freenet-ext.jar. So you likely originally launched it with the "older" 3.2.3 wrapper, and later one freenet-ext got updated. Restarting the wrapper should get rid of this message, though I don't think it's anything serious, since my installation is still using 3.2.3.
[freenet-support] Sorry to have to report bad bug in 1180
Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: > >> > 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. I have got that exact same warning in my logs as well. It has been like this for quite some time. Guido -- | _ | ASCII Ribbon Campaign Against HTML Emails. | ( ) | | X | | / \ |
[freenet-support] New windows updater script, recent chaos
We have a new update.cmd (command line updater script for Windows). If your Windows-based node won't start, please run update.cmd (in the folder Freenet is installed in, from a command line), and hopefully it will resolve the problem. You will need to manually start Freenet after the update succeeds (e.g. via the Start Freenet command on the start menu), because it only restarts Freenet if it's not actually running. I'm sorry for the disruption, we've had a series of catastrophic bugs to deal with, some of which were long-standing but only became a problem recently due to other changes. Some of these resulted in downloading corrupted updates. Apart from that, we've had to make a series of changes to freenet-ext.jar, and unfortunately we only have partial support for updating it, this again resulted in nodes not starting up. We have now fixed update.cmd, so at least the last-resort manual update will work; most of the time automatic update will work, but unfortunately it is currently possible for the node to update the main jar but not the ext jar, and thus break; this will also be fixed soon. The actual data corruption bug has been fixed in 1181, a better fix will be in 1182, and a long-term solution to the underlying problems (with a back-compatible metadata change) hopefully in 1183. This is mostly my fault ... sorry. -- 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/20081122/8bb39cf8/attachment.pgp>
[freenet-support] 1180 - peers forcibly disconnected due to not acknowledging packets
On Thursday 20 November 2008 07:52, Adrian Tritschler wrote: > Has happened with 1178, 1179 and now 1180 Thanks. We do need to know whether this goes away ... we don't have a fix yet though. Keep watching the support list, when we think we've fixed it we will say so in a new build announcement. > > Probably a bug: please report: 1 peers forcibly disconnected due to not > acknowledging packets. > > 1 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: -- 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/20081122/ce26cf69/attachment.pgp>
[freenet-support] What to do via command line
On Saturday 22 November 2008 05:33, Markus Hahn wrote: > Dear Supporters, dear Dennis. > > On Fri Nov 14 20:50:36 UTC 2008Dennis Nezic asked me: > > > Out of curiosity, what kinds of things were you looking to do via thecommand line? > > Well, I'm using a quite old notebook with a harddisc of 30 GB in it and - more important - with a no more than 512 MB RAM drive. Since I've installed freenet there are two new processes running - as far as I may trust my task-manager program. One of them is called "wrapper-linux" (a name I also found in one of the files of freenet), the other one is some java process. Each of them is permanently consuming 30%-80% of my CPU power and of RAM memory, even at times when there is no established node on my system, I mean when I have not opened freenet yet and even when I am not at all online. > So to me it seems like freenet likes to slow down my computer but at the same time makes no use of that. The fact that freenet, when running, might be expensive for my system, is not what is bothering me. > I'd like to gain control over these two programs, i.e. I want to be able to start and stop them via the command line, especially in times when i am not running a node. (I cannot stay online with that old notebook, what surely would be the best for freenet, as I have to use it at different locations.) At the moment I always have to "kill" them odd programs via the task manager, not really knowing what I am actually doing and if this might lead to damages in the programs or to freenet. By the way this is quite annoying. > > Thanks for your help. You do not have to kill them. You can for example visit the web interface and click the Shutdown Freenet button at the bottom of the page. Another option is to shut down the service from the services box in control panel (where exactly this is depends on which version of Windows you are running). You should also be able to use the start menu items to start and/or shut down Freenet. You can disable the service from the services control panel page so that you start it manually. However I strongly recommend against this. Freenet should run continually, and the computer it is run on should run continually, and it should have continuous connectivity. Otherwise expect performance to be *VERY* poor. In other words, on a laptop which is only occasionally connected to the internet, and when it is usually via other people's firewalled wifi's, Freenet is *not* going to run well. I agree that this is a problem as a rapidly increasing proportion of the world's computers are in exactly this situation, but it's not something we can fix before approximately 0.10. -- 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/20081122/6b914435/attachment.pgp>
[freenet-support] Some downloads failing since updating to 1178
1181 should fix this. 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/20081122/1d129774/attachment.pgp>
[freenet-support] Broken freesites in #1178
On Sunday 16 November 2008 11:08, SmallSister development wrote: > Hello, > > I've noted that freesites that are recently updated (The Ultimate > FreeNet Index) appear broken. > My personal freesite (that was inserted with jSite after the > announcement of the "tar.gz" sites) shows the same problem. 1181 should fix this. > > Peter. -- 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/20081122/92db0c56/attachment.pgp>
[freenet-support] SEVERE Bug report: duplicate of ID 0002694: 1178 kills some downloads
On Monday 17 November 2008 20:33, Ulrich Koepping wrote: > I have the same problem as described in Bug ID 0002694, after updating to latest freenet version, downloads fail - this happened with multiple keys. > > Klicking on restart in downloads menu does result in the same error immediately : "Temporary files error: invalid block type". > > I deleted the persistent-temp-* directory, after that the setup wizzard showed up (?), and all downloads were reset. I re-requested the download keys, and for the keys that failed before, the download failed again with the same error. > > I have not had a successfull downlaod after the update. > > This is the FIRST sever bug in freenet after my use of it for quite a while now. Although beeing beta it worked so far all the time. Functionality is fundamentally impacted. > > In case you need more info, reply. 1181 should fix this. If your node is broken, update manually with update.sh / update.cmd. -- 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/20081122/a73511da/attachment.pgp>
[freenet-support] Sorry to have to report bad bug in 1180
On Wednesday 19 November 2008 09:29, Luke771 wrote: > On Tue, 18 Nov 2008 23:32:18 -0500 > Dennis Nezic wrote: > > > 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 > > W4M(tm) [Works Fore Me] > > Freenet 0.7 Build 1180 r23747 > Freenet-ext Build #25 r23741 > Sun Java 6 from repos > Ubuntu 8.10 x86 > > > > > And that is simply wrong. freenet-ext (whatever that is) should be at > > #25 now. > > That's most likely the problem. > To force the update script to download the latest jar, run update.cmd testing. > > HowTo: > - Open a Cmd shell (the 'DOS window') Start=>Run=>(type) cmd => hit enter > - In the cmd shell, type 'cd C:\Program Files\Freenet' (no quotes) and hit enter > - Now type 'update.cmd testing' (no quotes) - Hit enter > > This will update to the latest testing version. > After completing the update, run update.cmd again, but this time do it the regular way (no testing) and the node will be reverted back to latest stable version. > > You may want to run the testing version to help find bugs before they make it into the stable release, but if you don't feel like bug-hunting, revert to stable. > > (in case of problem, an unoffical you-shouldnt-do-that way to get the new freenet-ext is to download it off the freenet website and replace the old one manually (not recommended. In fact, I shouldnt even suggest it) Unfortunately, update.cmd doesn't download freenet-ext.jar. And UOM *does* download new versions of the main jar even when it doesn't have the required freenet-ext.jar. So the only way to fix your node is to download the freenet-ext.jar manually, as Luke suggests. Or wait for the new update.cmd, which should be out any minute now. Sorry, this will have cost us quite a few nodes... :< -- 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/20081122/53f92e44/attachment.pgp>
[freenet-support] What to do via command line
Dear Supporters, dear Dennis. On Fri Nov 14 20:50:36 UTC 2008Dennis Nezic asked me: > Out of curiosity, what kinds of things were you looking to do via thecommand > line? Well, I'm using a quite old notebook with a harddisc of 30 GB in it and - more important - with a no more than 512 MB RAM drive. Since I've installed freenet there are two new processes running - as far as I may trust my task-manager program. One of them is called "wrapper-linux" (a name I also found in one of the files of freenet), the other one is some java process. Each of them is permanently consuming 30%-80% of my CPU power and of RAM memory, even at times when there is no established node on my system, I mean when I have not opened freenet yet and even when I am not at all online. So to me it seems like freenet likes to slow down my computer but at the same time makes no use of that. The fact that freenet, when running, might be expensive for my system, is not what is bothering me. I'd like to gain control over these two programs, i.e. I want to be able to start and stop them via the command line, especially in times when i am not running a node. (I cannot stay online with that old notebook, what surely would be the best for freenet, as I have to use it at different locations.) At the moment I always have to "kill" them odd programs via the task manager, not really knowing what I am actually doing and if this might lead to damages in the programs or to freenet. By the way this is quite annoying. Thanks for your help. -- next part -- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081122/73a62452/attachment.html>
Re: [freenet-support] Sorry to have to report bad bug in 1180
On Wednesday 19 November 2008 09:29, Luke771 wrote: On Tue, 18 Nov 2008 23:32:18 -0500 Dennis Nezic [EMAIL PROTECTED] wrote: 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 W4M(tm) [Works Fore Me] Freenet 0.7 Build 1180 r23747 Freenet-ext Build #25 r23741 Sun Java 6 from repos Ubuntu 8.10 x86 And that is simply wrong. freenet-ext (whatever that is) should be at #25 now. That's most likely the problem. To force the update script to download the latest jar, run update.cmd testing. HowTo: - Open a Cmd shell (the 'DOS window') Start=Run=(type) cmd = hit enter - In the cmd shell, type 'cd C:\Program Files\Freenet' (no quotes) and hit enter - Now type 'update.cmd testing' (no quotes) - Hit enter This will update to the latest testing version. After completing the update, run update.cmd again, but this time do it the regular way (no testing) and the node will be reverted back to latest stable version. You may want to run the testing version to help find bugs before they make it into the stable release, but if you don't feel like bug-hunting, revert to stable. (in case of problem, an unoffical you-shouldnt-do-that way to get the new freenet-ext is to download it off the freenet website and replace the old one manually (not recommended. In fact, I shouldnt even suggest it) Unfortunately, update.cmd doesn't download freenet-ext.jar. And UOM *does* download new versions of the main jar even when it doesn't have the required freenet-ext.jar. So the only way to fix your node is to download the freenet-ext.jar manually, as Luke suggests. Or wait for the new update.cmd, which should be out any minute now. Sorry, this will have cost us quite a few nodes... : pgpCbgEUwG7G0.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 20:33, Ulrich Koepping wrote: I have the same problem as described in Bug ID 0002694, after updating to latest freenet version, downloads fail - this happened with multiple keys. Klicking on restart in downloads menu does result in the same error immediately : Temporary files error: invalid block type. I deleted the persistent-temp-* directory, after that the setup wizzard showed up (?), and all downloads were reset. I re-requested the download keys, and for the keys that failed before, the download failed again with the same error. I have not had a successfull downlaod after the update. This is the FIRST sever bug in freenet after my use of it for quite a while now. Although beeing beta it worked so far all the time. Functionality is fundamentally impacted. In case you need more info, reply. 1181 should fix this. If your node is broken, update manually with update.sh / update.cmd. pgpOM28uViBPw.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] Broken freesites in #1178
On Sunday 16 November 2008 11:08, SmallSister development wrote: Hello, I've noted that freesites that are recently updated (The Ultimate FreeNet Index) appear broken. My personal freesite (that was inserted with jSite after the announcement of the tar.gz sites) shows the same problem. 1181 should fix this. Peter. pgpUkRE99OAL8.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
1181 should fix this. 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] pgplBwj5Ud2Lt.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] 1180 - peers forcibly disconnected due to not acknowledging packets
Has happened with 1178, 1179 and now 1180 Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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: * 81.56.138.175:1268 ___ 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] What to do via command line
Dear Supporters, dear Dennis. On Fri Nov 14 20:50:36 UTC 2008Dennis Nezic asked me: Out of curiosity, what kinds of things were you looking to do via thecommand line? Well, I'm using a quite old notebook with a harddisc of 30 GB in it and - more important - with a no more than 512 MB RAM drive. Since I've installed freenet there are two new processes running - as far as I may trust my task-manager program. One of them is called wrapper-linux (a name I also found in one of the files of freenet), the other one is some java process. Each of them is permanently consuming 30%-80% of my CPU power and of RAM memory, even at times when there is no established node on my system, I mean when I have not opened freenet yet and even when I am not at all online. So to me it seems like freenet likes to slow down my computer but at the same time makes no use of that. The fact that freenet, when running, might be expensive for my system, is not what is bothering me. I'd like to gain control over these two programs, i.e. I want to be able to start and stop them via the command line, especially in times when i am not running a node. (I cannot stay online with that old notebook, what surely would be the best for freenet, as I have to use it at different locations.) At the moment I always have to kill them odd programs via the task manager, not really knowing what I am actually doing and if this might lead to damages in the programs or to freenet. By the way this is quite annoying. Thanks for your help. ___ 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] What to do via command line
On Saturday 22 November 2008 05:33, Markus Hahn wrote: Dear Supporters, dear Dennis. On Fri Nov 14 20:50:36 UTC 2008Dennis Nezic asked me: Out of curiosity, what kinds of things were you looking to do via thecommand line? Well, I'm using a quite old notebook with a harddisc of 30 GB in it and - more important - with a no more than 512 MB RAM drive. Since I've installed freenet there are two new processes running - as far as I may trust my task-manager program. One of them is called wrapper-linux (a name I also found in one of the files of freenet), the other one is some java process. Each of them is permanently consuming 30%-80% of my CPU power and of RAM memory, even at times when there is no established node on my system, I mean when I have not opened freenet yet and even when I am not at all online. So to me it seems like freenet likes to slow down my computer but at the same time makes no use of that. The fact that freenet, when running, might be expensive for my system, is not what is bothering me. I'd like to gain control over these two programs, i.e. I want to be able to start and stop them via the command line, especially in times when i am not running a node. (I cannot stay online with that old notebook, what surely would be the best for freenet, as I have to use it at different locations.) At the moment I always have to kill them odd programs via the task manager, not really knowing what I am actually doing and if this might lead to damages in the programs or to freenet. By the way this is quite annoying. Thanks for your help. You do not have to kill them. You can for example visit the web interface and click the Shutdown Freenet button at the bottom of the page. Another option is to shut down the service from the services box in control panel (where exactly this is depends on which version of Windows you are running). You should also be able to use the start menu items to start and/or shut down Freenet. You can disable the service from the services control panel page so that you start it manually. However I strongly recommend against this. Freenet should run continually, and the computer it is run on should run continually, and it should have continuous connectivity. Otherwise expect performance to be *VERY* poor. In other words, on a laptop which is only occasionally connected to the internet, and when it is usually via other people's firewalled wifi's, Freenet is *not* going to run well. I agree that this is a problem as a rapidly increasing proportion of the world's computers are in exactly this situation, but it's not something we can fix before approximately 0.10. pgpPagn52jFj1.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] 1180 - peers forcibly disconnected due to not acknowledging packets
On Thursday 20 November 2008 07:52, Adrian Tritschler wrote: Has happened with 1178, 1179 and now 1180 Thanks. We do need to know whether this goes away ... we don't have a fix yet though. Keep watching the support list, when we think we've fixed it we will say so in a new build announcement. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 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: pgpePXRsnMY0h.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] New windows updater script, recent chaos
We have a new update.cmd (command line updater script for Windows). If your Windows-based node won't start, please run update.cmd (in the folder Freenet is installed in, from a command line), and hopefully it will resolve the problem. You will need to manually start Freenet after the update succeeds (e.g. via the Start Freenet command on the start menu), because it only restarts Freenet if it's not actually running. I'm sorry for the disruption, we've had a series of catastrophic bugs to deal with, some of which were long-standing but only became a problem recently due to other changes. Some of these resulted in downloading corrupted updates. Apart from that, we've had to make a series of changes to freenet-ext.jar, and unfortunately we only have partial support for updating it, this again resulted in nodes not starting up. We have now fixed update.cmd, so at least the last-resort manual update will work; most of the time automatic update will work, but unfortunately it is currently possible for the node to update the main jar but not the ext jar, and thus break; this will also be fixed soon. The actual data corruption bug has been fixed in 1181, a better fix will be in 1182, and a long-term solution to the underlying problems (with a back-compatible metadata change) hopefully in 1183. This is mostly my fault ... sorry. pgpsmdqJIRv1x.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] Sorry to have to report bad bug in 1180
Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: 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. I have got that exact same warning in my logs as well. It has been like this for quite some time. Guido -- | _ | ASCII Ribbon Campaign Against HTML Emails. | ( ) | | X | | / \ | ___ 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] Sorry to have to report bad bug in 1180
On Sat, 22 Nov 2008 16:54:58 +0100, guido [EMAIL PROTECTED] wrote: Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: 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. I have got that exact same warning in my logs as well. It has been like this for quite some time. Well, first of all, all of freenet's dependencies, including this wrapper utility, are bundled conveniently in freenet-ext.jar. So you likely originally launched it with the older 3.2.3 wrapper, and later one freenet-ext got updated. Restarting the wrapper should get rid of this message, though I don't think it's anything serious, since my installation is still using 3.2.3. ___ 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] Sorry to have to report bad bug in 1180
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 22, 2008 at 7:08 PM, Dennis Nezic wrote: On Sat, 22 Nov 2008 16:54:58 +0100, guido wrote: Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic: 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. I have got that exact same warning in my logs as well. It has been like this for quite some time. Well, first of all, all of freenet's dependencies, including this wrapper utility, are bundled conveniently in freenet-ext.jar. So you likely originally launched it with the older 3.2.3 wrapper, and later one freenet-ext got updated. Restarting the wrapper should get rid of this message, though I don't think it's anything serious, since my installation is still using 3.2.3. Actually the installer installs 3.3.1 iirc, but we don't have a way currently to update old installs. I manually did mine. - -- I may disagree with what you have to say, but I shall defend, to the death, your right to say it. - Voltaire Those who would give up Liberty, to purchase temporary Safety, deserve neither Liberty nor Safety. - Ben Franklin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: http://getfiregpg.org iD8DBQFJKMXW4esu1mlKOs8RAocKAJ9pMtx2X9le/pAAxWaB3OL9sUSpbgCfRryk +B5hFfMBpIX6IkwaYjMRSoU= =QH4Y -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]
