]
RH Bugzilla Integration updated WFLY-60:
----------------------------------------
Bugzilla References:
Failure slave host's security realm. Configure the slave host to
get the password from the vault
------------------------------------------------------------------------------------------------
Key: WFLY-60
URL:
https://issues.jboss.org/browse/WFLY-60
Project: WildFly
Issue Type: Bug
Components: Domain Management, Security
Reporter: Alexander Orobey
Assignee: Brian Stansberry
Priority: Critical
Fix For: 8.0.0.Alpha1
Attachments: host.xml
When setting up Password Vault for connect slave host to master jboss fails with:
16:19:25,298 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
16:19:25,451 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017:
Starting process 'Host Controller'
[Host Controller] 16:19:25,983 INFO [org.jboss.modules] (main) JBoss Modules version
1.2.0.CR1
[Host Controller] 16:19:26,148 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
[Host Controller] 16:19:26,217 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899:
JBoss AS 7.2.0.Final "Janus" starting
[Host Controller] 16:19:27,060 INFO [org.jboss.security] (Controller Boot Thread)
PBOX000361: Default Security Vault Implementation Initialized and Ready
[Host Controller] 16:19:27,075 INFO [org.xnio] (MSC service thread 1-8) XNIO Version
3.0.7.GA
[Host Controller] 16:19:27,089 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO
Implementation Version 3.0.7.GA
[Host Controller] 16:19:27,093 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902:
Creating http management service using network interface (management) port (9990)
securePort (-1)
[Host Controller] 16:19:27,100 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss
Remoting version 3.2.14.GA
[Host Controller] 16:19:27,173 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-4) MSC00001: Failed to start service
jboss.server.controller.management.security_realm.ManagementRealm.secret:
org.jboss.msc.service.StartException in service
jboss.server.controller.management.security_realm.ManagementRealm.secret: Failed to start
service
[Host Controller] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
[jboss-msc-1.0.4.GA.jar:1.0.4.GA]
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_17]
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_17]
[Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
[Host Controller] Caused by: java.lang.IllegalStateException: Bad Base64 input character
at 7: 64(decimal)
[Host Controller] at org.jboss.util.Base64.decode(Base64.java:704)
[Host Controller] at org.jboss.util.Base64.decode(Base64.java:735)
[Host Controller] at
org.jboss.as.domain.management.security.SecretIdentityService.start(SecretIdentityService.java:68)
[jboss-as-domain-management-7.2.0.Final.jar:7.2.0.Final]
[Host Controller] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.4.GA.jar:1.0.4.GA]
[Host Controller] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.4.GA.jar:1.0.4.GA]
[Host Controller] ... 3 more
[Host Controller]
[Host Controller] 16:19:27,396 FATAL [org.jboss.as.host.controller] (Controller Boot
Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting.
See previous messages for details.
[Host Controller] 16:19:27,417 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950:
JBoss AS 7.2.0.Final "Janus" stopped in 15ms
16:19:27,765 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host
Controller) JBAS012010: Process 'Host Controller' finished with an exit status of
99
16:19:27,767 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process
controller
16:19:27,768 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished;
exiting
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: