[freenet-support] Two bugs reported on FMS
On Wednesday 28 January 2009 07:24, 3BUIb3S50i 3BUIb3S50i wrote: > Don Sato at tGZmfuEbnEqArnhpyqj4of3-s21B0uTliyfALlQ0bw8 wrote: > > One of the recent Freenet builds caused my Freenet node end up with > > almost constant 100% CPU usage. This trouble began somewhere inbetween > > 1199-1203 releases. My node used to work very nicely before that. Is > > anyone else experiencing this problem? > > > > I can post info Stats page and Freenet logs to help in diagnosing the > > problem if needed. Just let me know which parts in particular you're > > interested in. Regarding wrapper.log, I found nothing of use in there, > > just the node (re)start/stop related activity. Please determine whether this is a memory-related problem. Add the following to your wrapper.conf, and then view the file freenet.loggc: wrapper.java.additional.3=-Xloggc:freenet.loggc If it is showing Full GC's very frequently (once a second or more), then there is a memory problem. If not, the problem is something else... A stack dump might also be interesting. If you are doing a big download or upload, there will inevitably be periods when Freenet uses lots of CPU for FEC encoding/decoding, or for compression/decompression; but this is generally run at a low priority. > > > > I even tried complete reinstall of the node with new datastore, but to no > > avail. Datastore type is salt-hash. Is the download queue empty? > > > > My specs: > > JVM Info > > > > * Used Java memory: 159 MiB > > * Allocated Java memory: 244 MiB > > * Maximum Java memory: 508 MiB > > * Running threads: 280/500 May not be a memory problem then ... Please do the above steps anyway. If it isn't a memory problem, a stack dump might be useful (note that it may have sensitive information in it sometimes...) > > * Available CPUs: 1 > > * Java Version: 1.6.0_10 > > * JVM Vendor: Sun Microsystems Inc. > > * JVM Version: 11.0-b15 > > * OS Name: Linux > > * OS Version: 2.6.27-9-generic > > * OS Architecture: i386 > > bubba at Uv~laZHgpQPILgjUTc2bD~mMDm5r1PJKYsS3kZNUixM wrote: > > Tommy[D]@EefdujDZxdWxl0qusX0cJofGmJBvd3dF4Ty61PZy8Y8 wrote: > > > >> myidentity at 1QowK8lzyEYNUsI0yGamWcd6ox80XQkKr8kCS6PmJ5Q schrieb: > >>> Has happened a couple times in the last couple days. All through put simply > >>> stops with my node. Once I simply waited a long time and it started to work > >>> again but the speed was very, very slow so I restarted the node. > >>> > >>> One time confirmed for sure it died for 6 hours till I got back to my computer > >>> and restarted the node. > >>> > >>> After restarting the node it seems to work fine again till it dies. This is not > >>> common maybe it has happened 3-4 times since the last update. > >>> > >>> I run a fast computer with lots of memory. 1 gig given to freenet. > >>> > >>> I will continue to monitor this and report back if it continues. > >> > >> Would be nice to have some data out of wrapper.log or logs/*, else it is hard to find the problem > >> and fix it. Also other things like node stats can be interesting. > > > > same here, i think it's a memory leak That is easily confirmed, see the procedure mentioned above. -- 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/20090128/873d4628/attachment.pgp>
[freenet-support] Italian user reports 1 peer diconnected for not acking
An italian user that doesnt speak English asked me to report for him that 1 peer has been forcibly diconnected for not acking packages for 10 min or more. His e-mail came from Gigi Puddu basetre at gmail.com and he identified himself as someone I helped on #freenet-it some time ago I told him that I would send his report so here it is. I also told him not to worry about his node, that it would keep working as usual. the message he got was the Italilan translation of "probable bug, please 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 to the support mailing list support at freenetproject.org. Please include this message and what version of the node you are running. The guy didn't include the release # in his e-mail, only that he's running freenet 0.7 (I know he has autoupdate enabled, so it's probably the letest stable at the time of this email (12 noon GMT, Wednesday 28) Luke --
[freenet-support] Two bugs reported on FMS
Don Sato at tGZmfuEbnEqArnhpyqj4of3-s21B0uTliyfALlQ0bw8 wrote: > One of the recent Freenet builds caused my Freenet node end up with > almost constant 100% CPU usage. This trouble began somewhere inbetween > 1199-1203 releases. My node used to work very nicely before that. Is > anyone else experiencing this problem? > > I can post info Stats page and Freenet logs to help in diagnosing the > problem if needed. Just let me know which parts in particular you're > interested in. Regarding wrapper.log, I found nothing of use in there, > just the node (re)start/stop related activity. > > I even tried complete reinstall of the node with new datastore, but to no > avail. Datastore type is salt-hash. > > My specs: > JVM Info > > * Used Java memory: 159 MiB > * Allocated Java memory: 244 MiB > * Maximum Java memory: 508 MiB > * Running threads: 280/500 > * Available CPUs: 1 > * Java Version: 1.6.0_10 > * JVM Vendor: Sun Microsystems Inc. > * JVM Version: 11.0-b15 > * OS Name: Linux > * OS Version: 2.6.27-9-generic > * OS Architecture: i386 bubba at Uv~laZHgpQPILgjUTc2bD~mMDm5r1PJKYsS3kZNUixM wrote: > Tommy[D]@EefdujDZxdWxl0qusX0cJofGmJBvd3dF4Ty61PZy8Y8 wrote: > >> myidentity at 1QowK8lzyEYNUsI0yGamWcd6ox80XQkKr8kCS6PmJ5Q schrieb: >>> Has happened a couple times in the last couple days. All through put simply >>> stops with my node. Once I simply waited a long time and it started to work >>> again but the speed was very, very slow so I restarted the node. >>> >>> One time confirmed for sure it died for 6 hours till I got back to my >>> computer >>> and restarted the node. >>> >>> After restarting the node it seems to work fine again till it dies. This >>> is not >>> common maybe it has happened 3-4 times since the last update. >>> >>> I run a fast computer with lots of memory. 1 gig given to freenet. >>> >>> I will continue to monitor this and report back if it continues. >> >> Would be nice to have some data out of wrapper.log or logs/*, else it is >> hard to find the problem >> and fix it. Also other things like node stats can be interesting. > > same here, i think it's a memory leak -- 3buib3s50i at gmail.com | dimonqmfcb at gmx.com
[freenet-support] Italian user reports 1 peer diconnected for not acking
An italian user that doesnt speak English asked me to report for him that 1 peer has been forcibly diconnected for not acking packages for 10 min or more. His e-mail came from Gigi Puddu base...@gmail.com and he identified himself as someone I helped on #freenet-it some time ago I told him that I would send his report so here it is. I also told him not to worry about his node, that it would keep working as usual. the message he got was the Italilan translation of probable bug, please 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 to the support mailing list supp...@freenetproject.org. Please include this message and what version of the node you are running. The guy didn't include the release # in his e-mail, only that he's running freenet 0.7 (I know he has autoupdate enabled, so it's probably the letest stable at the time of this email (12 noon GMT, Wednesday 28) Luke -- ___ 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] Two bugs reported on FMS
On Wednesday 28 January 2009 07:24, 3BUIb3S50i 3BUIb3S50i wrote: Don s...@tgzmfuebneqarnhpyqj4of3-s21b0utliyfallq0bw8 wrote: One of the recent Freenet builds caused my Freenet node end up with almost constant 100% CPU usage. This trouble began somewhere inbetween 1199-1203 releases. My node used to work very nicely before that. Is anyone else experiencing this problem? I can post info Stats page and Freenet logs to help in diagnosing the problem if needed. Just let me know which parts in particular you're interested in. Regarding wrapper.log, I found nothing of use in there, just the node (re)start/stop related activity. Please determine whether this is a memory-related problem. Add the following to your wrapper.conf, and then view the file freenet.loggc: wrapper.java.additional.3=-Xloggc:freenet.loggc If it is showing Full GC's very frequently (once a second or more), then there is a memory problem. If not, the problem is something else... A stack dump might also be interesting. If you are doing a big download or upload, there will inevitably be periods when Freenet uses lots of CPU for FEC encoding/decoding, or for compression/decompression; but this is generally run at a low priority. I even tried complete reinstall of the node with new datastore, but to no avail. Datastore type is salt-hash. Is the download queue empty? My specs: JVM Info * Used Java memory: 159 MiB * Allocated Java memory: 244 MiB * Maximum Java memory: 508 MiB * Running threads: 280/500 May not be a memory problem then ... Please do the above steps anyway. If it isn't a memory problem, a stack dump might be useful (note that it may have sensitive information in it sometimes...) * Available CPUs: 1 * Java Version: 1.6.0_10 * JVM Vendor: Sun Microsystems Inc. * JVM Version: 11.0-b15 * OS Name: Linux * OS Version: 2.6.27-9-generic * OS Architecture: i386 bu...@uv~lazhgpqpilgjutc2bd~mmdm5r1pjkyss3kznuixm wrote: tommy...@eefdujdzxdwxl0qusx0cjofgmjbvd3df4ty61pzy8y8 wrote: myident...@1qowk8lzyeynusi0ygamwcd6ox80xqkkr8kcs6pmj5q schrieb: Has happened a couple times in the last couple days. All through put simply stops with my node. Once I simply waited a long time and it started to work again but the speed was very, very slow so I restarted the node. One time confirmed for sure it died for 6 hours till I got back to my computer and restarted the node. After restarting the node it seems to work fine again till it dies. This is not common maybe it has happened 3-4 times since the last update. I run a fast computer with lots of memory. 1 gig given to freenet. I will continue to monitor this and report back if it continues. Would be nice to have some data out of wrapper.log or logs/*, else it is hard to find the problem and fix it. Also other things like node stats can be interesting. same here, i think it's a memory leak That is easily confirmed, see the procedure mentioned above. pgpVSRXZA1hh0.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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] installation
I think I installed FreeNet, but when I go to the site listed I get the following message: Safari can’t connect to the server. Safari can’t open the page “http://127.0.0.1:/wizard/” because it could not connect to the server “127.0.0.1”. ___ 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] installation
On Wednesday 28 January 2009 19:09, Joseph Schultz wrote: I think I installed FreeNet, but when I go to the site listed I get the following message: Safari can’t connect to the server. Safari can’t open the page “http://127.0.0.1:/wizard/” because it could not connect to the server “127.0.0.1”. Is Safari set to use a proxy? That's the first thing to check. You should be able to tell it to not use the proxy for 127.0.0.1. If that is not the problem, then find the directory you installed Freenet to. Is there a wrapper.log file? If so, please send me it, it should help to debug this... If not, please let me know, and I suggest you run run.sh start in that directory (from a command line e.g.). pgpGI8h1bCmB8.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:support-requ...@freenetproject.org?subject=unsubscribe
