Toad wrote: > Interesting. A thread dump would be _really_ useful, kill -QUIT `cat > freenet.pid` will dump threads to standard error.
Ok, here are more details on a hang up that occurred last night. Node ran fine for about 12 hours at a stretch, uploading about 20kb/s, downloading about 10kb/s. Then traffic dropped to nearly 0 kb/s, both up and down. The number of concurrent connections of the box started rising (increased by 400 over the last 5 hours). Now cpu usage is down to 0%. Output from top: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 18590 freenet 35 10 147M 74M 552 S N 0.0 29.7 342:49 0 java So far this is behavior I've seen quite often. But surprisingly, the web interface doesn't respond any more: it still listens on the 8888 port but doesn't reply (it usually works fine in this situation). Unfortunately it ignores a kill -QUIT / kill -3. So I didn't manage to get at thread dump (suggestions welcomed). Attached is freenet.log. Traffic dropped at about the same time (or a bit after) the time of the last log entry. Configuration: - Red Hat 9 on PIII 800 256 Mb - Sun JVM 1.4.2-beta-b19 started with -Xmx128M - max store size 10Gb, 9Gb used, 7.3Gb free space on device - freenet.conf has the default settings, except for - ipAddress, listenPort, storeFile, storeSize, mainport.allowedHosts - doAnnounce=false - rtMaxNodes=100 - misc log options - using the native fec libraries I've backed up the log, configuration and stats files; if there's anything helpful in there let me know and I'll mail it to you. Cheers, Menno -------------- next part -------------- A non-text attachment was scrubbed... Name: freenet.log.zip Type: application/zip Size: 13306 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20030512/fe66cfa0/attachment.zip>
