Installing on top of an external AS7

[huchangchun]

Dear RHQ Team,

I try to install RHQ 4.6 on top of an external AS 7 following https://docs.jboss.org/author/display/RHQ/Running+The+Installer.

It fails (RHQ throw error when run rhq-install.sh) until I copy the rhq.keystore and rhq.rhq.truststore to %External AS7%/standalone/configuration/.

Could you check this issue? Many thanks for fixing it.

Best regards.

Changchun.

[mazz]

What is the error? What version of AS7 did you use? At what step did the installation fail?

We'd need more information. Saying "RHQ throws an error when running rhq-install.sh" isn't much to go on

[huchangchun]

Hi John,

Thanks for your reply. Let me reply your question and then explain the problem in details.

1. The error is

"

09:55:24,931 WARN  [org.rhq.enterprise.server.installer.ServerInstallUtil] Failed to restore the original keystore from backup - please rename [/home/jon/jboss-as-7.1.1.Final/standalone/configuration/rhq.keystore.backup] to [/home/jon/jboss-as-7.1.1.Final/standalone/configuration/rhq.keystore]

09:55:24,947 INFO  [org.rhq.enterprise.server.installer.ServerInstallUtil] Creating https connector...

09:55:25,816 ERROR [org.rhq.enterprise.server.installer.Installer] An error occurred: org.rhq.common.jbossas.client.controller.FailureException: Failed to add new connector [https]: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"JBAS014671: Failed services" => {"jboss.web.connector.https" => "org.jboss.msc.service.StartException in service jboss.web.connector.https: JBAS018007: Error starting web connector"}}}}

        at org.rhq.common.jbossas.client.controller.WebJBossASClient.addConnector(WebJBossASClient.java:176) [rhq-jboss-as-dmr-client-4.6.0.jar:4.6.0]

        at org.rhq.enterprise.server.installer.ServerInstallUtil.setupWebConnectors(ServerInstallUtil.java:1283) [rhq-installer-util-4.6.0.jar:4.6.0]

        at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceImpl.java:285) [rhq-installer-util-4.6.0.jar:4.6.0]

        at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:130) [rhq-installer-util-4.6.0.jar:4.6.0]

        at org.rhq.enterprise.server.installer.Installer.main(Installer.java:57) [rhq-installer-util-4.6.0.jar:4.6.0]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_15]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_15]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_15]

        at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]

        at org.jboss.modules.Module.run(Module.java:260)

"

2. I use jboss-as-dist-7.1.1.Final.zip

Let me introduce the steps how to reproduce this problem.

1. unzip  jboss-as-dist-7.1.1.Final.zip

2. unzip rhq-server-4.6.0.zip

3. remove the "jbossas" folder in rhq-server-4.6.0

4. export RHQ_SERVER_JBOSS_HOME to the folder of jboss-as-7.1.1.Final

5. go to bin directory of rhq-server-4.6.0

6. run "sh rhq-server.sh start" to start RHQ

7. edit rhq-server.properties, enable auto install

8. run "sh rhq-install.sh" to install RHQ. Then we can get the error message as above.

According the warning message and script of making RHQ build, I guess the reason may be that the jboss-as-7.1.1.Final miss rhq.keystore and rhq.rhq.truststore files. So I copy these two files from other RHQ build to "jboss-as-7.1.1.Final/standalone/configuration". Then I run command "rhq-install.sh" again. At last, the problem is resolved.

I hope above information is enough now. Let me know if I miss anything. I hope this problem can be resolved by generating the rhq.keystore and rhq.truststore automatically when they are missed.

Many thanks and best regards.

[mazz]

Thank you for your excellent write up! I was able to replicate this problem using your steps exactly. I wrote a BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=922791

I'll look at this today. I have a feeling this is an easy one to fix. But I'll know in a little bit. Follow that BZ for progress.

[mazz]

I fixed this issue. Patch is attached to the BZ and I'm waiting for fedorahosted outage to be repaired before I can push to the master branch on the remote repo. Fedorahosted status can be found here - currently an outage is in progress.

[huchangchun]

Hi John,

I can find the fix in master branch now.

Thank you very much for your prompt action.

Best regards.

Changchun