On Tuesday 06 May 2008 22:20, Jim Cook wrote:
> At 09:17 AM 5/6/2008, Matthew Toseland wrote:
> 
> >* PGP Signed by an unknown key
> >
> >On Tuesday 06 May 2008 01:41, Jim Cook wrote:
> > > 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.
> >
> >The above happened before this change?
> 
> Yes, it did.  And I've realized that setting Freenet's priority to 
> NORMAL in Process Explorer didn't persist, so I need to figure our 
> how to make it so.

In wrapper.conf.
> 
> > > > > 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".
> >
> >Because of IPv6? That's not related. Are you sure it tries to reseed? Does 
it
> >show the announcing alert on the homepage? What does it say in the
> >wrapper.log?
> 
> On the homepage, it said that it was trying to connect, and that it 
> would be slow for a while.  I've e-mailed you the relevant part of 
> the wrapper.log.

What if you click on the alert? Show me the details.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20080507/f9bbecdc/attachment.pgp>

Reply via email to