You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Frank Ren (JIRA)" <ji...@apache.org> on 2013/08/01 22:17:49 UTC
[jira] [Created] (DIRSERVER-1880) ApacheDS failed to start on boot
Frank Ren created DIRSERVER-1880:
------------------------------------
Summary: ApacheDS failed to start on boot
Key: DIRSERVER-1880
URL: https://issues.apache.org/jira/browse/DIRSERVER-1880
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 2.0.0-M14
Environment: uname -a
Linux central-server 3.2.0-49-virtual #75-Ubuntu SMP Tue Jun 18 17:59:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/issue.net
Ubuntu 12.04.2 LTS
java -version
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
Reporter: Frank Ren
cat /var/lib/apacheds-2.0.0-M14/default/log/wrapper.log
STATUS | wrapper | 2013/08/01 19:55:48 | --> Wrapper Started as Daemon
STATUS | wrapper | 2013/08/01 19:55:48 | Launching a JVM...
INFO | jvm 1 | 2013/08/01 19:55:52 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2013/08/01 19:55:52 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
INFO | jvm 1 | 2013/08/01 19:55:52 |
ERROR | wrapper | 2013/08/01 19:56:26 | Startup failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2013/08/01 19:56:26 | JVM did not exit on request, terminated
INFO | wrapper | 2013/08/01 19:56:26 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper | 2013/08/01 19:56:26 | JVM exited in response to signal SIGKILL (9).
FATAL | wrapper | 2013/08/01 19:56:26 | There were 1 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2013/08/01 19:56:26 | There may be a configuration problem: please check the logs.
STATUS | wrapper | 2013/08/01 19:56:26 | <-- Wrapper Stopped
It's an empty file, /var/lib/apacheds-2.0.0-M14/default/log/apacheds.log
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira