Re: [freenet-support] Problem with open Freenet

2012-08-02 Thread Matthew Toseland 
On Wednesday 09 May 2012 18:29:19 Rafał Cieloch wrote:
> Hey when i want to open Freenet after instalation i have comunnicate:
> 
> The freenet wrapper terminated unexpectedly
> 
> Freenet launcher was unable to connect to the Freenet node at port 
> 
> You can help me what is going ?
> 
The log suggests that Freenet is working. Have you tried just opening 
http://127.0.0.1:/ in a web browser?

If it doesn't work, please send an up to date copy of the last part (200 lines 
or so) of your wrapper.log. Thanks.


signature.asc
Description: This is a digitally signed message part.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

[freenet-support] Problem with open Freenet

2012-05-09 Thread Rafał Cieloch 
Hey when i want to open Freenet after instalation i have comunnicate:

The freenet wrapper terminated unexpectedly

Freenet launcher was unable to connect to the Freenet node at port 

You can help me what is going ?



This is log:
STATUS | wrapper  | 2012/05/09 19:18:14 | --> Wrapper Started as Console
STATUS | wrapper  | 2012/05/09 19:18:14 | Java Service Wrapper Community
Edition 32-bit 3.3.5
STATUS | wrapper  | 2012/05/09 19:18:14 |   Copyright (C) 1999-2009 Tanuki
Software, Ltd.  All Rights Reserved.
STATUS | wrapper  | 2012/05/09 19:18:14 |
http://wrapper.tanukisoftware.org
STATUS | wrapper  | 2012/05/09 19:18:14 |
STATUS | wrapper  | 2012/05/09 19:18:14 | Launching a JVM...
ERROR  | wrapper  | 2012/05/09 19:19:14 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2012/05/09 19:19:14 |
ADVICE | wrapper  | 2012/05/09 19:19:14 |

ADVICE | wrapper  | 2012/05/09 19:19:14 | Advice:
ADVICE | wrapper  | 2012/05/09 19:19:14 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2012/05/09 19:19:14 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2012/05/09 19:19:14 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2012/05/09 19:19:14 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2012/05/09 19:19:14 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2012/05/09 19:19:14 | the Wrapper classes:
ADVICE | wrapper  | 2012/05/09 19:19:14 | freenet.node.NodeStarter
ADVICE | wrapper  | 2012/05/09 19:19:14 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2012/05/09 19:19:14 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2012/05/09 19:19:14 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2012/05/09 19:19:14 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2012/05/09 19:19:14 | within the Wrapper:
ADVICE | wrapper  | 2012/05/09 19:19:14 |
http://wrapper.tanukisoftware.org/doc/english/integrate.html
ADVICE | wrapper  | 2012/05/09 19:19:14 |

ADVICE | wrapper  | 2012/05/09 19:19:14 |
ERROR  | wrapper  | 2012/05/09 19:19:19 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2012/05/09 19:19:28 | Reloading Wrapper configuration...
STATUS | wrapper  | 2012/05/09 19:19:28 | Launching a JVM...
INFO   | jvm 2| 2012/05/09 19:20:01 | WrapperManager: Initializing...
ERROR  | wrapper  | 2012/05/09 19:20:17 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2012/05/09 19:20:17 |
ADVICE | wrapper  | 2012/05/09 19:20:17 |

ADVICE | wrapper  | 2012/05/09 19:20:17 | Advice:
ADVICE | wrapper  | 2012/05/09 19:20:17 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2012/05/09 19:20:17 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2012/05/09 19:20:17 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2012/05/09 19:20:17 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2012/05/09 19:20:17 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2012/05/09 19:20:17 | the Wrapper classes:
ADVICE | wrapper  | 2012/05/09 19:20:17 | freenet.node.NodeStarter
ADVICE | wrapper  | 2012/05/09 19:20:17 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2012/05/09 19:20:17 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2012/05/09 19:20:22 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2012/05/09 19:20:22 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2012/05/09 19:20:22 | within the Wrapper:
ADVICE | wrapper  | 2012/05/09 19:20:22 |
http://wrapper.tanukisoftware.org/doc/english/integrate.html
ADVICE | wrapper  | 2012/05/09 19:20:22 |

ADVICE | wrapper  | 2012/05/09 19:20:22 |
INFO   | jvm 2| 2012/05/09 19:20:22 | WrapperManager: WARNING - The
Wrapper jar file currently in use is version "3.3.1"
INFO   | jvm 2| 2012/05/09 19:20:22 | WrapperManager:   while
the version of the Wrapper which launched this JVM is
INFO   | jvm 2| 2012/05/09 19:20:22 | WrapperManager:   "3.3.5".
INFO   | jvm 2| 2012/05/09 19:20:22 | WrapperManager:   The
Wrapper may appear to work correctly but some features may
INFO   | jvm 2| 2