Bug 1343644 - RHQ 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.
Summary: RHQ server installation does not complete and terminal shows "INFO [org.rhq.s...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1343642
TreeView+ depends on / blocked
 
Reported: 2016-06-07 15:02 UTC by bkramer
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description bkramer 2016-06-07 15:02:56 UTC
Description of problem:
RHQ 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 RHQ server is started and user is able to log in to the RHQ 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):
RHQ 4.12

How reproducible:
Always

Steps to Reproduce:
1. Unzip rhq archive file;
2. Edit $RHQ-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 RHQ UI. Once the installation script is interrupted/closed, it will not be possible to log in to RHQ UI and attempt to start RHQ 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:


Note You need to log in before you can comment on or make changes to this bug.