Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Slave failed to join domain master due to authentication failure.

    Posted on

    I created a two nodes (VMs) JBoss 7.1.3 cluster with domain configuration. Now I created another node as a slave to join the domain. The new one failed to join the domain when I tried to start it.

    [/opt/jboss/jboss-eap-7.1/bin]$ ./domain.sh -Djboss.domain.base.dir=/opt/jboss/jboss-eap-7.1/domain --host-config=host-slave.xml

    JBoss Bootstrap Environment

    JBOSS_HOME: /opt/jboss/jboss-eap-7.1

    JAVA: java

    JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

    11:42:07,159 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.4.Final-redhat-1
    11:42:07,450 INFO [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
    [Host Controller] 11:42:07,944 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.4.Final-redhat-1
    ...
    [Host Controller] 11:42:09,550 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.7.Final-redhat-1
    [Host Controller] 11:42:09,602 INFO [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on 10.124.236.93:9999
    [Host Controller] 11:42:09,954 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://10.124.236.95:9999: java.lang.IllegalStateException: WFLYHC0043: Unable to connect due to authentication failure.
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService.rethrowIrrecoverableConnectionFailures(RemoteDomainConnectionService.java:674)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:293)
    [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.connectToDomainMaster(DomainModelControllerService.java:938)
    [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:692)
    [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
    [Host Controller] at java.lang.Thread.run(Thread.java:748)
    [Host Controller] Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
    [Host Controller] DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication
    [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
    [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446)
    [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
    [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
    [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
    [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
    [Host Controller] at ...asynchronous invocation...(Unknown Source)
    [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:570)
    [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:532)
    [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:520)
    [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
    [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection.lambda$openConnection$0(RemoteDomainConnection.java:223)
    [Host Controller] at org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108)
    [Host Controller] at org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:268)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection.openConnection(RemoteDomainConnection.java:223)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$InitialConnectTask.connect(RemoteDomainConnection.java:592)
    [Host Controller] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection.connect(RemoteDomainConnection.java:147)
    [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:288)
    [Host Controller] ... 4 more
    [Host Controller] Suppressed: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication
    [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:736)
    [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:578)
    [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
    [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
    [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
    [Host Controller]
    [Host Controller] 11:42:09,956 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
    [Host Controller] 11:42:09,956 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
    [Host Controller] 11:42:09,957 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
    [Host Controller] 11:42:09,984 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 7.1.3.GA (WildFly Core 3.0.16.Final-redhat-1) stopped in 12ms
    [Host Controller]
    11:42:10,307 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
    11:42:10,308 INFO [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller
    11:42:10,309 INFO [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting

    I have followed another discussion:
    https://access.redhat.com/discussions/2934251
    and compared two slave nodes' domain.xml and host-slave.xml. I have created admin user on each slave node separately (one node with 01admin, the other 02admin).
    Attached new node's domain.xml and host-slave.xml
    Can anyone help? Does JBoss supports three nodes domain cluster?

    Attachments

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat