On Sat, Mar 31, 2007 at 11:34:27PM +0100, Mr. Flibble wrote: > After attempting to do an update, which seemed to take a very long time > (about an hour, which is a lot longer than It's taken before), I've tried to > stop my node (as I couldn't get to the web interface).
Okay, so the node has actually crashed. > > I tried stopping the windows service (which normally takes a while), but > the java process is still running, pegging the cpu somewhat, and taskman > refuses to kill the task... > > The last few lines of the log read as follows: > > Mar 31, 2007 21:44:45:850 (freenet.node.PeerManager, > WrapperListener_start_runner, NORMAL): Read 15 peers from .\peers-xxxx > Mar 31, 2007 21:44:57:428 (freenet.node.Node, WrapperListener_start_runner, > NORMAL): Initializing CHK Datastore > Mar 31, 2007 21:46:38:006 (freenet.node.Node, WrapperListener_start_runner, > NORMAL): Initializing CHK Datacache > Mar 31, 2007 21:52:10:584 (freenet.store.BerkeleyDBFreenetStore, > WrapperListener_start_runner, ERROR): Reconstructing block numbers index... > > Before I reboot (which I'd prefer not to do as my freenet 0.5 node is also > on this machine too and takes ages to start up), is this error serious, or > should I leave it to do it's "reconstruction" ? Upgrade to the most recent version, restart it. Then tell us if the errors continue. Reconstruction shouldn't be a big problem... but some builds had wrapper timeout issues with it causing continual restarts.
signature.asc
Description: Digital signature
_______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
