Re: Wrapper unexpected termination
Dennis Nezic <[email protected]>
| Newsgroups | gmane.network.freenet.support |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 28 May 2012 15:11:48 -0400 (EDT), [email protected] wrote: > Hi Dennis and thanks for the reply. > > No change to disk space or memory they are fine. Here is tha last > park of the wrapper log from the last failed instalation. > [...] > INFO | jvm 1 | 2012/05/28 08:38:11 | Defragmenting persistent > downloads database. > [...] > INFO | jvm 1 | 2012/05/28 08:38:26 | Defragment completed. 13.6 > MiB (14320632) -> 13.6 MiB (14319872) (0% shrink) > > [...] > WrapperManager Error: > at com.db4o.reflect.generic.GenericArrayReflector.set > (GenericArrayReflector. java:103) > WrapperManager Error: at > com.db4o.internal.handlers.array.ArrayHandler.readInto > (ArrayHandler.java:418) Looks like some kind of node.db4o* corruption -- another kinda common bug we seem to encounter. I have had at least one a while ago. I'm not sure if the defragmenting of it just before had anything to do with it. The simplest "solution" is to delete your node.db4(.crypt?|*) file. You'll lose the downloads/uploads that you had queued, but that should get the node back up and running at least :s. _______________________________________________ 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:support-request-RdDMkVZAZeuJnvDnx1genB2eb7JE58TQ@public.gmane.org?subject=unsubscribe