Jboss 7.0无法在Red Hat

时间:2017-05-20 00:27:18

标签: linux jboss redhat jboss-eap-7

嗨,我正在尝试在Red Hat Enterprise Linux 7中运行Jboss EAP 7.0.0,安装顺利,直到我需要启动该服务。

 sudo service jboss-eap-rhel start
Redirecting to /bin/systemctl start  jboss-eap-rhel.service
Job for jboss-eap-rhel.service failed. See 'systemctl status jboss-eap-rhel.service' and 'journalctl -xn' for details.

在到达服务日志后,它显示JBoss EAP启动脚本无法启动。

localhost.localdomain systemd 1:无法启动SYSV:JBoss EAP启动脚本。

systemctl status jboss-eap-rhel.service
jboss-eap-rhel.service - SYSV: JBoss EAP startup script
   Loaded: loaded (/etc/rc.d/init.d/jboss-eap-rhel.sh)
   Active: failed (Result: resources) since Wed 2017-05-17 05:35:37 EDT; 6min ago
  Process: 16673 ExecStart=/etc/rc.d/init.d/jboss-eap-rhel.sh start (code=exited, status=0/SUCCESS)
 Main PID: 6979

May 17 05:35:06 localhost.localdomain systemd[1]: Starting SYSV: JBoss EAP startup script...
May 17 05:35:06 localhost.localdomain jboss-eap-rhel.sh[16673]: Starting jboss-eap: chown: missing operand after ‘/var/run/jboss-eap’
May 17 05:35:06 localhost.localdomain jboss-eap-rhel.sh[16673]: Try 'chown --help' for more information.
May 17 05:35:37 localhost.localdomain jboss-eap-rhel.sh[16673]: jboss-eap started with errors, please see server log for details
May 17 05:35:37 localhost.localdomain jboss-eap-rhel.sh[16673]: [  OK  ]
May 17 05:35:37 localhost.localdomain systemd[1]: PID file /var/run/jboss-eap/jboss-eap.pid not readable (yet?) after start.
May 17 05:35:37 localhost.localdomain systemd[1]: Failed to start SYSV: JBoss EAP startup script.
May 17 05:35:37 localhost.localdomain systemd[1]: Unit jboss-eap-rhel.service entered failed state.

我检查了jboss conf和eap-rhel.sh查找错误的内容,包括standalone.xml和standalone-full.xml,但一切看起来都没问题。

jboss的文件现在在/ usr / share中(我已经在不同的文件夹中安装和卸载了几次试图解决它,是的,我在每次安装之前删除了剩余的文件)。

为了确定,我提到了每次安装后我完成的步骤:

  1. jboss-eap.conf已成功编辑。用户和jboss的路径改为正确的。

  2. 将jboss-eap.conf复制到/ etc / default

  3. 将jboss-eap-rhel复制到/etc/init.d

  4. 我也用

    打开它

    ./ standalone.sh -c standalone-full.xml

    它会抛出此警告:

    03:56:23,735 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX00                                                                                                                                                             13: Node identifier property is set to the default value. Please make sure it is                                                                                                                                                              unique.
    

    并且不起作用(因为该服务仍未激活)。

    ¿我该如何开始服务?

2 个答案:

答案 0 :(得分:1)

  

03:56:23,735 WARN [org.jboss.as.txn](ServerService线程池 - 60)WFLYTX0013:节点标识符属性设置为默认值。请确保它是唯一的。

除非您启用了JTA,否则不必担心它。您可以在standalone-full.xml文件中设置节点标识符的唯一值,如:

<subsystem xmlns="urn:jboss:domain:transactions:1.4">
<core-environment node-identifier="${jboss.tx.node.id}">
...

关于服务,请验证您遵循的步骤http://www.dmartin.es/2014/07/jboss-eap-6-as-rhel-7-service/

答案 1 :(得分:0)

如果您正在使用 JBoss 7.x ,则可以使用以下CLI命令:

/host=master/server-config=server-one/system-property=jboss.tx.node.id:add(boot-time=true,value=master)

/host={slave-host}/server-config=server-one/system-property=jboss.tx.node.id:add(boot-time=true,value=slave2)

/profile={some-profile}/subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}")

:reload-servers(blocking=true)

这将添加以下行:

   <subsystem xmlns="urn:jboss:domain:transactions:4.0">
  <core-environment node-identifier="${jboss.tx.node.id}">
     <process-id>
        <uuid/>
     </process-id>
  </core-environment>
  <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
  <object-store path="tx-object-store" relative-to="jboss.server.data.dir"/>
   </subsystem>

domain.xml 配置文件的每个配置文件部分(在域控制器中),并且:

   <servers>
  <server name="server-one" group="x-server-group" auto-start="true">
     <system-properties>
        <property name="jboss.tx.node.id" value="slave1" boot-time="true"/>
     </system-properties>
  </server>
   </servers>

host-slave.xml 配置文件中的每个服务器定义下(在主机控制器中)。

外部参考:
https://access.redhat.com/solutions/748323
https://access.redhat.com/solutions/260023
https://issues.jboss.org/browse/JBEAP-11208