Increase visibility into IT operations to detect and resolve technical issues before they impact your business.
I'm trying to set up a test env of one Domain Controller and 2 Host Controllers using EAP7 ati Linux. The Domain Controller is up and running fine, but when i try to add a HC to this domain controller, i get the following error:
[...]
[Host Controller] 18:57:28,797 INFO [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on 192.168.244.147:9999
[Host Controller] 18:57:29,034 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://192.168.244.146:9999 -- java.lang.IllegalStateException: WFLYHC0043: Unable to connect due to authentication failure.
[Host Controller] 18:57:29,034 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
[Host Controller] 18:57:29,034 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
[Host Controller] 18:57:29,120 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 79ms
[Host Controller]
18:57:29,481 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
18:57:29,486 INFO [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller
18:57:29,488 INFO [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting
Here is my slave's "host-slave.xml", important parts:
<domain-controller>
<remote username="jbossadm" security-realm="ManagementRealm">
<discovery-options>
<static-discovery name="primary" protocol="${jboss.domain.master.protocol:remote}" host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}"/>
</discovery-options>
</remote>
</domain-controller>
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:192.168.244.147}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:192.168.244.147}"/>
</interface>
</interfaces>
The SSH is configured for the "jboss" operating system user and i am starting the HC (domain.sh) as jboss user. The JBoss administrator, configured at installation is "jbossadm"
I am using the following startup script, at the slave:
./domain.sh -Djboss.domain.master.address=192.168.244.146 --host-config=host-slave.xml
... sorry, but i am quite new on the JBoss world.
Any help will be very helpful.
Thanks
I faced the same issue but after adding "name" property in host-slave.xml. This problem was resolved !! Please try and let me know.
host xmlns="urn:jboss:domain:5.0" name="slave"
Pude resolver el problema, hay que hacer lo siguiente:
I can solve the problem, you must do the following:
Generar un usuario (gcplnxdevdg02)en el Domain Controller, copiar el Secret value obtenido.
Modificar el archivo host.xml o host-slave.xml del Host Controller agregando el secret value:
Agregar el valor name como sigue, este valor debe tener el mismo nombre del usuario que generamos en el paso 1. IMPORTANTE
Asegurar que los valores de conexión, ip y puerto sean correctos:
Donde gcplnxdevdg01 es el Domain Controller.
Reiniciar el Host Controller en este caso es gcplnxdevdg02
Listo, ya te conectas sin problema.
Saludos
Why are some of us replying in Spanish? This makes the solution for non Spanish readers at least confusing, if not unreadabe.
Google translate is not Always our friend.
Regards,
Jan Gerrit
P.S. If I would use my native language may be 1 or 2 Red Hat customers would understand.
E.g. "Nimmen kin dit lêse, tink ik".
It soe it lestich wêze om te lêzen sûnder Google Oersetting, hoewol it ticht genôch is foar myn Dútske taalfeardichheden om hast bepaald te bestimmen.
the following is not a translation, but to underscore the point Jan Gerrit made, that we really ought to only be using English in this forum, as Red Hat has mentioned in previous discussions.
Let's see if this configuration steps can help you:
Assuming you've already created a management user for the host-controller, or you can simply add a new one by entering the following command: