6 Replies Latest reply on Sep 7, 2015 8:26 AM by Florian Reiser

    What services failed when starting?

    Florian Reiser Newbie

      Hello,

       

      I am using wildfly 8.2.0.Final and see the following log message in server.log: Tweek started (9 services failed, ...)

      However I do not see any other errors in the log which could explain the message.

       

      How can I query wildfly for the services, which failed to start?

       

      With kind regards

       

      Florian

        • 1. Re: What services failed when starting?
          tomekadamski Novice

          Hi Florian,

          Can you paste the whole server.log which is generated during server startup?

           

          Regards,

          Tomek

          • 2. Re: What services failed when starting?
            Florian Reiser Newbie

            Hello Tomasz,

             

            sorry for taking so long.

             

            The server log:

            [0m10:45:01,188 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
            [0m [0m10:45:01,998 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
            [0m [0m10:45:02,085 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
            [0m [32m10:45:02,088 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties:
              [Standalone] =
              admin.port = 8490
              awt.toolkit = sun.awt.X11.XToolkit
              file.encoding = UTF-8
              file.encoding.pkg = sun.io
              file.separator = /
              java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
              java.awt.headless = true
              java.awt.printerjob = sun.print.PSPrinterJob
              java.class.path = /opt/wildfly/jboss-modules.jar
              java.class.version = 52.0
              java.endorsed.dirs = /usr/java/jdk1.8.0_51/jre/lib/endorsed
              java.ext.dirs = /usr/java/jdk1.8.0_51/jre/lib/ext:/usr/java/packages/lib/ext
              java.home = /usr/java/jdk1.8.0_51/jre
              java.io.tmpdir = /tmp
              java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
              java.net.preferIPv4Stack = true
              java.runtime.name = Java(TM) SE Runtime Environment
              java.runtime.version = 1.8.0_51-b16
              java.specification.name = Java Platform API Specification
              java.specification.vendor = Oracle Corporation
              java.specification.version = 1.8
              java.util.logging.manager = org.jboss.logmanager.LogManager
              java.vendor = Oracle Corporation
              java.vendor.url = http://java.oracle.com/
              java.vendor.url.bug = http://bugreport.sun.com/bugreport/
              java.version = 1.8.0_51
              java.vm.info = mixed mode
              java.vm.name = Java HotSpot(TM) 64-Bit Server VM
              java.vm.specification.name = Java Virtual Machine Specification
              java.vm.specification.vendor = Oracle Corporation
              java.vm.specification.version = 1.8
              java.vm.vendor = Oracle Corporation
              java.vm.version = 25.51-b03
              javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
              javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
              javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
              javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
              javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
              javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
              javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
              javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
              javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
              javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
              jboss.bind.address.management = 127.0.0.1
              jboss.bind.address.public = 0.0.0.0
              jboss.home.dir = /opt/wildfly
              jboss.host.name = unknown-host
              jboss.modules.dir = /opt/wildfly/modules
              jboss.modules.system.pkgs = org.jboss.byteman
              jboss.node.name = unknown-host
              jboss.qualified.host.name = unknown-host.unknown-domain
              jboss.server.base.dir = /opt/wildfly/standalone
              jboss.server.config.dir = /opt/wildfly/standalone/configuration
              jboss.server.data.dir = /opt/wildfly/standalone/data
              jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
              jboss.server.log.dir = /opt/wildfly/standalone/log
              jboss.server.name = unknown-host
              jboss.server.persist.config = true
              jboss.server.temp.dir = /opt/wildfly/standalone/tmp
              jndi.defaultPerPageEntriesAdminGui = 20
              line.separator =
            
            
              log.level = INFO
              log.level.console = INFO
              logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
              module.path = /opt/wildfly/modules
              org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
              org.jboss.resolver.warning = true
              org.xml.sax.driver = __redirected.__XMLReaderFactory
              os.arch = amd64
              os.name = Linux
              os.version = 3.10.0-229.el7.x86_64
              path.separator = :
              ssl-client-cert.keystore = server-ssl.keystore
              ssl-client-cert.keystore.alias = alias_name
              ssl-client-cert.keystore.password = keystore
              ssl-client-cert.port = 8453
              ssl-client-cert.truststore = server-truststore.keystore
              ssl-client-cert.truststore.password = keystore
              ssl-only.keystore = server-ssl.keystore
              ssl-only.keystore.alias = alias_name
              ssl-only.keystore.password = keystore
              ssl-only.port = 8443
              sun.arch.data.model = 64
              sun.boot.class.path = /usr/java/jdk1.8.0_51/jre/lib/resources.jar:/usr/java/jdk1.8.0_51/jre/lib/rt.jar:/usr/java/jdk1.8.0_51/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_51/jre/lib/jsse.jar:/usr/java/jdk1.8.0_51/jre/lib/jce.jar:/usr/java/jdk1.8.0_51/jre/lib/charsets.jar:/usr/java/jdk1.8.0_51/jre/lib/jfr.jar:/usr/java/jdk1.8.0_51/jre/classes
              sun.boot.library.path = /usr/java/jdk1.8.0_51/jre/lib/amd64
              sun.cpu.endian = little
              sun.cpu.isalist =
              sun.io.unicode.encoding = UnicodeLittle
              sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml --properties=/opt/wildfly/standalone/configuration/security-suite-standalone.properties
              sun.java.launcher = SUN_STANDARD
              sun.jnu.encoding = UTF-8
              sun.management.compiler = HotSpot 64-Bit Tiered Compilers
              sun.os.patch.level = unknown
              user.country = CH
              user.dir = /
              user.home = /opt/wildfly
              user.language = de
              user.name = wildfly
              user.timezone = Europe/Zurich
            [0m [32m10:45:02,090 DEBUG [org.jboss.as.config] (MSC service thread 1-2) VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties
            [0m [0m10:45:05,049 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
            [0m [0m10:45:05,080 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final
            [0m [0m10:45:05,085 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final
            [0m [0m10:45:05,171 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) JBAS010280: Activating Infinispan subsystem.
            [0m [0m10:45:05,333 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 29) JBAS011800: Activating Naming Subsystem
            [0m [0m10:45:05,311 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 34) JBAS013171: Activating Security Subsystem
            [0m [33m10:45:05,311 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 35) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
            [0m [0m10:45:05,361 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.6.Final
            [0m [0m10:45:05,448 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 23) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
            [0m [0m10:45:05,504 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 20) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
            [0m [0m10:45:05,557 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.21.Final
            [0m [0m10:45:05,609 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
            [0m [0m10:45:05,629 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 36) JBAS017502: Undertow 1.1.0.Final starting
            [0m [0m10:45:05,660 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 20) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.3)
            [0m [0m10:45:05,719 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.1.0.Final starting
            [0m [0m10:45:05,722 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2
            [0m [0m10:45:05,787 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
            [0m [0m10:45:05,790 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = postgres
            [0m [0m10:45:06,004 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 36) JBAS017527: Creating file handler for path /opt/wildfly/welcome-content
            [0m [0m10:45:06,185 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server ssl-client-cert-server.
            [0m [0m10:45:06,185 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server ssl-only-server.
            [0m [0m10:45:06,185 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.
            [0m [0m10:45:06,185 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server admin-server.
            [0m [33m10:45:06,326 WARN  [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
            [0m [0m10:45:06,373 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
            [0m [0m10:45:06,388 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
            [0m [0m10:45:06,458 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "lukbpoc.war" (runtime-name: "lukbpoc.war")
            [0m [0m10:45:06,459 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "fido.ear" (runtime-name: "fido.ear")
            [0m [0m10:45:06,460 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "web.ear" (runtime-name: "web.ear")
            [0m [0m10:45:09,569 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "dao-impl.jar")
            [0m [0m10:45:09,569 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "fido-war.war")
            [0m [0m10:45:09,570 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "services-impl.jar")
            [0m [0m10:45:09,623 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener ssl-client-cert-https listening on /0.0.0.0:8453
            [0m [0m10:45:09,633 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener admin-https listening on /0.0.0.0:8490
            [0m [0m10:45:09,635 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener ssl-only-https listening on /0.0.0.0:8443
            [0m [0m10:45:09,636 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener default-https listening on /0.0.0.0:8090
            [0m [0m10:45:09,979 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "mobile-war.war")
            [0m [0m10:45:09,980 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "server-services.jar")
            [0m [0m10:45:09,980 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "auth-dao.jar")
            [0m [0m10:45:09,981 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "selfcare-war.war")
            [0m [0m10:45:09,981 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "certificate-services.jar")
            [0m [0m10:45:09,981 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "auth-services.jar")
            [0m [0m10:45:09,981 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015973: Starting subdeployment (runtime-name: "admin-war.war")
            [0m [0m10:45:10,483 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for fido-pu
            [0m [0m10:45:10,504 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/fidoDb]
            [0m [0m10:45:10,730 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for twofaPU
            [0m [0m10:45:10,739 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/twofaDb]
            [0m [0m10:45:10,733 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
            [0m [0m10:45:11,630 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment web.ear
            [0m [0m10:45:11,641 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 38) JBAS011409: Starting Persistence Unit (phase 1 of 2) Service 'fido.ear#fido-pu'
            [0m [0m10:45:11,723 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 38) HHH000204: Processing PersistenceUnitInfo [
              name: fido-pu
              ...]
            [0m [0m10:45:11,955 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 39) JBAS011409: Starting Persistence Unit (phase 1 of 2) Service 'web.ear/auth-dao.jar#twofaPU'
            [0m [0m10:45:11,955 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 39) HHH000204: Processing PersistenceUnitInfo [
              name: twofaPU
              ...]
            [0m [0m10:45:12,180 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
            [0m [0m10:45:12,263 INFO  [org.hibernate.Version] (ServerService Thread Pool -- 38) HHH000412: Hibernate Core {4.3.7.Final}
            [0m [0m10:45:12,288 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 38) HHH000206: hibernate.properties not found
            [0m [0m10:45:12,332 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 38) HHH000021: Bytecode provider name : javassist
            [0m [0m10:45:12,345 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final
            [0m [0m10:45:12,541 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment fido.ear
            [0m [0m10:45:12,675 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment auth-dao.jar
            [0m [0m10:45:12,678 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ValidationTokenStore in deployment unit subdeployment "auth-dao.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/auth-dao/ValidationTokenStore!ch.ti8m.security.twofa.server.authentication.ValidationTokenStore
              java:app/auth-dao/ValidationTokenStore!ch.ti8m.security.twofa.server.authentication.ValidationTokenStore
              java:module/ValidationTokenStore!ch.ti8m.security.twofa.server.authentication.ValidationTokenStore
              java:global/ti8m secure web module/auth-dao/ValidationTokenStore
              java:app/auth-dao/ValidationTokenStore
              java:module/ValidationTokenStore
            
            
            [0m [0m10:45:12,678 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named DeviceInformationStore in deployment unit subdeployment "auth-dao.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/auth-dao/DeviceInformationStore!ch.ti8m.security.twofa.server.authentication.DeviceInformationStore
              java:app/auth-dao/DeviceInformationStore!ch.ti8m.security.twofa.server.authentication.DeviceInformationStore
              java:module/DeviceInformationStore!ch.ti8m.security.twofa.server.authentication.DeviceInformationStore
              java:global/ti8m secure web module/auth-dao/DeviceInformationStore
              java:app/auth-dao/DeviceInformationStore
              java:module/DeviceInformationStore
            
            
            [0m [0m10:45:12,682 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment selfcare-war.war
            [0m [0m10:45:12,740 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /lukbpoc
            [0m [0m10:45:12,743 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment server-services.jar
            [0m [0m10:45:12,744 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named AuthServerServiceImpl in deployment unit subdeployment "server-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/server-services/AuthServerServiceImpl!ch.ti8m.security.twofa.server.server.AuthServerService
              java:app/server-services/AuthServerServiceImpl!ch.ti8m.security.twofa.server.server.AuthServerService
              java:module/AuthServerServiceImpl!ch.ti8m.security.twofa.server.server.AuthServerService
              java:global/ti8m secure web module/server-services/AuthServerServiceImpl
              java:app/server-services/AuthServerServiceImpl
              java:module/AuthServerServiceImpl
            
            
            [0m [0m10:45:12,745 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment mobile-war.war
            [0m [0m10:45:12,789 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment admin-war.war
            [0m [0m10:45:12,997 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment auth-services.jar
            [0m [0m10:45:12,998 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named AuthService in deployment unit subdeployment "auth-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/auth-services/AuthService!ch.ti8m.security.twofa.server.authentication.AuthService
              java:app/auth-services/AuthService!ch.ti8m.security.twofa.server.authentication.AuthService
              java:module/AuthService!ch.ti8m.security.twofa.server.authentication.AuthService
              java:global/ti8m secure web module/auth-services/AuthService
              java:app/auth-services/AuthService
              java:module/AuthService
            
            
            [0m [0m10:45:12,998 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RequestTokenCache in deployment unit subdeployment "auth-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/auth-services/RequestTokenCache!ch.ti8m.security.twofa.server.authentication.RequestTokenCache
              java:app/auth-services/RequestTokenCache!ch.ti8m.security.twofa.server.authentication.RequestTokenCache
              java:module/RequestTokenCache!ch.ti8m.security.twofa.server.authentication.RequestTokenCache
              java:global/ti8m secure web module/auth-services/RequestTokenCache
              java:app/auth-services/RequestTokenCache
              java:module/RequestTokenCache
            
            
            [0m [0m10:45:13,022 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment dao-impl.jar
            [0m [0m10:45:13,023 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named U2FKeyStorageImpl in deployment unit subdeployment "dao-impl.jar" of deployment "fido.ear" are as follows:
            
            
              java:global/fido/dao-impl/U2FKeyStorageImpl!ch.ti8m.security.fido.server.storage.U2FKeyStorage
              java:app/dao-impl/U2FKeyStorageImpl!ch.ti8m.security.fido.server.storage.U2FKeyStorage
              java:module/U2FKeyStorageImpl!ch.ti8m.security.fido.server.storage.U2FKeyStorage
              java:global/fido/dao-impl/U2FKeyStorageImpl
              java:app/dao-impl/U2FKeyStorageImpl
              java:module/U2FKeyStorageImpl
            
            
            [0m [0m10:45:13,023 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ChallengeDataStorageImpl in deployment unit subdeployment "dao-impl.jar" of deployment "fido.ear" are as follows:
            
            
              java:global/fido/dao-impl/ChallengeDataStorageImpl!ch.ti8m.security.fido.server.storage.ChallengeDataStorage
              java:app/dao-impl/ChallengeDataStorageImpl!ch.ti8m.security.fido.server.storage.ChallengeDataStorage
              java:module/ChallengeDataStorageImpl!ch.ti8m.security.fido.server.storage.ChallengeDataStorage
              java:global/fido/dao-impl/ChallengeDataStorageImpl
              java:app/dao-impl/ChallengeDataStorageImpl
              java:module/ChallengeDataStorageImpl
            
            
            [0m [0m10:45:13,023 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named PendingRegistrationStorageImpl in deployment unit subdeployment "dao-impl.jar" of deployment "fido.ear" are as follows:
            
            
              java:global/fido/dao-impl/PendingRegistrationStorageImpl!ch.ti8m.security.fido.server.storage.PendingRegistrationStorage
              java:app/dao-impl/PendingRegistrationStorageImpl!ch.ti8m.security.fido.server.storage.PendingRegistrationStorage
              java:module/PendingRegistrationStorageImpl!ch.ti8m.security.fido.server.storage.PendingRegistrationStorage
              java:global/fido/dao-impl/PendingRegistrationStorageImpl
              java:app/dao-impl/PendingRegistrationStorageImpl
              java:module/PendingRegistrationStorageImpl
            
            
            [0m [0m10:45:13,032 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment certificate-services.jar
            [0m [0m10:45:13,033 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named KeyStoreProvider in deployment unit subdeployment "certificate-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/certificate-services/KeyStoreProvider!ch.ti8m.security.twofa.server.certificates.helpers.KeyStoreProvider
              java:app/certificate-services/KeyStoreProvider!ch.ti8m.security.twofa.server.certificates.helpers.KeyStoreProvider
              java:module/KeyStoreProvider!ch.ti8m.security.twofa.server.certificates.helpers.KeyStoreProvider
              java:global/ti8m secure web module/certificate-services/KeyStoreProvider
              java:app/certificate-services/KeyStoreProvider
              java:module/KeyStoreProvider
            
            
            [0m [0m10:45:13,033 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named CertificateService in deployment unit subdeployment "certificate-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/certificate-services/CertificateService!ch.ti8m.security.twofa.server.certificates.CertificateService
              java:app/certificate-services/CertificateService!ch.ti8m.security.twofa.server.certificates.CertificateService
              java:module/CertificateService!ch.ti8m.security.twofa.server.certificates.CertificateService
              java:global/ti8m secure web module/certificate-services/CertificateService
              java:app/certificate-services/CertificateService
              java:module/CertificateService
            
            
            [0m [0m10:45:13,033 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named CaProvider in deployment unit subdeployment "certificate-services.jar" of deployment "web.ear" are as follows:
            
            
              java:global/ti8m secure web module/certificate-services/CaProvider!ch.ti8m.security.twofa.server.certificates.helpers.CaProvider
              java:app/certificate-services/CaProvider!ch.ti8m.security.twofa.server.certificates.helpers.CaProvider
              java:module/CaProvider!ch.ti8m.security.twofa.server.certificates.helpers.CaProvider
              java:global/ti8m secure web module/certificate-services/CaProvider
              java:app/certificate-services/CaProvider
              java:module/CaProvider
            
            
            [0m [0m10:45:13,037 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment fido-war.war
            [0m [0m10:45:13,120 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: web.ear
            [0m [0m10:45:13,124 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment services-impl.jar
            [0m [0m10:45:13,125 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named BouncyCastleCrypto in deployment unit subdeployment "services-impl.jar" of deployment "fido.ear" are as follows:
            
            
              java:global/fido/services-impl/BouncyCastleCrypto!ch.ti8m.security.fido.server.services.impl.util.Crypto
              java:app/services-impl/BouncyCastleCrypto!ch.ti8m.security.fido.server.services.impl.util.Crypto
              java:module/BouncyCastleCrypto!ch.ti8m.security.fido.server.services.impl.util.Crypto
              java:global/fido/services-impl/BouncyCastleCrypto
              java:app/services-impl/BouncyCastleCrypto
              java:module/BouncyCastleCrypto
            
            
            [0m [0m10:45:13,125 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named FidoServiceImpl in deployment unit subdeployment "services-impl.jar" of deployment "fido.ear" are as follows:
            
            
              java:global/fido/services-impl/FidoServiceImpl!ch.ti8m.security.fido.server.services.FidoService
              java:app/services-impl/FidoServiceImpl!ch.ti8m.security.fido.server.services.FidoService
              java:module/FidoServiceImpl!ch.ti8m.security.fido.server.services.FidoService
              java:global/fido/services-impl/FidoServiceImpl
              java:app/services-impl/FidoServiceImpl
              java:module/FidoServiceImpl
            
            
            [0m [0m10:45:13,164 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: fido.ear
            [0m [0m10:45:13,309 INFO  [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.2.6 (Final)
            [0m [0m10:45:13,644 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment fido.ear
            [0m [0m10:45:13,712 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment web.ear
            [0m [0m10:45:13,954 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 39) JBAS011409: Starting Persistence Unit (phase 2 of 2) Service 'web.ear/auth-dao.jar#twofaPU'
            [0m [0m10:45:13,962 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 38) JBAS011409: Starting Persistence Unit (phase 2 of 2) Service 'fido.ear#fido-pu'
            [0m [0m10:45:14,414 INFO  [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 39) HCANN000001: Hibernate Commons Annotations {4.0.4.Final}
            [0m [0m10:45:15,073 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 39) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
            [0m [0m10:45:15,081 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (ServerService Thread Pool -- 39) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
            [0m [0m10:45:15,109 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 38) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
            [0m [0m10:45:15,110 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (ServerService Thread Pool -- 38) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
            [0m [0m10:45:15,300 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 39) HHH000397: Using ASTQueryTranslatorFactory
            [0m [0m10:45:15,347 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 38) HHH000397: Using ASTQueryTranslatorFactory
            [0m [0m10:45:18,006 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class ch.ti8m.security.fido.server.fido.appl.FidoApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,009 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource ch.ti8m.security.fido.server.fido.FidoEndpoint from Application class ch.ti8m.security.fido.server.fido.appl.FidoApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,010 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class ch.ti8m.security.utils.exceptions.IllegalArgumentExceptionMapper from Application class ch.ti8m.security.fido.server.fido.appl.FidoApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,029 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,051 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.InvalidPermissionExceptionMapper from Application class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,051 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.admingui.exceptions.BadRequestExceptionMapper from Application class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,051 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.IllegalArgumentExceptionMapper from Application class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,051 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.EJBTransactionRolledbackExceptionMapper from Application class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,051 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource ch.ti8m.security.twofa.server.admin.endpoints.AdminEndpoint from Application class ch.ti8m.security.twofa.server.admin.AdminApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,100 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /fido/u2f
            [0m [0m10:45:18,137 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class ch.ti8m.security.twofa.server.selfcare.SelfCareApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,139 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /web/admin
            [0m [0m10:45:18,176 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource ch.ti8m.security.twofa.server.selfcare.endpoints.SelfCareEndpoint from Application class ch.ti8m.security.twofa.server.selfcare.SelfCareApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,176 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class ch.ti8m.security.utils.exceptions.InvalidPermissionExceptionMapper from Application class ch.ti8m.security.twofa.server.selfcare.SelfCareApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,176 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class ch.ti8m.security.utils.exceptions.IllegalArgumentExceptionMapper from Application class ch.ti8m.security.twofa.server.selfcare.SelfCareApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,176 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class ch.ti8m.security.utils.exceptions.EJBTransactionRolledbackExceptionMapper from Application class ch.ti8m.security.twofa.server.selfcare.SelfCareApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,184 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /web/selfcare
            [0m [0m10:45:18,188 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class ch.ti8m.security.twofa.server.mobile.MobileApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,189 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.InvalidPermissionExceptionMapper from Application class ch.ti8m.security.twofa.server.mobile.MobileApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,189 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.IllegalArgumentExceptionMapper from Application class ch.ti8m.security.twofa.server.mobile.MobileApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,189 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource ch.ti8m.security.twofa.server.mobile.endpoints.MobileEndpoint from Application class ch.ti8m.security.twofa.server.mobile.MobileApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,189 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class ch.ti8m.security.utils.exceptions.EJBTransactionRolledbackExceptionMapper from Application class ch.ti8m.security.twofa.server.mobile.MobileApplication$Proxy$_$$_WeldClientProxy
            [0m [0m10:45:18,194 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /web/mobile
            [0m [0m10:45:18,219 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "lukbpoc.war" (runtime-name : "lukbpoc.war")
            [0m [0m10:45:18,219 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "fido.ear" (runtime-name : "fido.ear")
            [0m [0m10:45:18,219 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "web.ear" (runtime-name : "web.ear")
            [0m [0m10:45:18,231 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
            JBAS014775:    New missing/unsatisfied dependencies:
                  service jboss.mbean.server (missing) dependents: [service jboss.infinispan.web.config]
            
            
            [0m [0m10:45:18,305 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
            [0m [0m10:45:18,305 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
            [0m [31m10:45:18,305 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 17957ms - Started 1255 of 1391 services (9 services failed or missing dependencies, 215 services are lazy, passive or on-demand)
            [0m
            
            • 3. Re: What services failed when starting?
              Wolfgang Mayer Master

              The reason for the message "Unable to use InetAddress.getLocalHost() to resolve address." might be that your host is not configured. You should check if there is an entry in /etc/hosts

              • 4. Re: What services failed when starting?
                Florian Reiser Newbie

                Hello Wolfgang,

                 

                its correct. The entry in /etc/hosts was not set. But that did not solve the original problem.

                 

                How can I find out, what services failed to start?

                 

                Regards

                 

                Florian

                • 5. Re: What services failed when starting?
                  Wolfgang Mayer Master

                  Apparently some issues came up with infinispan.

                  Do you see all the caches in wildfly.

                  [standalone@localhost:9990 /] /subsystem=infinispan:read-children-names(child-type=cache-container

                  {

                      "outcome" => "success",

                      "result" => [

                          "ejb",

                          "hibernate",

                          "web"

                      ]

                  }

                  • 6. Re: What services failed when starting?
                    Florian Reiser Newbie

                    Hello Wolfgang,

                     

                    yes, the infinispan subsystem is up and running:

                     

                    {
                        "outcome" => "success",
                        "result" => [
                            "ejb",
                            "hibernate",
                            "web"
                        ]
                    }
                    

                     

                     

                    Regards

                     

                    Florian