4 Replies Latest reply on Jun 29, 2017 10:29 PM by Abhijit Humbe

    JBAS015986 Host Controller shutdown has been requested via an OS signal

    Qadeer Khan Newbie

      We are using EAP 6.4.11 in standalone mode (not domain mode) and on couple of servers, EAP shuts down by itself on startup. Jboss is started as a service.

       

      There is an INFO message in the server.log file  "JBAS015986: Host Controller shutdown has been requested via an OS signal."

       

      This behavior is inconsistent though as sometimes the server starts straightaway and sometimes it requires several attempts (6-8).

       

      There are other servers with exactly the same configuration where there is no problem starting the EAP servers

       

      Any insights?

       

      Thanks

        • 1. Re: JBAS015986 Host Controller shutdown has been requested via an OS signal
          Abhijit Humbe Master

          Have you checked /var/log/messages file and see if OOMkiller has send shutdown signal . JVM crash can also cause such issues, check for hs_err_pid file in filesystem.

          To avoid JBoss shutdown because of the OS signal you can add -Xrs JVM option in standalone.conf file.

          • 2. Re: JBAS015986 Host Controller shutdown has been requested via an OS signal
            Qadeer Khan Newbie

            These are the messages regarding the Jboss EAP shutdown from

            /var/log/message

             

            Jun 26 09:14:04 MCR-JRN-FUSE01 jboss-as-standalone.sh: Starting jboss-as: /

             

            Jun 26 09:15:34 MCR-JRN-FUSE01 systemd: jboss-as.service start operation

            timed out. Terminating.

             

            Jun 26 09:15:34 MCR-JRN-FUSE01 systemd: Unit jboss-as.service entered

            failed state.

             

            Jun 26 09:15:34 MCR-JRN-FUSE01 systemd: jboss-as.service failed.

             

            Jun 26 09:15:52 MCR-JRN-FUSE01 jboss-as-standalone.sh: Starting jboss-as: /

             

            Jun 26 09:17:22 MCR-JRN-FUSE01 systemd: jboss-as.service start operation

            timed out. Terminating.

             

            Jun 26 09:17:22 MCR-JRN-FUSE01 systemd: Unit jboss-as.service entered

            failed state.

             

            Jun 26 09:17:22 MCR-JRN-FUSE01 systemd: jboss-as.service failed.

             

            Jun 26 09:18:01 MCR-JRN-FUSE01 jboss-as-standalone.sh: Starting jboss-as: /

             

            Jun 26 09:19:17 MCR-JRN-FUSE01 jboss-as-standalone.sh:

            Jun 26 09:19:17 MCR-JRN-FUSE01 systemd: jboss-as.service: Supervising

            process 28823 which is not our child. We'll most likely not notice when it

            exits.

             

            It does not look like  OOMkiller sending a shutdown signal. I also looked

            for hs_err_pid file and could not find one.

             

             

            Regarding using -Xrs option, is there any downside?

             

            Thanks

             

            On Tue, Jun 27, 2017 at 9:17 AM, abhijithumbe <do-not-reply@jboss.com>

            • 3. Re: JBAS015986 Host Controller shutdown has been requested via an OS signal
              Qadeer Khan Newbie

              We tried starting the service after adding -Xrs JVM option in standalone.conf file but there was no difference we still continued to have the same problem i.e. EAP starts after several failed attempts

              • 4. Re: JBAS015986 Host Controller shutdown has been requested via an OS signal
                Abhijit Humbe Master

                Looks like server is taking more time to start than default value specified in jboss-as-standalone.sh script. Can you increase default statup wait time by modifying startup script. In sh file update value of  'STARTUP_WAIT'  parameter reload the systemctl service and try to start server instance.