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

[GSS](7.2.0) Startup error when started as system service

    XMLWordPrintable

Details

    • Documentation (Ref Guide, User Guide, etc.), 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)

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1383 Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7391 The "JBOSS_MARKERFILE" in "jboss-eap-rhel.sh" doesn't work.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12932 Upgrade WildFly Core to 4.0.1.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18778 Startup error when started as system service

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5374 Missing productization changes on scripts

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1766 Scripts for running EAP as service on Windows is missing

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-2078 Scripts for running EAP as service on RHEL are missing

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rhn-engineering-lgao Lin Gao
              rhn-support-jbaesner Joerg Baesner
              Votes:
              1 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

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