Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13984

[GSS](7.0.z) Startup error when started as system service

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.0.3.GA, 7.1.0.DR7
    • Scripts
    • None
    • Compatibility/Configuration, User Experience
    • +
    • Workaround Exists
    • Hide

      If JBOSS_HOME and jboss.server.base.dir have different locations the jboss-eap-rhel.sh can be adapted to expect the startup-marker file at the correct location.

      Show
      If JBOSS_HOME and jboss.server.base.dir have different locations the jboss-eap-rhel.sh can be adapted to expect the startup-marker file at the correct location.
    • Hide

      To reproduce use the following steps (even without using it as system service):
      1.) Install EAP7 CP03 to /app/product/jboss-eap-7.0
      2.) create a folder /app/instance/example-standalone-instance
      3.) copy standard standalone folder cp -a /app/product/jboss-eap-7.0/standalone/ /app/instance/example-instance
      4.) Edit /app/product/jboss-eap-7.0/bin/init.d/jboss-eap.conf and set:

      • JBOSS_HOME="/app/product/jboss-eap-7.0"
      • JBOSS_USER="<your user>"
      • JBOSS_MODE="standalone"
      • STARTUP_WAIT=5
      • JBOSS_OPTS="-Djboss.server.base.dir=/app/instance/example-instance/standalone"
      • JBOSS_PIDFILE="/app/instance/example-instance/example-standalone-instance.pid"
      • JBOSS_CONSOLE_LOG="/app/instance/example-instance/console.log"
      • JBOSS_LOCKFILE="/app/instance/example-instance/lock"

      5.) Change into root environment (e. g. sudo su)
      6.) export JBOSS_CONF='/app/product/jboss-eap-7.0/bin/init.d/jboss-eap.conf'
      7.) start the script (/app/product/jboss-eap-7.0/bin/init.d/jboss-eap-rhel.sh start)

      You'll see an indication of a start with errors, see:

      Starting jboss-eap: /home/jbaesner
      jboss-eap started with errors, please see server log for details
      [ OK ]

      But if you look into /app/instance/example-instance/console.log, you can notice that the server has started successfully:

      4:44:30,661 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.3.GA (WildFly Core 2.1.9.Final-redhat-1) started in 2380ms - Started 268 of 554 services (372 services are lazy, passive or on-demand)

      And the startup-marker file is created in /app/instance/example-instance/standalone/tmp/

      But jboss-eap-rhel.sh expectes the file in JBOSS_MARKERFILE=$JBOSS_HOME/standalone/tmp/startup-marker (line 71)

      Show
      To reproduce use the following steps (even without using it as system service): 1.) Install EAP7 CP03 to /app/product/jboss-eap-7.0 2.) create a folder /app/instance/example-standalone-instance 3.) copy standard standalone folder cp -a /app/product/jboss-eap-7.0/standalone/ /app/instance/example-instance 4.) Edit /app/product/jboss-eap-7.0/bin/init.d/jboss-eap.conf and set: JBOSS_HOME="/app/product/jboss-eap-7.0" JBOSS_USER="<your user>" JBOSS_MODE="standalone" STARTUP_WAIT=5 JBOSS_OPTS="-Djboss.server.base.dir=/app/instance/example-instance/standalone" JBOSS_PIDFILE="/app/instance/example-instance/example-standalone-instance.pid" JBOSS_CONSOLE_LOG="/app/instance/example-instance/console.log" JBOSS_LOCKFILE="/app/instance/example-instance/lock" 5.) Change into root environment (e. g. sudo su ) 6.) export JBOSS_CONF='/app/product/jboss-eap-7.0/bin/init.d/jboss-eap.conf' 7.) start the script ( /app/product/jboss-eap-7.0/bin/init.d/jboss-eap-rhel.sh start ) You'll see an indication of a start with errors, see: Starting jboss-eap: /home/jbaesner jboss-eap started with errors, please see server log for details [ OK ] But if you look into /app/instance/example-instance/console.log , you can notice that the server has started successfully: 4:44:30,661 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.3.GA (WildFly Core 2.1.9.Final-redhat-1) started in 2380ms - Started 268 of 554 services (372 services are lazy, passive or on-demand) And the startup-marker file is created in /app/instance/example-instance/standalone/tmp/ But jboss-eap-rhel.sh expectes the file in JBOSS_MARKERFILE=$JBOSS_HOME/standalone/tmp/startup-marker (line 71)

      If a JBoss EAP7 instance will be started as a system service and the JBOSS_HOME location differs from 'jboss.server.base.dir' the jboss-eap-rhel.sh script does not detect a successful server start, cause it's expecting the 'startup-marker' file in the wrong location.

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified