Re: [freenet-support] Error messages in wrapper log
Hi Dennis, Thanks. Between your answer and others, I think I have my questions answered. Please disregard my second e-mail. Mel On 2/8/2013 5:30 PM, Dennis Nezic wrote: Woops. I should have finished reading the original message. That corrupt database message is still odd though! On Fri, 8 Feb 2013 17:02:24 -0500, Dennis Nezic wrote: I assume you mean the "Database corrupted" message? I wonder how serious it is -- if freenet was able to recover from it. Can you download files? The generic answer to such database corruptions is to get rid of (or move) node.db4o*, which will also get rid of your download/upload queues. On Fri, 08 Feb 2013 07:52:28 -0600, Mel wrote: Hello, The newer versions of Freenet are giving errors that I am not sure are safe. I have checked some of the archives but could not find the exact answer. A portion of my wrapper log is below. This is on a Vista 32bit machine with all updates as far as I can tell. The main questions are the warning about the wrapper jar and JVM being different, and having only some level of anonymity. Thanks for your help. MW STATUS | wrapper | 2013/02/05 13:01:33 | --> Wrapper Started as Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service Wrapper Community Edition 32-bit 3.3.5 [...] ___ 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:support-requ...@freenetproject.org?subject=unsubscribe ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Error messages in wrapper log
Woops. I should have finished reading the original message. That corrupt database message is still odd though! On Fri, 8 Feb 2013 17:02:24 -0500, Dennis Nezic wrote: > I assume you mean the "Database corrupted" message? I wonder how > serious it is -- if freenet was able to recover from it. Can you > download files? > > The generic answer to such database corruptions is to get rid of (or > move) node.db4o*, which will also get rid of your download/upload > queues. > > On Fri, 08 Feb 2013 07:52:28 -0600, Mel wrote: > > Hello, > > > > The newer versions of Freenet are giving errors that I am not sure > > are safe. I have checked some of the archives but could not find the > > exact answer. A portion of my wrapper log is below. This is on a > > Vista 32bit machine with all updates as far as I can tell. The main > > questions are the warning about the wrapper jar and JVM being > > different, and having only some level of anonymity. > > > > Thanks for your help. > > > > MW > > > > STATUS | wrapper | 2013/02/05 13:01:33 | --> Wrapper Started as > > Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service > > Wrapper Community Edition 32-bit 3.3.5 [...] ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Error messages in wrapper log
On 02/08/2013 08:52 AM, Mel wrote: > Hello, > > The newer versions of Freenet are giving errors that I am not sure are > safe. I have checked some of the archives but could not find the exact > answer. A portion of my wrapper log is below. This is on a Vista 32bit > machine with all updates as far as I can tell. The main questions are > the warning about the wrapper jar and JVM being different, and having > only some level of anonymity. > > Thanks for your help. > > MW > > [snip] > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: WARNING - The > Wrapper jar file currently in use is version "3.3.1" > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: while the > version of the Wrapper which launched this JVM is > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: "3.3.5". > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: The Wrapper > may appear to work correctly but some features may > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: not function > correctly. This configuration has not been tested > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: and is not > supported. This is a known problem with Freenet's usage of the wrapper. I've lost track of what's holding up an upgrade at this point. > INFO | jvm 1| 2013/02/05 13:01:49 | Testnet mode DISABLED. You may > have some level of anonymity. :) > INFO | jvm 1| 2013/02/05 13:01:49 | Note that this version of > Freenet is still a very early alpha, and may well have numerous bugs and > design flaws. > INFO | jvm 1| 2013/02/05 13:01:49 | 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). This is the part you mention as "only some level of anonymity?" It's an inherent property of the network that if someone malicious is able to directly connect to your node they can get more information than you'd like by virtue of routing a large portion of one's requests. This is why darknet is better than opennet: if you know someone personally they're much less likely to be malicious than some arbitrary person your node automatically connects to as part of opennet. Does that answer your questions? Please let me know if that raises anything unclear or surprising. Steve signature.asc Description: OpenPGP digital signature ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Error messages in wrapper log
I assume you mean the "Database corrupted" message? I wonder how serious it is -- if freenet was able to recover from it. Can you download files? The generic answer to such database corruptions is to get rid of (or move) node.db4o*, which will also get rid of your download/upload queues. On Fri, 08 Feb 2013 07:52:28 -0600, Mel wrote: > Hello, > > The newer versions of Freenet are giving errors that I am not sure > are safe. I have checked some of the archives but could not find the > exact answer. A portion of my wrapper log is below. This is on a > Vista 32bit machine with all updates as far as I can tell. The main > questions are the warning about the wrapper jar and JVM being > different, and having only some level of anonymity. > > Thanks for your help. > > MW > > STATUS | wrapper | 2013/02/05 13:01:33 | --> Wrapper Started as > Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service > Wrapper Community Edition 32-bit 3.3.5 > STATUS | wrapper | 2013/02/05 13:01:33 | Copyright (C) 1999-2009 > Tanuki Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2013/02/05 13:01:33 | > http://wrapper.tanukisoftware.org STATUS | wrapper | 2013/02/05 > 13:01:33 | STATUS | wrapper | 2013/02/05 13:01:33 | Launching a > JVM... INFO | jvm 1| 2013/02/05 13:01:41 | WrapperManager: > Initializing... INFO | jvm 1| 2013/02/05 13:01:42 | > WrapperManager: WARNING - The Wrapper jar file currently in use is > version "3.3.1" INFO | jvm 1| 2013/02/05 13:01:42 | > WrapperManager: while the version of the Wrapper which launched this > JVM is INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: > "3.3.5". INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: > The Wrapper may appear to work correctly but some features may > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: not > function correctly. This configuration has not been tested > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: and is not > supported. > INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: > INFO | jvm 1| 2013/02/05 13:01:47 | freenet.jar built with > freenet-ext.jar Build #29 rv29 running with ext build 29 rv29 > INFO | jvm 1| 2013/02/05 13:01:47 | Creating config from > freenet.ini INFO | jvm 1| 2013/02/05 13:01:47 | Creating > logger... INFO | jvm 1| 2013/02/05 13:01:47 | Set interval to > 10 and multiplier to 1 > INFO | jvm 1| 2013/02/05 13:01:47 | Starting executor... > INFO | jvm 1| 2013/02/05 13:01:47 | Finding old log files. New > log file is > C:\Users\Mel\AppData\Local\Freenet\logs > \freenet-1432-2013-02-05-13.log.gz INFO | jvm 1| 2013/02/05 > 13:01:47 | Created log files INFO | jvm 1| 2013/02/05 13:01:47 > | Initializing Node using Freenet Build #1432 rbuild01432 and > | freenet-ext Build #29 rv29 with > Oracle Corporation JVM version 1.7.0_13 running on x86 Windows Vista > 6.0 INFO | jvm 1| 2013/02/05 13:01:47 | Set fproxy max length > to 2306867 and max length with progress to 5767168 = 5767168 > INFO | jvm 1| 2013/02/05 13:01:47 | Starting FProxy on > 127.0.0.1,0:0:0:0:0:0:0:1: > INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Native CPUID library > 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from > resource INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Optimized > native BigInteger library 'net/i2p/util/jbigi-windows-pentium3.dll' > loaded from resource > INFO | jvm 1| 2013/02/05 13:01:48 | SHA1: using SUN version 1.7 > INFO | jvm 1| 2013/02/05 13:01:48 | MD5: using SUN version 1.7 > INFO | jvm 1| 2013/02/05 13:01:48 | SHA-256: using SUN version > 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-384: using SUN > version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-512: using > SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:49 | Not > creating node.db4o for now, waiting for config as to security level... > INFO | jvm 1| 2013/02/05 13:01:49 | FNP port created on > 0.0.0.0:59903 INFO | jvm 1| 2013/02/05 13:01:49 | Testnet mode > DISABLED. You may have some level of anonymity. :) > INFO | jvm 1| 2013/02/05 13:01:49 | Note that this version of > Freenet is still a very early alpha, and may well have numerous bugs > and design flaws. > INFO | jvm 1| 2013/02/05 13:01:49 | 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| 2013/02/05 13:01:49 | Trying to read node > file backup ... > INFO | jvm 1| 2013/02/05 13:01:49 | Creating new cryptographic > keys... INFO | jvm 1| 2013/02/05 13:01:49 | Creating PeerManager > INFO | jvm 1| 2013/02/05 13:01:49 | No darknet peers file found. > INFO | jvm 1| 2013/02/05 13:01:49 | Memory is 494 MiB > (518979584 bytes) > INFO | jvm 1| 2013/02/05 13:01:49 | Setting standard 500 thread > limit. This should be enough for most no
[freenet-support] Error messages in wrapper log
Hello, The newer versions of Freenet are giving errors that I am not sure are safe. I have checked some of the archives but could not find the exact answer. A portion of my wrapper log is below. This is on a Vista 32bit machine with all updates as far as I can tell. The main questions are the warning about the wrapper jar and JVM being different, and having only some level of anonymity. Thanks for your help. MW STATUS | wrapper | 2013/02/05 13:01:33 | --> Wrapper Started as Console STATUS | wrapper | 2013/02/05 13:01:33 | Java Service Wrapper Community Edition 32-bit 3.3.5 STATUS | wrapper | 2013/02/05 13:01:33 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2013/02/05 13:01:33 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2013/02/05 13:01:33 | STATUS | wrapper | 2013/02/05 13:01:33 | Launching a JVM... INFO | jvm 1| 2013/02/05 13:01:41 | WrapperManager: Initializing... INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: WARNING - The Wrapper jar file currently in use is version "3.3.1" INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: while the version of the Wrapper which launched this JVM is INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: "3.3.5". INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: The Wrapper may appear to work correctly but some features may INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: not function correctly. This configuration has not been tested INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: and is not supported. INFO | jvm 1| 2013/02/05 13:01:42 | WrapperManager: INFO | jvm 1| 2013/02/05 13:01:47 | freenet.jar built with freenet-ext.jar Build #29 rv29 running with ext build 29 rv29 INFO | jvm 1| 2013/02/05 13:01:47 | Creating config from freenet.ini INFO | jvm 1| 2013/02/05 13:01:47 | Creating logger... INFO | jvm 1| 2013/02/05 13:01:47 | Set interval to 10 and multiplier to 1 INFO | jvm 1| 2013/02/05 13:01:47 | Starting executor... INFO | jvm 1| 2013/02/05 13:01:47 | Finding old log files. New log file is C:\Users\Mel\AppData\Local\Freenet\logs\freenet-1432-2013-02-05-13.log.gz INFO | jvm 1| 2013/02/05 13:01:47 | Created log files INFO | jvm 1| 2013/02/05 13:01:47 | Initializing Node using Freenet Build #1432 rbuild01432 and freenet-ext Build #29 rv29 with Oracle Corporation JVM version 1.7.0_13 running on x86 Windows Vista 6.0 INFO | jvm 1| 2013/02/05 13:01:47 | Set fproxy max length to 2306867 and max length with progress to 5767168 = 5767168 INFO | jvm 1| 2013/02/05 13:01:47 | Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO | jvm 1| 2013/02/05 13:01:48 | INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium3.dll' loaded from resource INFO | jvm 1| 2013/02/05 13:01:48 | SHA1: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | MD5: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-256: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-384: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:48 | SHA-512: using SUN version 1.7 INFO | jvm 1| 2013/02/05 13:01:49 | Not creating node.db4o for now, waiting for config as to security level... INFO | jvm 1| 2013/02/05 13:01:49 | FNP port created on 0.0.0.0:59903 INFO | jvm 1| 2013/02/05 13:01:49 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 1| 2013/02/05 13:01:49 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 1| 2013/02/05 13:01:49 | 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| 2013/02/05 13:01:49 | Trying to read node file backup ... INFO | jvm 1| 2013/02/05 13:01:49 | Creating new cryptographic keys... INFO | jvm 1| 2013/02/05 13:01:49 | Creating PeerManager INFO | jvm 1| 2013/02/05 13:01:49 | No darknet peers file found. INFO | jvm 1| 2013/02/05 13:01:49 | Memory is 494 MiB (518979584 bytes) INFO | jvm 1| 2013/02/05 13:01:49 | Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. INFO | jvm 1| 2013/02/05 13:01:49 | Database corrupted (before entering NodeClientCore)! INFO | jvm 1| 2013/02/05 13:01:49 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s INFO | jvm 1| 2013/02/05 13:01:49 | Initializing USK Manager ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support
