On Mon, 2003-10-13 at 13:15, Mike Stump wrote: > Well, the high sucess rate was just a temporary aberration only > possible at node startup when when someone stubles across a connection > and others aren't querying yet and they load things that are really > popular. It dropped back down to 1-2% after a very short while. > > The deadlocking has continued unabated and has caused me to move on to > more recent builds in hopes maybe that the problem is cured (or > reduced), and to retweak connections and the query limit down in hopes > of trying to avoid the deadlock. > > More on 6236 later, pause, nope it deadlocked just over 12 minute > range. Hum... Let's go back and try 5028 for grins. No deadlock > yet...
Regarding your deadlock observations:
Give us the non-default parameters in freenet.conf:
grep '^[a-zA-Z]' freenet.conf | grep -v bookmark
Also, next time it occurs, send the java process a QUIT
signal to cause a thread dump of all active threads.
kill -QUIT $(cat freenet.pid)
This is what I put into start-freenet.sh. We need the JVM
environment too.
if [ -f freenet.log ] ; then
echo "Saving old log file"
logfilename=freenet-$(ls -l --time-style=full-iso freenet.log | gawk
'{print $6"-"$7}').log
mv freenet.log $logfilename
ls -l $logfilename
gzip $logfilename
ls -l $logfilename.gz
fi
echo -n "JVM environment: "
java freenet.node.Main --system
echo -n "Freenet version: "
java freenet.node.Main --version
grep '^[a-zA-Z]' freenet.conf | grep -v bookmark
echo -n "Starting Freenet now: `date --utc` `date '+%H:%M:%S %Z: '`"
nice -n 10 -- java -Xmx256m $JAVA_ARGS freenet.node.Main "$@" &
echo $! > freenet.pid
echo "Done, freenet process id is `cat freenet.pid`."
-- Ed Huff
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
