> 
> I'm pretty stumped on this one. I installed java and freenet on my
debian
> machine, and when I `sh start-freenet.sh', everything works fine for a
> while, but if I leave the server alone, I come back and freenet is
just
> not running. Neither syslog nor freenet.log indicate anything, and I
don't
> know where jre logs.
> 
> - Harrison [harrisonts(a)illx.org]
> 

Presumably Java is crashing for some reason, you probably have a load of
hs_err_pid_nnnn files in the freenet directory containing random stack
dumps.
What does `java -version` say? You should use Sun (preferably) or
Blackdown at least v1.4.2 (later versions are generally speaking
"better" but use more memory.)

How long does it take it to die? How big is your datastore? Did it use
to work or has it always done this?

AFAIK, the most common reason for random crashes other than hardware
issues is running out of heap with large datastores. Java stupidly
provides no real way for apps to tell they're running out of memory (or
disk space!), so starvation results in slowing to a crawl followed by an
OOM exception. Some versions of Java appear to be worse at this than
others, e.g. on blackdown 1.4.1 (only one I can use, Sparc box) I had to
set the maximum heap to 1GB yes one Gigabyte for it to start
successfully, and it doesn't even have a large store :)
Although that box is temporarily out of commission with RAM ECC errors
on one module now so that may have had something to do with it ...

Anyway find the "java -Xmx128m etc etc" line at the end of
start-freenet.sh that actually runs freenet, and try changing the Xmx
(maximum heap size) to something larger e.g. -Xmx256m. Hopefully this
will help.

Incidentally it's intended to get the current alpha development version,
the pretty much rewritten and significantly different (UDP, mixed
scalable darknet/lightnet etc) 0.7, to work with with Free JVMs like
Kaffe at some point which may help with this sort of issue.

Bob



Reply via email to