当前位置: 首页 > 知识库问答 >
问题:

MSC00001:无法启动服务jboss。网络平民的

韩玉石
2023-03-14

嗨,朋友们,我是管理Jboss Appserver的新手,我正在使用Red Hat EnterpriseLinuxServer版本5.8(Tikanga),我的JAVA版本是

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)

并具有JBoss版本JBoss-as-7.1.1。最后,将我的JAVA\u主页和JBOSS\u主页配置如下

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

但是,当我尝试使用我的公共ip以独立模式运行它时

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

我收到以下错误

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

  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)

但当我开始的时候

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

没有错误任何人都可以帮助我我已经阅读了链接或参考,但它不能解决我的问题

共有3个答案

芮承运
2023-03-14

如果hosts条目也不正确,那么也可能导致问题。

在尝试启动服务器时,请确保您的主机具有当前/正确的ip地址。如果没有静态ip地址,可能会出现这种情况。

顾骏祥
2023-03-14

我在Wildfly 9.0.1中遇到了完全相同的问题。最终的问题是,在同一URL中定义了两个IP地址的主机中,etc/hosts的值不正确。清理主机使问题消失。

有宏峻
2023-03-14

检查jboss。绑定地址并确保它指向本地有效的ip或主机名。

例如,我的环回地址正常,网络配置正常,主机文件为空,但ping到localhost或127.0.0.1正常工作,但问题是,有人复制粘贴了另一个服务器配置,忘记更改jboss.bind.address设置包含在standalone.xml中:

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

因此,将其更改为适当的值可以解决问题。

由于这是一个环境变量,它可能在不同的位置设置错误,例如服务器配置和启动脚本或Eclipse启动配置等。但文件系统搜索应该找到设置它的位置。

 类似资料:
  • 请帮帮我.我使用的是Ubuntu 16.04

  • 启动jboss服务器时,出现错误,无法启动服务jboss.deployment.unit.“jbpm console.war”。但是当我使用start.demo运行jbpm6演示时,它工作得很好。

  • 问题内容: 码头工人给我一个困难时期。我按照以下说明进行操作,以便在运行由strato.de托管的Ubuntu 14.04的虚拟服务器上安装docker。 执行此行直接将我带入此错误消息: 安装完成后,我安装了上述两个软件包。现在我的问题是我无法让docker运行。 结果是: 结果是 和 结果是 有人对缺少哪些依赖项有任何线索吗?还有什么可能出问题了?码头工人是否提供任何日志? 我正在来回寻找解决

  • 当收到来自服务器的数据报文时,显示错误日志:

  • 我有一个spring boot可执行罐,装在数字海洋水滴中。我可以使用现在我想让我作为一个服务运行。 我已经创建了文件/etc/systemd/system/myapp。用这些内容服务 然后使其在系统启动时启动 我正在尝试启动服务 但是我得到了这个错误 无法启动myapp.service:未知单位:myapp.service详情请参阅系统日志和'systemctl statusmyapp.serv

  • 好吧,这就是问题所在。我做,但我没有从或获得新的日志消息。 舱单: null 活动代码: 我试过什么: 将所有“cont”更改为“this” StartService(新意图(cont,FlashService.class)); null 更新: 完整活动代码: