Re: [freenet-support] BUG: Freenet does not respect size limit for datastore
Evan Daniel wrote: Persistent-temp is not part of the datastore, and is not expected to stay within the datastore size limit. It's used to hold data from partially completed downloads. In theory, it will only grow to be slightly larger than your total queue size. However, there appear to be some bugs that make it leak space slowly. If it grows beyond your total queue size rapidly, though, that's not something I've seen. I can live with some additional disk-space use for downloaded files in transit; if it cleans up after the downloads are complete. (I planned a few gigs for downloads I configured Freenet.) Yet, presistent-temp grew over the weeks to achieve 11 GB... with several wrapper-induced shutdowns of Freenet. (The db4o implementation for downloads can get pretty unresponsive at times.) But with 17GB datastore (15 GB configured) PLUS 11GB in persistent-temp Freenet eats the best part of a 30 GB partition... Reclaiming ~9GB in unused temp files would make quite a difference. ___ 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] BUG: Freenet does not respect size limit for datastore
Dennis Nezic wrote: On Thu, 24 Dec 2009 23:03:25 +0100, SmallSister development wrote: Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. Interesting. Come to think of it, I also run pretty low on free diskspace ... 99% disk usage (of over 1tb) not being uncommon ... although that should still leave several gigs free. But, it's also interesting that you didn't have to delete your node.db4o file to get rid of the Internal error. And the Internal error reappeared after Freenet filled up the partition again overnight. persistent-temp had grown to 11 GB, which is a significant chunk of a 30 GB partition. ___ 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
[freenet-support] BUG: Freenet does not respect size limit for datastore
I found that Freenet (Build #1239) happily expands the datastore over the configured size limit. (Disk space is the limit...) This leads to very interesting behaviour when the file system gets full and I would like your help to solve the following two issues: 1) Error message on all pages: The auto-updater may have been compromised! We have turned it off for now, please click for more details. The auto-updater has been disabled. This might be because of a local problem, such as running out of disk space, or the auto-updating system may have been compromised. The reason is: Permanent error fetching revocation (error inserting the revocation key?): FetchException:Temporary files error:null:-1:null:false:null:Failed to close binary blob stream: java.io.IOException: No space left on device. [Bug 2: there is no link to click on at all...] 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] ___ 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] BUG: Freenet does not respect size limit for datastore
Dennis Nezic wrote: On Thu, 24 Dec 2009 13:28:36 +0100, SmallSister development wrote: 2) Error message on the file sharing pages: Internal error Internal error Return to queue page. [The queue page gives this error message too] I have posted about this bug as far back as June 12th '09, with freenet version 1216 and probably earlier -- basically ever since the db40 thing was merged :P. Toad flippantly suggested it was my flaky hardware (raid 5 software array) or a bug in the db40 libraries. But the regularity of these errors (I still get them from time to time, and have to delete my node.db4o) makes me surmise otherwise. The error disappeared when I freed some disk space... And I got the data store shrunk by resizing it; it is at 40% use now. I'll clean out temp files and node.db4o once the downloads have completed. ___ 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] Privacy (Was: No subject)
VolodyA! V Anarhist wrote: This point has already been answered, but i feel that there is a point that can be made here by answering it again. When you fetch something from the regular internet, the request is easily traceable back to you. The warning that you see tells you that for that reason. The question is how did you get Freenet to run? If you have downloaded the installer from the official freenet site, or even if you have just visited the site without the use of Tor, somebody can potentially see that. It's the same with plug-ins. Anyhow, back to my original point. When you download plugin (or anything else Freenet-related) from the Web, you identify yourself as a user of Freenet. That (in and of itself) does not tell anybody exactly what you say on Freenet (although may identify how you say that... downloading Freemail says that you will be sending Freemail messages, downloading Frost says you will be a frost user, etc.) When you run Freenet, it will generate a specific pattern of network usage and it would not be too hard for an ISP to map a large part of the Freenet nodes if it has a few nodes on its network. (It is also possible to map the network by adding a monitoring node, no real privacy leak here for Opennet nodes.) Assume The Internet knows you are running a Freenet node. And your ISP (and relevant uplinks) are able to detect that you're running a Darknet node! ISPs should not know what you're reading over Freenet, but I would not be surprised if they could do traffic analysis and determine whether you're downloading or uploading large files. (Has someone tried and published before?) ___ 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] Remove all identifying content from posted files (especially audio)
VolodyA! V Anarhist wrote: Brian Mearns wrote: On Thu, Sep 10, 2009 at 6:54 AM, SmallSister development smallsis...@xs4all.nl wrote: Brian Mearns wrote: I understand the basic architecture of Freenet and how it protects contributors, but I'm concerned that the files themselves might contain identifying information about the source of the file. In particular, for audio files such as MP3, Ogg Vorbis, and Flac. Does anyone have any information on making sure there are no fingerprints left on these files when posting? There is no way to be certain. There could be a future algorithm piecing together just enough bits from a file to identify you. Word frequency analysis has been used to discern likely writers of a plain text file. Yes, you can avoid stupid mistakes by checking for known signatures and removing them, but that is something that would be different for different file types (ogg would be somewhat different from mp3; but doc and pdf require totally different approaches.) It would be useful to have tools that can identify and remove watermarks and Freenet would be a great place to publish them (with source code please!) Bugger, I didn't even think of steganographic watermarks (shame on me), I was thinking more in terms of meta data known to be stored with various file formats (like ID3 tags), but this seems to be more complicated than I expected. Thanks for the insight. For audio and video the best approach could be to take the streams and remux them into the same container type, then to copy only the metadata which the user knows about (for example some audio files have autogain settings, etc). You would still have a potential for watermarking, as Peter already pointed out, and these watermarks will become more and more common as Internet Music Shop software develops (this is not to assume that internet shops is the only source of watermarked audio, other groups can watermark a file, this is most dangerous in countries where freenet is illegal(*)). I have heard noticed that multiple rips of the same CD can produce different .wav files; some of the differences are caused by the CD-player firmware and some caused by scratches/defects on the CD. Add some compression artefacts of the mp3 encoder (subtle algorithm differences between implementations) and you're very likely able to identify each mp3 uniquely. Even re-encoding may be detectable. NOTE: this is all without explicitly inserting a watermark. Remuxing and detection and removal of steganographic watermarks is likely to bring you 95% of the way; which could be good enough. ___ 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] Remove all identifying content from posted files (especially audio)
Brian Mearns wrote: I understand the basic architecture of Freenet and how it protects contributors, but I'm concerned that the files themselves might contain identifying information about the source of the file. In particular, for audio files such as MP3, Ogg Vorbis, and Flac. Does anyone have any information on making sure there are no fingerprints left on these files when posting? There is no way to be certain. There could be a future algorithm piecing together just enough bits from a file to identify you. Word frequency analysis has been used to discern likely writers of a plain text file. Yes, you can avoid stupid mistakes by checking for known signatures and removing them, but that is something that would be different for different file types (ogg would be somewhat different from mp3; but doc and pdf require totally different approaches.) It would be useful to have tools that can identify and remove watermarks and Freenet would be a great place to publish them (with source code please!) Peter. ___ 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] Auto-update key blown according to 1 peer(s)!
theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. I got the message too (from another IP) and they told me that it wasn't serious... Peter. ___ 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
[freenet-support] Auto-update key blown according to 1 peer(s)!
One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. Is this serious, someone attempting a sick joke or a developer hitting some wrong keys on his keyboard? Peter. ___ 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
[freenet-support] How to remove an opennet peer?
Matthew Toseland wrote: >>>>> On Thu, 12 Feb 2009 11:45:29 +0100, SmallSister development wrote: >>>>>> I get the error message: >>>>>>> One or more of your node's peers have never connected in the two >>>>>>> weeks since they were added. Consider removing them since they are >>>>>>> marginally affecting performance (wasting packets talking to nodes >>>>>>> that aren't there). >>>>>> A quick investigation identified the culprit: an ipv6-only opnennet >>>>>> peer. How do I get it off the list? (I am perfectly willing to ignore >>>>>> it, it doesn't seem to do much harm.) >>>>>> >>>>>> Yes, my Linux boxen have ipv6 support, but that isn't configured nor >>>>>> routed. > > Look in the peers file. Find the reference, it will include all the IPs, not > just the IPv6 one. > > HOWEVER, the above message should NEVER result from an opennet peer. If it > does, THERE IS A BUG! Are you sure it's an opennet peer that is responsible? > A "NEVER CONNECTED" opennet peer should be purged within a few hours, if it > isn't I would like to know! I am 100% sure that it is an opennet peer. (I never added any friends.) Here is the record from "openpeers-37365" (it is the first record in the file): opennet=true identity=vO9Wzm7MyjbZfhX4WxYBG45Jl7IC6byGFRguKVJow~E location=-1.0 testnet=false lastGoodVersion=Fred,0.7,1.0,1198 version=Fred,0.7,1.0,1204 dsaPubKey.y=L7OcjtnIDSJv9K~Ej2KvCichx9ZaNG0c7RG1XkDNLJwx1HXAilapB3PtQ1vgl39nO2B3 5sPBgxmJwU8QcTKTr8p5g-S32ArRBHVImhqfjlnUCjdeLFQnNtuCfJo7otl7nfOTC4KEKk8U34Mj6SDI 5xE7waHELf4F3aT1gOUJVdwoANaOLAaxETwEbNJKRMi7tZT2pfkl~emHkMHSvXXAZLFnLPY~vI65z3hN fiBkPV9dCWv9etOpaSs73L1wZXbA9Bkspmvtw2LyEVf~wU094DVumruFKNftFvqgzN4IWeIxFjczvEn0 6RXYXHZP~M9VEiWc9tvuFkYrt0JRwh~vcA physical.udp=2001:0:4137:9e50:88b:1825:e788:476c:59863;67.60.47.203:59863;24.119 .184.147:59863 dsaGroup.g=UaRatnDByf0QvTlaaAXTMzn1Z15LDTXe-J~gOqXCv0zpz83CVngSkb--bVRuZ9R65OFg~ ATKcuw8VJJwn1~A9p5jRt2NPj2EM7bu72O85-mFdBhcav8WHJtTbXb4cxNzZaQkbPQUv~gEnuEeMTc80 KZVjilQ7wlTIM6GIY~ZJVHMKSIkEU87YBRtIt1R~BJcnaDAKBJv~oXv1PS-6iwQRFMynMEmipfpqDXBT kqaQ8ahiGWA41rY8d4jDhrzIgjvkzfxkkcCpFFOldwW8w8MEecUoRLuhKnY1sm8nnTjNlYLtc1Okeq-b a0mvwygSAf4wxovwY6n1Fuqt8yZe1PDVg dsaGroup.q=ALFDNoq81R9Y1kQNVBc5kzmk0VvvCWosXY5t9E9S1tN5 dsaGroup.p=AIYIrE9VNhM38qPjirGGT-PJjWZBHY0q-JxSYyDFQfZQeOhrx4SUpdc~SppnWD~UHymT7 WyX28eV3YjwkVyc~--H5Tc83hPjx8qQc7kQbrMb~CJy7QBX~YSocKGfioO-pwfRZEDDguYtOJBHPqeen VDErGsfHTCxDDKgL2hYM8Ynj8Kes0OcUzOIVhShFSGbOAjJKjeg82XNXmG1hhdh2tnv8M4jJQ9ViEj42 5Mrh6O9jXovfPmcdYIr3C~3waHXjQvPgUiK4N5Saf~FOri48fK-PmwFZFc-YSgI9o2-70nVybSnBXlM9 6QkzU6x4CYFUuZ7-B~je0ofeLdX7xhehuk ark.pubURI=SSK at Q02BG6Pyj~cjJul5cgrzJyK8W7NBA1w4veE4BIAIgJU,FPtOPsvGJCK82oQwhlaKn 71rRb0tVGFLRTdnSNqhUiU,AQACAAE/ark ark.number=17 auth.negTypes=2;4 metadata.routableConnectionCheckCount=103334 metadata.timeLastSuccess=0 metadata.neverConnected=true metadata.peerAddedTime=1233133161091 metadata.detected.udp=2001:0:4137:9e50:143d:1279:bcc3:d034:59863 End My freenet node is on a LAN, behind a NAT gateway. I have set forwarding rules for incoming freenet UDP packets on the gateway. The freenet node (64 bit Linux) has ipv6 support, but ipv6 is not configured. The gateway only knows about ipv4. One specific (potentially relevant) configuration I made to freenet on my box is to only advertise the external ipv4 address. "physical.udp=213.84.14.16:37365" Peter.
Re: [freenet-support] How to remove an opennet peer?
Matthew Toseland wrote: On Thu, 12 Feb 2009 11:45:29 +0100, SmallSister development wrote: I get the error message: One or more of your node's peers have never connected in the two weeks since they were added. Consider removing them since they are marginally affecting performance (wasting packets talking to nodes that aren't there). A quick investigation identified the culprit: an ipv6-only opnennet peer. How do I get it off the list? (I am perfectly willing to ignore it, it doesn't seem to do much harm.) Yes, my Linux boxen have ipv6 support, but that isn't configured nor routed. Look in the peers file. Find the reference, it will include all the IPs, not just the IPv6 one. HOWEVER, the above message should NEVER result from an opennet peer. If it does, THERE IS A BUG! Are you sure it's an opennet peer that is responsible? A NEVER CONNECTED opennet peer should be purged within a few hours, if it isn't I would like to know! I am 100% sure that it is an opennet peer. (I never added any friends.) Here is the record from openpeers-37365 (it is the first record in the file): opennet=true identity=vO9Wzm7MyjbZfhX4WxYBG45Jl7IC6byGFRguKVJow~E location=-1.0 testnet=false lastGoodVersion=Fred,0.7,1.0,1198 version=Fred,0.7,1.0,1204 dsaPubKey.y=L7OcjtnIDSJv9K~Ej2KvCichx9ZaNG0c7RG1XkDNLJwx1HXAilapB3PtQ1vgl39nO2B3 5sPBgxmJwU8QcTKTr8p5g-S32ArRBHVImhqfjlnUCjdeLFQnNtuCfJo7otl7nfOTC4KEKk8U34Mj6SDI 5xE7waHELf4F3aT1gOUJVdwoANaOLAaxETwEbNJKRMi7tZT2pfkl~emHkMHSvXXAZLFnLPY~vI65z3hN fiBkPV9dCWv9etOpaSs73L1wZXbA9Bkspmvtw2LyEVf~wU094DVumruFKNftFvqgzN4IWeIxFjczvEn0 6RXYXHZP~M9VEiWc9tvuFkYrt0JRwh~vcA physical.udp=2001:0:4137:9e50:88b:1825:e788:476c:59863;67.60.47.203:59863;24.119 .184.147:59863 dsaGroup.g=UaRatnDByf0QvTlaaAXTMzn1Z15LDTXe-J~gOqXCv0zpz83CVngSkb--bVRuZ9R65OFg~ ATKcuw8VJJwn1~A9p5jRt2NPj2EM7bu72O85-mFdBhcav8WHJtTbXb4cxNzZaQkbPQUv~gEnuEeMTc80 KZVjilQ7wlTIM6GIY~ZJVHMKSIkEU87YBRtIt1R~BJcnaDAKBJv~oXv1PS-6iwQRFMynMEmipfpqDXBT kqaQ8ahiGWA41rY8d4jDhrzIgjvkzfxkkcCpFFOldwW8w8MEecUoRLuhKnY1sm8nnTjNlYLtc1Okeq-b a0mvwygSAf4wxovwY6n1Fuqt8yZe1PDVg dsaGroup.q=ALFDNoq81R9Y1kQNVBc5kzmk0VvvCWosXY5t9E9S1tN5 dsaGroup.p=AIYIrE9VNhM38qPjirGGT-PJjWZBHY0q-JxSYyDFQfZQeOhrx4SUpdc~SppnWD~UHymT7 WyX28eV3YjwkVyc~--H5Tc83hPjx8qQc7kQbrMb~CJy7QBX~YSocKGfioO-pwfRZEDDguYtOJBHPqeen VDErGsfHTCxDDKgL2hYM8Ynj8Kes0OcUzOIVhShFSGbOAjJKjeg82XNXmG1hhdh2tnv8M4jJQ9ViEj42 5Mrh6O9jXovfPmcdYIr3C~3waHXjQvPgUiK4N5Saf~FOri48fK-PmwFZFc-YSgI9o2-70nVybSnBXlM9 6QkzU6x4CYFUuZ7-B~je0ofeLdX7xhehuk ark.puburi=...@q02bg6pyj~cjjul5cgrzjyk8w7nba1w4vee4biaigju,FPtOPsvGJCK82oQwhlaKn 71rRb0tVGFLRTdnSNqhUiU,AQACAAE/ark ark.number=17 auth.negTypes=2;4 metadata.routableConnectionCheckCount=103334 metadata.timeLastSuccess=0 metadata.neverConnected=true metadata.peerAddedTime=1233133161091 metadata.detected.udp=2001:0:4137:9e50:143d:1279:bcc3:d034:59863 End My freenet node is on a LAN, behind a NAT gateway. I have set forwarding rules for incoming freenet UDP packets on the gateway. The freenet node (64 bit Linux) has ipv6 support, but ipv6 is not configured. The gateway only knows about ipv4. One specific (potentially relevant) configuration I made to freenet on my box is to only advertise the external ipv4 address. physical.udp=213.84.14.16:37365 Peter. ___ 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
[freenet-support] How to remove an opennet peer?
Luke771 wrote: > On Thu, 12 Feb 2009 09:42:46 -0500 > Dennis Nezic wrote: > >> On Thu, 12 Feb 2009 11:45:29 +0100, SmallSister development wrote: >>> I get the error message: >>>> One or more of your node's peers have never connected in the two >>>> weeks since they were added. Consider removing them since they are >>>> marginally affecting performance (wasting packets talking to nodes >>>> that aren't there). >>> A quick investigation identified the culprit: an ipv6-only opnennet >>> peer. How do I get it off the list? (I am perfectly willing to ignore >>> it, it doesn't seem to do much harm.) >>> >>> Yes, my Linux boxen have ipv6 support, but that isn't configured nor >>> routed. >> An iptables DROP rule to filter that ip address? :b > > Edit openpeers-<port#> and delete the culprit. > You may need to add a firewall rule to prevent the same IP from being re-added > (stop freenet, edit file, add firewall rule, start freenet) > Can you tell me what ipv4 address to block? The ipv6 address that the peer advertises is not routed.
[freenet-support] How to remove an opennet peer?
I get the error message: > One or more of your node's peers have never connected in the two > weeks since they were added. Consider removing them since they are > marginally affecting performance (wasting packets talking to nodes > that aren't there). A quick investigation identified the culprit: an ipv6-only opnennet peer. How do I get it off the list? (I am perfectly willing to ignore it, it doesn't seem to do much harm.) Yes, my Linux boxen have ipv6 support, but that isn't configured nor routed. Peter.
[freenet-support] How to remove an opennet peer?
I get the error message: One or more of your node's peers have never connected in the two weeks since they were added. Consider removing them since they are marginally affecting performance (wasting packets talking to nodes that aren't there). A quick investigation identified the culprit: an ipv6-only opnennet peer. How do I get it off the list? (I am perfectly willing to ignore it, it doesn't seem to do much harm.) Yes, my Linux boxen have ipv6 support, but that isn't configured nor routed. Peter. ___ 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] How to remove an opennet peer?
Luke771 wrote: On Thu, 12 Feb 2009 09:42:46 -0500 Dennis Nezic denn...@dennisn.dyndns.org wrote: On Thu, 12 Feb 2009 11:45:29 +0100, SmallSister development wrote: I get the error message: One or more of your node's peers have never connected in the two weeks since they were added. Consider removing them since they are marginally affecting performance (wasting packets talking to nodes that aren't there). A quick investigation identified the culprit: an ipv6-only opnennet peer. How do I get it off the list? (I am perfectly willing to ignore it, it doesn't seem to do much harm.) Yes, my Linux boxen have ipv6 support, but that isn't configured nor routed. An iptables DROP rule to filter that ip address? :b Edit openpeers-port# and delete the culprit. You may need to add a firewall rule to prevent the same IP from being re-added (stop freenet, edit file, add firewall rule, start freenet) Can you tell me what ipv4 address to block? The ipv6 address that the peer advertises is not routed. ___ 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
[freenet-support] What did you do to the Update Now button in 1195?
Apparently build 1196 has been pushed out; the common A new stable version of Freenet is available message box has appeared on the message list. Unfortunately the Update Now button in the box only brings me to the proxy home page and does not seem to do anything but bringing me to the freenet proxy home page. Peter. I have to try the update.sh trick... will do soon ___ 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] What did you do to the Update Now button in 1195?
For me the manual ugrade with update.sh went smoothly and I am fully connected (20 strangers) again on build 1196. Are you sure you are on build 1196? (One or two peers would suggest that you are still running build 1195.) Peter. Niels Egberts wrote: Mine would not auto-upgrade either (I waited for about 15 minutes, 1195 downloaded within a few minutes). Then I ran update.sh, which went without trouble execpt for the fact that the node did not restart by itself, I had to kill it. Now I'm connected to 1 opennet peer. On Tue, Jan 13, 2009 at 9:48 AM, SmallSister development smallsis...@xs4all.nl wrote: Apparently build 1196 has been pushed out; the common A new stable version of Freenet is available message box has appeared on the message list. Unfortunately the Update Now button in the box only brings me to the proxy home page and does not seem to do anything but bringing me to the freenet proxy home page. Peter. I have to try the update.sh trick... will do soon ___ 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
[freenet-support] Freenet 0.7 build 1194
Matthew Toseland wrote: > Freenet 0.7 build 1194 is now available. Please upgrade, this will be > mandatory on Friday. Some fairly substantial changes: It looks like the infamous "# peers forcibly disconnected" bug is gone in this release, thanks and congratulations! (I see far less package handling related messages in the logfiles.) While I'm at it: Merry Christmas and a Happy New Year! Peter.
Re: [freenet-support] Freenet 0.7 build 1194
Matthew Toseland wrote: Freenet 0.7 build 1194 is now available. Please upgrade, this will be mandatory on Friday. Some fairly substantial changes: It looks like the infamous # peers forcibly disconnected bug is gone in this release, thanks and congratulations! (I see far less package handling related messages in the logfiles.) While I'm at it: Merry Christmas and a Happy New Year! Peter. ___ 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
[freenet-support] Probably a bug
Sorry Matthew, within an hour of restarting my node I got my first disconnect. I am running 1188, and it seems all peers are running that same version. I got several copies of this error message in my logs: Dec 06, 2008 10:48:30:870 (freenet.node.PacketTracker, UdpSocketHandler for port 37365(2), NORMAL): Asking me to resend packet 74030 which we haven't sent yet or which they have already acked (next=74080) would that be related? Peter. Matthew Toseland wrote: > Thanks for your bug report. 1188 should fix this, but only after > Saturday morning. Please wait until Saturday, then restart your node, > and then let us know if you get this message again. Thanks. > > On Thursday 04 December 2008 02:38, IG wrote: >> Probably a bug: please report: 9 peers forcibly disconnected due to >> not acknowledging packets. 9 of your peers are having severe >> problems (not acknowledging packets even after 10 minutes).
Re: [freenet-support] Probably a bug
Sorry Matthew, within an hour of restarting my node I got my first disconnect. I am running 1188, and it seems all peers are running that same version. I got several copies of this error message in my logs: Dec 06, 2008 10:48:30:870 (freenet.node.PacketTracker, UdpSocketHandler for port 37365(2), NORMAL): Asking me to resend packet 74030 which we haven't sent yet or which they have already acked (next=74080) would that be related? Peter. Matthew Toseland wrote: Thanks for your bug report. 1188 should fix this, but only after Saturday morning. Please wait until Saturday, then restart your node, and then let us know if you get this message again. Thanks. On Thursday 04 December 2008 02:38, IG wrote: Probably a bug: please report: 9 peers forcibly disconnected due to not acknowledging packets. 9 of your peers are having severe problems (not acknowledging packets even after 10 minutes). ___ 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] A 1180 non-starter
Freenet 1180 refuses to start; here is an extract from the wrapper.log file: STATUS | wrapper | 2008/11/19 10:06:54 | Launching a JVM... ERROR | wrapper | 2008/11/19 10:06:54 | JVM exited while loading the application. INFO | jvm 5| 2008/11/19 10:06:54 | Exception in thread "main" java.lang.NoClassDefFoundError: freenet/node/NodeStarter INFO | jvm 5| 2008/11/19 10:06:54 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter INFO | jvm 5| 2008/11/19 10:06:54 | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) INFO | jvm 5| 2008/11/19 10:06:54 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 5| 2008/11/19 10:06:54 | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClass(ClassLoader.java:307) INFO | jvm 5| 2008/11/19 10:06:54 | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClass(ClassLoader.java:252) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) INFO | jvm 5| 2008/11/19 10:06:54 | Could not find the main class: freenet.node.NodeStarter. Program will exit. FATAL | wrapper | 2008/11/19 10:06:54 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
[freenet-support] A 1180 non-starter
Freenet 1180 refuses to start; here is an extract from the wrapper.log file: STATUS | wrapper | 2008/11/19 10:06:54 | Launching a JVM... ERROR | wrapper | 2008/11/19 10:06:54 | JVM exited while loading the application. INFO | jvm 5| 2008/11/19 10:06:54 | Exception in thread main java.lang.NoClassDefFoundError: freenet/node/NodeStarter INFO | jvm 5| 2008/11/19 10:06:54 | Caused by: java.lang.ClassNotFoundException: freenet.node.NodeStarter INFO | jvm 5| 2008/11/19 10:06:54 | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) INFO | jvm 5| 2008/11/19 10:06:54 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 5| 2008/11/19 10:06:54 | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClass(ClassLoader.java:307) INFO | jvm 5| 2008/11/19 10:06:54 | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClass(ClassLoader.java:252) INFO | jvm 5| 2008/11/19 10:06:54 | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) INFO | jvm 5| 2008/11/19 10:06:54 | Could not find the main class: freenet.node.NodeStarter. Program will exit. FATAL | wrapper | 2008/11/19 10:06:54 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. ___ 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] Broken freesites in #1178
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. Peter.
[freenet-support] Broken freesites in #1178
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. Peter. ___ 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]
