[
https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728723#comment-13728723
]
Frank Ren commented on DIRSERVER-1880:
--------------------------------------
Thank you, Pierre.
First, it's not a slow machine/VM.
* CPU: Intel i7
* RAM: 16 GB
* DISK: two 7200 rpm disks formed Raid 0
ApacheDS used to start automatically. But, recently it didn't. If I start it
manually with
sudo service apacheds-2.0.0-M11-default start
It won't take long - the same amount of time it used to take to start.
The only problem is ApacheDS stopped auto starting at boot.
Secondly, I've increased the timeout from 240 to 2400. It didn't help. Just as
I said it won't take longer to start ApacheDS manually. So, I don't think it
was really a timeout that occurred. Perhaps, it was ApacheDS was trying to
locate something that was change recently, and no longer available. It's only
my guess.
Can you or someone else show me another direction? Does anyone experience the
same problem recently? Thanks
b.t.w. I also tested it with the following three setups (all os updated with
sudo aptitude safe-upgrade)
* M11 on an EC2 instance of Ubuntu 12.04 server doesn't auto start.
* M14 on an EC2 instance of Ubuntu 12.04 server doesn't auto start. (timeout
240 and 2400)
* M14 on an EC2 instance of Ubuntu 10.04 server doesn't auto start.
> 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
