Freenet error

Timothy Clark <[email protected]>
Newsgroups gmane.network.freenet.support
Message-ID <CAJ3+Ef2yFJiGozAyK08nGUS93zWR+eD0OJN+zacuEn45z=8H+Q@mail.gmail.com>
I keep getting the error message saying that the freenet wrapper terminated
unexpectedly. And also that it is unable to connect to node 8888. How can I
fix this?

I'm running on Windows 7.

Here is my wrapper log:

STATUS | wrapper  | 2013/09/01 10:11:34 | --> Wrapper Started as Console
STATUS | wrapper  | 2013/09/01 10:11:34 | Java Service Wrapper Community
Edition 32-bit 3.5.20
STATUS | wrapper  | 2013/09/01 10:11:34 |   Copyright (C) 1999-2013 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2013/09/01 10:11:34 |
http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2013/09/01 10:11:34 |
STATUS | wrapper  | 2013/09/01 10:11:36 | Launching a JVM...
ERROR  | wrapper  | 2013/09/01 10:12:06 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2013/09/01 10:12:06 |
ADVICE | wrapper  | 2013/09/01 10:12:06 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:12:06 | Advice:
ADVICE | wrapper  | 2013/09/01 10:12:06 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2013/09/01 10:12:06 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2013/09/01 10:12:06 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2013/09/01 10:12:06 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2013/09/01 10:12:06 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2013/09/01 10:12:06 | the Wrapper classes:
ADVICE | wrapper  | 2013/09/01 10:12:06 |     freenet.node.NodeStarter
ADVICE | wrapper  | 2013/09/01 10:12:06 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2013/09/01 10:12:06 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2013/09/01 10:12:06 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2013/09/01 10:12:06 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2013/09/01 10:12:06 | within the Wrapper:
ADVICE | wrapper  | 2013/09/01 10:12:06 |
http://wrapper.tanukisoftware.com/doc/english/integrate.html
ADVICE | wrapper  | 2013/09/01 10:12:06 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:12:06 |
ERROR  | wrapper  | 2013/09/01 10:12:06 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/09/01 10:12:06 | JVM exited after being requested
to terminate.
STATUS | wrapper  | 2013/09/01 10:12:11 | Reloading Wrapper configuration...
STATUS | wrapper  | 2013/09/01 10:12:11 | Launching a JVM...
ERROR  | wrapper  | 2013/09/01 10:12:41 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2013/09/01 10:12:41 |
ADVICE | wrapper  | 2013/09/01 10:12:41 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:12:41 | Advice:
ADVICE | wrapper  | 2013/09/01 10:12:41 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2013/09/01 10:12:41 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2013/09/01 10:12:41 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2013/09/01 10:12:41 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2013/09/01 10:12:41 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2013/09/01 10:12:41 | the Wrapper classes:
ADVICE | wrapper  | 2013/09/01 10:12:41 |     freenet.node.NodeStarter
ADVICE | wrapper  | 2013/09/01 10:12:41 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2013/09/01 10:12:41 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2013/09/01 10:12:41 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2013/09/01 10:12:41 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2013/09/01 10:12:41 | within the Wrapper:
ADVICE | wrapper  | 2013/09/01 10:12:41 |
http://wrapper.tanukisoftware.com/doc/english/integrate.html
ADVICE | wrapper  | 2013/09/01 10:12:41 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:12:41 |
ERROR  | wrapper  | 2013/09/01 10:12:41 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/09/01 10:12:45 | JVM exited after being requested
to terminate.
STATUS | wrapper  | 2013/09/01 10:12:49 | Reloading Wrapper configuration...
STATUS | wrapper  | 2013/09/01 10:12:50 | Launching a JVM...
ERROR  | wrapper  | 2013/09/01 10:13:19 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2013/09/01 10:13:19 |
ADVICE | wrapper  | 2013/09/01 10:13:19 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:13:19 | Advice:
ADVICE | wrapper  | 2013/09/01 10:13:19 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2013/09/01 10:13:19 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2013/09/01 10:13:19 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2013/09/01 10:13:19 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2013/09/01 10:13:19 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2013/09/01 10:13:19 | the Wrapper classes:
ADVICE | wrapper  | 2013/09/01 10:13:19 |     freenet.node.NodeStarter
ADVICE | wrapper  | 2013/09/01 10:13:19 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2013/09/01 10:13:19 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2013/09/01 10:13:19 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2013/09/01 10:13:19 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2013/09/01 10:13:19 | within the Wrapper:
ADVICE | wrapper  | 2013/09/01 10:13:19 |
http://wrapper.tanukisoftware.com/doc/english/integrate.html
ADVICE | wrapper  | 2013/09/01 10:13:19 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:13:19 |
ERROR  | wrapper  | 2013/09/01 10:13:19 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/09/01 10:13:19 | JVM exited after being requested
to terminate.
STATUS | wrapper  | 2013/09/01 10:13:24 | Reloading Wrapper configuration...
STATUS | wrapper  | 2013/09/01 10:13:25 | Launching a JVM...
ERROR  | wrapper  | 2013/09/01 10:13:54 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2013/09/01 10:13:54 |
ADVICE | wrapper  | 2013/09/01 10:13:54 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:13:54 | Advice:
ADVICE | wrapper  | 2013/09/01 10:13:54 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2013/09/01 10:13:54 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2013/09/01 10:13:54 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2013/09/01 10:13:54 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2013/09/01 10:13:54 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2013/09/01 10:13:54 | the Wrapper classes:
ADVICE | wrapper  | 2013/09/01 10:13:54 |     freenet.node.NodeStarter
ADVICE | wrapper  | 2013/09/01 10:13:54 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2013/09/01 10:13:54 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2013/09/01 10:13:54 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2013/09/01 10:13:54 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2013/09/01 10:13:54 | within the Wrapper:
ADVICE | wrapper  | 2013/09/01 10:13:54 |
http://wrapper.tanukisoftware.com/doc/english/integrate.html
ADVICE | wrapper  | 2013/09/01 10:13:54 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:13:54 |
ERROR  | wrapper  | 2013/09/01 10:13:54 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/09/01 10:13:55 | JVM exited after being requested
to terminate.
STATUS | wrapper  | 2013/09/01 10:14:00 | Reloading Wrapper configuration...
STATUS | wrapper  | 2013/09/01 10:14:00 | Launching a JVM...
ERROR  | wrapper  | 2013/09/01 10:14:30 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2013/09/01 10:14:30 |
ADVICE | wrapper  | 2013/09/01 10:14:30 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:14:30 | Advice:
ADVICE | wrapper  | 2013/09/01 10:14:30 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2013/09/01 10:14:30 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2013/09/01 10:14:30 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2013/09/01 10:14:30 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2013/09/01 10:14:30 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2013/09/01 10:14:30 | the Wrapper classes:
ADVICE | wrapper  | 2013/09/01 10:14:30 |     freenet.node.NodeStarter
ADVICE | wrapper  | 2013/09/01 10:14:30 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2013/09/01 10:14:30 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2013/09/01 10:14:30 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2013/09/01 10:14:30 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2013/09/01 10:14:30 | within the Wrapper:
ADVICE | wrapper  | 2013/09/01 10:14:30 |
http://wrapper.tanukisoftware.com/doc/english/integrate.html
ADVICE | wrapper  | 2013/09/01 10:14:30 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2013/09/01 10:14:30 |
ERROR  | wrapper  | 2013/09/01 10:14:30 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/09/01 10:14:31 | JVM exited after being requested
to terminate.
FATAL  | wrapper  | 2013/09/01 10:14:31 | There were 5 failed launches in a
row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2013/09/01 10:14:31 |   There may be a configuration
problem: please check the logs.
INFO   | wrapperp | 2013/09/01 10:14:31 | backend pipe closed.
INFO   | wrapperp | 2013/09/01 10:14:31 | backend pipe closed.
STATUS | wrapper  | 2013/09/01 10:14:31 | <-- Wrapper Stopped



Thank you.

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.