1 Reply Latest reply on Aug 17, 2016 3:05 PM by mnovak

    wildfly 9.0.1.final error: WFLYSRV0082: failed to resolve interface public

    marlowa42
    marlowa42 Aug 17, 2016 8:18 AM

      I am trying to start my wildfly application server but it is giving this error. Googling I see it is a very common error but the causes seem vague. I have seen "solutions" such as disable the firewall and set the various bind addresses to 0.0.0.0 which I am already doing. Loopback localhost is configured correctly in my hosts file and I can ping it ok. So I am at a loss.

       

      The full error message is:

      12:13:33,017 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: WFLYSRV0082: failed to resolve interface public

          at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:91)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          at java.lang.Thread.run(Thread.java:745)

       

      Later on I get the error:

       

      [0m [31m12:13:37,735 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

          ("core-service" => "management"),

          ("management-interface" => "http-interface")

      ]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {

          "Services that were unable to start:" => [

              "jboss.serverManagement.controller.management.http",

              "jboss.serverManagement.controller.management.http.shutdown"

          ],

          "Services that may be the cause:" => [

              "jboss.http-upgrade-registry.default",

              "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

          ]

      }}

       

      Might this be related?

       

      Here is the socket-binding-group part of my config file:

       

      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
          <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9991}"/>
          <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
          <socket-binding name="ajp" port="${jboss.ajp.port:8209}"/>
          <socket-binding name="http" port="${jboss.http.port:8280}"/>
          <socket-binding name="remoting" port="${jboss.http.port:4448}"/>
          <socket-binding name="https" port="${jboss.https.port:8443}"/>
          <socket-binding name="txn-recovery-environment" port="4712"/>
          <socket-binding name="txn-status-manager" port="4713"/>
          <socket-binding name="messaging" interface="messaging" port="5445"/>
          <socket-binding name="messaging-throughput" interface="messaging" port="5455"/>
          <outbound-socket-binding name="mail-smtp">
              <remote-destination host="localhost" port="25"/>
          </outbound-socket-binding>
      </socket-binding-group>