Description of problem: JBoss ON server installation does not complete and terminal shows "INFO [org.rhq.server.control.command.Install] Still waiting for server to start..." over and over again. However, while installation script is still running, the server.log shows that JBoss ON server is started and user is able to log in to the JBoss ON UI. If the user stop/interrupt the installation script, everything will go back and their attempt to start server with ./rhqctl start will not be successful because the server is not installed. Version-Release number of selected component (if applicable): JBoss ON 3.3.0 How reproducible: Always Steps to Reproduce: 1. Unzip jon-server-3.3.0.zip file; 2. Edit $JON-SERVER-HOME/bin/rhq-server.properties file to set database properties, ... 3. Make sure that jboss.bind.address.management parameter is commented out: ... # By default only local management connections # jboss.bind.address.management=127.0.0.1 ... Actual results: Installation script will not finish and will output "Still waiting for server to start..." message although it is possible to log in to the JBoss ON UI. Once the installation script is interrupted/closed, it will not be possible to log in to JBoss ON UI and attempt to start JBoss ON server will fail with message that server is not installed. Expected results: If for some reason jboss.bind.address.management is commented out - we should use jboss.bind.address and installation should be done successfully. Additional info:
Fixed in the master: commit a30441ee0c962b06b4b325d77f1188972f5ae4a6 Author: Michael Burman <miburman> Date: Thu Aug 3 14:11:38 2017 +0300 [BZ 1343642] If jboss.bind.address.management is not set, fallback to jboss.bind.address for server installation polling
Moving to ON_QA as available for test with the following binary: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/133/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *NOTE Build represents JON 3.3.9 DR01 build. Please report issues as you encounter them.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2846