On Thu, 16 Jan 2003, Matthew Toseland wrote: > On Thu, Jan 16, 2003 at 10:16:49AM -0800, Chris Linstruth wrote: > > Exactly what I'm seeing. When I stop/restart it'll run for give-or-take > > a few hours, 48 hours then usage will go to 0, 0ms CurrentRoutingTime. > What exact build number is this? 543 > And please send me a log file, with logLevel=debug, and a thread dump, > which you get by kill -QUIT'ing the node. node restarted with logging enabled. I'll post when it misbehaves again. > > > > Glad I'm not alone. > > -- > > Chris Linstruth <[EMAIL PROTECTED]> > > QNET > > 1529 East Palmdale Blvd Suite 200 > > Palmdale, CA 93550 > > (661) 538-2028 > > > > > > On Thu, 16 Jan 2003, Niklas Bergh wrote: > > > > > This problem is very similar to the problem I have been wrestling with for > > > some time... If you look in your 'Node Status Info' page, what > > > CurrentRoutingTime do you see. Is it 0 and the row below still says that > > > there are many pooled jobs and that your node is currently queryrejecting it > > > might be the same problem. > > > > > > My problem appeared when I raised the number of threads in order to make my > > > node use more of the available bandwidth. > > >
_______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
