MSC00001: Failed to start service jboss.network.public

Question

Hi friends I am new in managing Jboss Appserver I am using Red Hat Enterprise Linux Server release 5.8 (Tikanga) and my JAVA version is

java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)

and have JBoss Version jboss-as-7.1.1.Final this and have configur my JAVA_HOME and JBOSS_HOME as followes

export JAVA_HOME=/opt/jdk1.7.0_75
export JRE_HOME=/opt/jdk1.7.0_75/jre
export PATH=$PATH:/opt/jdk1.7.0_75/bin:/opt/jdk1.7.0_75/jre/bin
export JBOSS_HOME=/opt/jboss-as-7.1.1.Final; export PATH=$JBOSS_HOME/bin:$PATH

but when i am trying to run it in standalone mode with my public ip using

./standalone.sh -Djboss.bind.address=XXX.XX.XXX.XXX -Djboss.bind.address.management=XXX.XX.XXX.XXXX

I am getting the following error

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss-as-7.1.1.Final

  JAVA: /opt/jdk1.7.0_75/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

=========================================================================

16:59:24,755 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
16:59:24,922 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:59:24,970 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
16:59:25,901 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
16:59:25,930 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
        at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]

16:59:25,944 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
16:59:25,928 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
        at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]

16:59:25,968 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.3.GA
16:59:25,971 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
16:59:25,979 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.3.GA
16:59:26,004 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:59:26,010 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:59:26,028 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:59:26,035 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final
16:59:26,038 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:59:26,131 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:59:26,144 INFO  [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:59:26,156 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
16:59:26,170 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:59:26,255 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:59:26,323 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:59:26,727 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.1.Final/standalone/deployments
16:59:30,013 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
      service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management

16:59:30,030 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
16:59:30,031 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 5556ms - Started 106 of 179 services (27 services failed or missing dependencies, 45 services are passive or on-demand)

But when I start it with

./standalone.sh -Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0

Have no error any one could please help me i have read the link or reference but it could not solve my problem

Answer 1

Check jboss.bind.address and ensure that it points to a local valid ip or hostname.

E.g. my loopback address was fine, network configuration was fine, hosts file was empty but ping to localhost or 127.0.0.1 was working, but the problem was, someone copy-pasted another server configuration and forgot to change the jboss.bind.address setting that was included in the standalone.xml:

<system-properties>
    <property name="jboss.bind.address" value="another-hostname.domain.tld"/>
</system-properties>

So changing that to a proper value fixed the issue.

Since this is an environment variable, it may be wrongly set in different places, e.g. server config and startup scripts or Eclipse launch configuration, etc. but a filesystem search should find the places where it is set.

Answer 2

I got exactly the same problem with Wildfly 9.0.1.Final. The problem was a bad value in /etc/hosts, where two IP addresses were defined for the same URL. Cleaning hosts made the problem disappear.

Answer 3

If the hosts entry is incorrect as well, then that might also cause the problem.

Make sure you /etc/hosts has the current/correct ip address when you are trying to start the server. This might be the case if you don't have a static ip address.

Answer 4

I had a similar problem and it was because the loopback was not configured... If you don't get the lo interface in the output of ifconfig, run:

ifconfig lo 127.0.0.1 up

to enable it