Toad wrote:
On Sun, Sep 28, 2003 at 12:29:49PM -0700, Martin Stone Davis wrote:
Martin Stone Davis wrote:
In my case, I also turned off bwlimiter, and after 7 hours, there
doesn't appear to be a reduction in outgoing bw. I'll continue to let
it run another 10 hours unless I get an out-of-memory
On Sun, Sep 28, 2003 at 12:29:49PM -0700, Martin Stone Davis wrote:
> Martin Stone Davis wrote:
>
> > In my case, I also turned off bwlimiter, and after 7 hours, there
> > doesn't appear to be a reduction in outgoing bw. I'll continue to let
> > it run another 10 hours unless I get an out-of-memo
After 5 hours running 6211, I started getting OOMs. I was running
another memory-intensive app at the time, so I'll try again without
running anything like that.
late part of my log file:
Sep 28, 2003 7:28:36 PM (freenet.message.DataRequest, QThread-117764,
NORMAL): Long messageInitialStateTi
Grrr, one of the seednode sources was returning bogus data.
Ian.
On Mon, Sep 29, 2003 at 07:53:16AM +0200, Niklas Bergh wrote:
> Sanity?
>
> >I tried re-seeding, but getting the same exception.
> >
> >I opened up seednodes.ref, and on line 601:
> >
> >( Error: Unable to retreve data from databas
I added a check for this into CVS.. the DSASignature class will now
intentionally NPE when it is constructed with invalid parameters instead of
when it is used later on. Should make tracking down the root cause of this
issue much easier. Please cause it again and report :)
/N
>247d8b802e2c1b21652
Sanity?
>I tried re-seeding, but getting the same exception.
>
>I opened up seednodes.ref, and on line 601:
>
>( Error: Unable to retreve data from database
>)^M
>
>IF that line is removed the rror no longer occurs
___
Devl mailing list
[EMAIL PROTECTE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| I checked my rtnode_a and rtnodes_b file, and look what I found
|
| 'Õ^T?N
| version=] ^Rbª^5^QãÇâ,5028
| presentations=1
|
identity.g=930168de21e7fb66c0375e08e964255a0f7f0ad54507a51864afdc686f36be8bb8b7$
|
| identity.q=ef1f7a7a73362e526515f348075aee2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tracy R Reed wrote:
|
| I have this and I saw someone on IRC with this also. I suspect a node out
| there was handing out a corrupted noderef and now a bunch of us have it.
| Any easy way to figure out which node it is so we can remove it? Not a big
|
On Sun, Sep 28, 2003 at 09:57:56PM -0500, Salah Coronya spake thusly:
> Sep 28, 2003 8:15:22 AM (freenet.node.Main, main, ERROR): Skipped bad
> NodeReference while reading seed nodes
> freenet.node.BadReferenceException: NodeReference self signature check
> failed.
I have this and I saw someone on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| Okay, I'll change back to maxRequestsPerInterval=300, re-activate
| bwlimiting, and upgrade to version 6211. My machine has 512MB of RAM,
| so I will set JavaMem=256.
|
| -Martin
|
| Brandon Low wrote:
|
|> How much ram doe
sounds great! Strangely (very strangely) my node on 6211 hasn't started
leaking memory yet, and it has been up for 7 hours... wonder if
something automagically fixed that issue or something...
Anywho, if we can resolve the memory leak issue and have code that works
for > 24 hour uptime then it is
Okay, I'll change back to maxRequestsPerInterval=300, re-activate
bwlimiting, and upgrade to version 6211. My machine has 512MB of RAM,
so I will set JavaMem=256.
-Martin
Brandon Low wrote:
How much ram does your box have? My freenet runs at about 200M most of
the time to be 'comfortable' so
How much ram does your box have? My freenet runs at about 200M most of
the time to be 'comfortable' so the fact that it OOM'd when only being
allowed to use ~128M doesn't surprise me... if your box has at least
384M of ram, try running freenet with -Xmx256M.
--Brandon
On Sun, 09/28/03 at 12:29:4
Martin Stone Davis wrote:
> In my case, I also turned off bwlimiter, and after 7 hours, there
> doesn't appear to be a reduction in outgoing bw. I'll continue to let
> it run another 10 hours unless I get an out-of-memory error or someone
> tells me I should switch to a new version.
Here's what h
Salah Coronya wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| As you probably read in the "Decreasing upstream bandwidth over time in
| 6205" thread, I've been having the same kind of problem. (note: I am
| now using 6209)
|
| It turns out that my QueriesPerHour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| As you probably read in the "Decreasing upstream bandwidth over time in
| 6205" thread, I've been having the same kind of problem. (note: I am
| now using 6209)
|
| It turns out that my QueriesPerHour is very high, like Sal
Has the decreasing upstream bw usage over time improved with more recent
builds? Has anyone _not_ bwlimiting in freenet had problems with OOMs?
I am of the belief that there is a slow memory leak in bwlimiting on
heavily loaded nodes.
--Brandon
On Sat, 09/27/03 at 23:28:53 -0700, Martin Stone Da
As you probably read in the "Decreasing upstream bandwidth over time in
6205" thread, I've been having the same kind of problem. (note: I am
now using 6209)
It turns out that my QueriesPerHour is very high, like Salah's, although
mine averages around 80,000. I've altered my freenet.ini as fol
18 matches
Mail list logo
