At 01:50 PM 5/5/2008, Matthew Toseland wrote: <snip>
> > After checking the logs, it's clear what's going on. Freenet runs > > just fine after I log off; indeed, it seems to be happier. However, > > when I log on, various Freenet processes start timing out, and the > > node drops all connections after ca. 10 min. This is a fairly old > > machine with a 2.8 GHz Pentium D and 2 Gb RAM, and it's pretty maxed > > out during logon. It loads three apps (Firefox, Eudora and > > UltraEdit) and runs a few system and malware scans, and Freenet drops > > connections before the system frees up. > >Eeek. We should seriously consider increasing Freenet's base priority from >BELOW_NORMAL to NORMAL. We use thread priorities everywhere, only threads >which are critical and don't use much CPU are high priority, so 95% of the >time this shouldn't impact on system performance... > >See https://bugs.freenetproject.org/view.php?id=2337 I've increased its base priority to NORMAL. > > Although Freenet reports that it's trying to connect, I find that it > > hasn't after more than 2 hr. But once I stop and restart in Win XP > > services manager, it connects immediately. > >That's bad. It ought to recover. Does it try to reseed? Yes, it keeps trying, but reports "java.net.SocketException: Protocol not allowed". After stopping the node and restarting, it adds its first peer within two minutes, has five by four minutes, and rapidly connects to ca. 20. > > Is that behavior normal? > >No, it may be a bug. I wasn't keeping enough logs to span the last logoff/logon, but I saw the same behavior after the update to Build #1145. Within a few hours after the update, the node dropped all connections, and wouldn't reconnect until I stopped and restarted. I'll e-mail log excerpts off list. <snip> = Jim Cook <jimcook at panix.com>
