4 Replies Latest reply on Mar 12, 2018 12:39 PM by Jan Kalina

    Help getting server to start

    Jon vrabel Newbie

      Hey Group,

       

      First off let me apologize, I'm super new to Wildfly and my engineer left with little to no documentation. I have several AWS servers running on AWS and this one controlling some of the UI and things like swagger and ssl etc.. When I try to start wildfly server with standalone, I get several errors.  I've reverted the standalone.xml file back to how it was before I edited the ssl cert info and its still not starting.  I simply wanted to update the expired ssl signed jsk cert and restart. These are the errors I'm getting. Any help would be appreciated.

       

      Wildfly 8.2.0

       

      04:08:39,159 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.server.controller.management.security_realm.SslRealm.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.SslRealm.key-manager: JBAS015229: Unable to start service

        at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:154)

        at org.jboss.as.domain.management.security.FileKeyManagerService.start(FileKeyManagerService.java:119)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]

      Caused by: java.io.IOException: Invalid keystore format

        at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) [rt.jar:1.8.0_31]

        at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) [rt.jar:1.8.0_31]

        at java.security.KeyStore.load(KeyStore.java:1433) [rt.jar:1.8.0_31]

        at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:113)

        ... 6 more

       

      04:08:39,185 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "PerigonWebService.war" (runtime-name: "PerigonWebService.war")

      04:08:39,208 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/ec2-user/apps/wildfly/wildfly-8.2.0.Final/standalone/deployments

      04:08:39,359 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      ^C04:08:42,177 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]

      04:08:42,178 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping

      04:08:42,212 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2

      04:08:42,216 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017521: Undertow HTTP listener default suspending

      04:08:42,217 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080

      04:08:42,220 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017506: Undertow 1.1.0.Final stopping

      04:08:45,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."PerigonWebService.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."PerigonWebService.war".STRUCTURE: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]

      Caused by: java.lang.IllegalStateException: Container is down

        at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:715) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:208) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

       

      04:08:45,029 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment PerigonWebService.war (runtime-name: PerigonWebService.war) in 2922ms

      04:08:45,071 WARN  [org.jboss.as.logging] (Controller Boot Thread) JBAS011507: The path manager service does not appear to be started. Any changes may be lost as a result of this.

      04:08:45,083 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "PerigonWebService.war" (runtime-name : "PerigonWebService.war")

      04:08:45,088 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: java.util.concurrent.RejectedExecutionException: Task org.jboss.as.controller.notification.NotificationSupports$NonBlockingNotificationSupport$1@45688c15 rejected from java.util.concurrent.ThreadPoolExecutor@6d888f7[Shutting down, pool size = 49, active threads = 49, queued tasks = 0, completed tasks = 51]

        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) [rt.jar:1.8.0_31]

        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) [rt.jar:1.8.0_31]

        at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) [rt.jar:1.8.0_31]

        at org.jboss.as.controller.notification.NotificationSupports$NonBlockingNotificationSupport.emit(NotificationSupports.java:95) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.emitNotifications(AbstractOperationContext.java:604) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:587) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:298) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:752) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:727) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:501) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:298) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:293) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:346) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:297) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]

       

      04:08:45,092 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 2984ms

      04:08:45,093 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

        • 1. Re: Help getting server to start
          jaikiran pai Master

          The standalone/configuration/standalone_xml_history/ directory under your WildFly installation directory would have one or more (auto) backed up standalone configuration files. Before doing anything, copy those over to some place and then checkout which one of those is the most relevant in your case and replace the existing standalone configuration with that one.

          • 2. Re: Help getting server to start
            Jon vrabel Newbie

            Thanks you for your reply!

             

            The first thing I did before trying to replace the jsk was save the expired jsk and standalone.xml local to my Mac.  On the new standalone all I changed was the cert name and alias.  Once the server had issues I reverted back to the expired cert and standalone.xml.  Server still the these errors. I’m not even sure how to create a .war file and if the jars in their are outdated?

             

            Sent from my iPhone

            • 3. Re: Help getting server to start
              Wolfgang Mayer Master

              The message is: Invalid keystore format

               

              Did you verify that the KeyStore file is correct?

              $JAVA_HOME/bin/keytool -list -keystore keystore

               

              • 4. Re: Help getting server to start
                Jan Kalina Newbie

                From the stacktrace it looks your keystore file is broken - maybe you have not restored the keystore file from backup? Is the original keystore file on place?

                Otherwise I would check keystore file format (is it really JKS) and whether it corresponds to what is set in standalone.xml:

                <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx" provider="PKCS12"/>

                The example above is for PKCS12 type of keystore (provider) - if you have really generated JKS, you should be able to omit provider param.