Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-M14
    • Fix Version/s: 2.0.0-M15
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      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

        Activity

        Hide
        Pierre-Arnaud Marcelot added a comment -

        It's most likely the server took too much time to start (slow machine/VM?) and the wrapper killed it.

        You can try to increase the "wrapper.ping.timeout" parameter of the wrapper in the "wrapper.conf" file from the "conf" directory of the ApacheDS installation.
        (See http://directory.apache.org/apacheds/advanced-ug/5.1-layout.html)

        You may also switch to Oracle's JVM.

        Hope this helps.

        Show
        Pierre-Arnaud Marcelot added a comment - It's most likely the server took too much time to start (slow machine/VM?) and the wrapper killed it. You can try to increase the "wrapper.ping.timeout" parameter of the wrapper in the "wrapper.conf" file from the "conf" directory of the ApacheDS installation. (See http://directory.apache.org/apacheds/advanced-ug/5.1-layout.html ) You may also switch to Oracle's JVM. Hope this helps.
        Hide
        Frank Ren added a comment -

        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.
        Show
        Frank Ren added a comment - 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.
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Hi Frank,

        So, ApacheDS does start, but only manually, right?

        Could you use the log4.properties from this jira issue, DIRSERVER-1871?
        https://issues.apache.org/jira/browse/DIRSERVER-1871?focusedCommentId=13718593&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13718593

        In the meantime, I'll experiment on a Ubuntu VM to see if I can reproduce the issue.

        Thanks.

        Show
        Pierre-Arnaud Marcelot added a comment - Hi Frank, So, ApacheDS does start, but only manually, right? Could you use the log4.properties from this jira issue, DIRSERVER-1871 ? https://issues.apache.org/jira/browse/DIRSERVER-1871?focusedCommentId=13718593&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13718593 In the meantime, I'll experiment on a Ubuntu VM to see if I can reproduce the issue. Thanks.
        Hide
        Frank Ren added a comment -

        I'll try with the log4j config, and attach the log file. Thanks.

        On Mon, Aug 5, 2013 at 7:58 PM, Pierre-Arnaud Marcelot (JIRA) <

        Show
        Frank Ren added a comment - I'll try with the log4j config, and attach the log file. Thanks. On Mon, Aug 5, 2013 at 7:58 PM, Pierre-Arnaud Marcelot (JIRA) <
        Hide
        Radoslaw Kujawa added a comment -

        Frank Ren I had same problem as you, but adding "wrapper.startup.timeout=120" line solved my problem. Keep in mind that it is not ping timeout setting but startup timeout setting.

        Cheers,
        Radoslaw Kujawa

        Show
        Radoslaw Kujawa added a comment - Frank Ren I had same problem as you, but adding "wrapper.startup.timeout=120" line solved my problem. Keep in mind that it is not ping timeout setting but startup timeout setting. Cheers, Radoslaw Kujawa
        Hide
        Frank Ren added a comment -

        Thank you, Radoslaw. I'll check it out.

        Show
        Frank Ren added a comment - Thank you, Radoslaw. I'll check it out.
        Hide
        Frank Ren added a comment -

        Hi, Radoslaw. I've confirmed that it solves the problem by setting
        wrapper.startup.timeout=120. Thanks again.

        I'd like to suggest it be taken as a default property in wrapper.conf.

        Show
        Frank Ren added a comment - Hi, Radoslaw. I've confirmed that it solves the problem by setting wrapper.startup.timeout=120. Thanks again. I'd like to suggest it be taken as a default property in wrapper.conf.
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Agreed and just committed.

        Show
        Pierre-Arnaud Marcelot added a comment - Agreed and just committed.
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Fixed at revision 1512266.

        http://svn.apache.org/r1512266

        Show
        Pierre-Arnaud Marcelot added a comment - Fixed at revision 1512266. http://svn.apache.org/r1512266

          People

          • Assignee:
            Pierre-Arnaud Marcelot
            Reporter:
            Frank Ren
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development