[freenet-support] Node won't start

2007-03-09 Thread Andrew Walker
I'm running Gentoo Linux and can't get my node to start. I get the following message running as console. vm 5| Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in jvm 5| Initializing USK Manager wrapper | JVM did not exit on request, terminated wrapper | JVM exited

Re: [freenet-support] Node won't start

2007-03-09 Thread Andrew Walker
On Friday 09 March 2007 18:42:31 Matthew Toseland wrote: Please delete wrapper.log and then restart. Once it has failed send me the *full* wrapper.log. This is most likely some sort of timeout problem; we can probably fix it. On Fri, Mar 09, 2007 at 06:35:31PM +, Andrew Walker wrote

Re: [freenet-support] Node won't start

2007-03-10 Thread Andrew Walker
+, Andrew Walker wrote: On Friday 09 March 2007 18:42:31 Matthew Toseland wrote: Please delete wrapper.log and then restart. Once it has failed send me the *full* wrapper.log. This is most likely some sort of timeout problem; we can probably fix it. On Fri, Mar 09, 2007 at 06:35

[freenet-support] Node won't start

2007-03-09 Thread Andrew Walker
I'm running Gentoo Linux and can't get my node to start. I get the following message running as console. vm 5| Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in jvm 5| Initializing USK Manager wrapper | JVM did not exit on request, terminated wrapper | JVM exited

[freenet-support] Node won't start

2007-03-09 Thread Andrew Walker
On Friday 09 March 2007 18:42:31 Matthew Toseland wrote: > Please delete wrapper.log and then restart. Once it has failed send me > the *full* wrapper.log. This is most likely some sort of timeout > problem; we can probably fix it. > > On Fri, Mar 09, 2007 at 06:35:31PM +, Andr

[freenet-support] Node won't start

2007-03-10 Thread Andrew Walker
Mar 09, 2007 at 07:00:10PM +, Andrew Walker wrote: > > On Friday 09 March 2007 18:42:31 Matthew Toseland wrote: > > > Please delete wrapper.log and then restart. Once it has failed send me > > > the *full* wrapper.log. This is most likely some sort of timeout > > &g