Bug 1014553

Summary: server not accessible via gui if installed after failure
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: InstallerAssignee: Thomas Segismont <tsegismo>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jkremser, jshaughn, mfoley, theute, tsegismo
Target Milestone: ER03Keywords: Reopened
Target Release: JON 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-03 13:17:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1006862    
Attachments:
Description Flags
serverNotAccessible.png
none
server.log none

Description Armine Hovsepyan 2013-10-02 10:49:41 UTC
Created attachment 806374 [details]
serverNotAccessible.png

Description of problem:
server not accessible via gui if installed after failure

Version-Release number of selected component (if applicable):
JOn 3.2 ER2 (noticed on er1 as well)

How reproducible:


Steps to Reproduce:
1. get jon 3.2 er2 and unzip it
2. run rhqctl install without giving bind.address
3. fix bind.address 
4. re-run rhqctl install

Actual results:
After step2. server install fails with exit 2
after step 4. server is installed, server.log contains "JBoss Operations Network 3.2.0.ER2 (build 9bf6f76:371eac0) Server started."  log, process is running, but server is not accessible via GUI.

Expected results:
after step4. server is installed and accessible via GUI

Additional info:
screenshot attached

Comment 1 Thomas Segismont 2013-10-03 12:08:17 UTC
Which bind.address did you use?

Can you provide the full log of your server?

Comment 2 Jirka Kremser 2013-10-03 13:04:46 UTC
Jay's mail:

There is now more up-front validation of rhq-server.properties and 
rhq-storage.properties when executing 'rhqctl install'.   Issues with 
property settings should cause rhqctl to exit before actually attempting 
to install anything.  Furthermore, it will now prompt for 
jboss.bind.address and rhq.server.database.password if it is unset in 
rhq-server.properties file.

=> should be fixed now by aafabc790 as well as bug 1002778

Jay, could you please confirm this?

note: Unfortunately, the "splash page" can't indicate the errors that happen too soon as this one. On the other hand, we can prevent them to happen.

Comment 3 Armine Hovsepyan 2013-10-03 13:08:19 UTC
Thomas, i guess the issue is that jboss server is being started during the first installation attempt and when installation fails the process is still running.

Full server.log attached

Comment 4 Armine Hovsepyan 2013-10-03 13:08:44 UTC
Created attachment 807079 [details]
server.log

Comment 5 Thomas Segismont 2013-10-03 13:17:00 UTC
Armine,

There is absolutely no error in this log file.

You have set jboss.bind.address.management = 127.0.0.1

Well your Jboss server is only listening on the loopback address. No chance you can reach it from outside.

Closing the issue.

Comment 6 Thomas Segismont 2013-10-03 13:17:57 UTC
It it's not clear, I said JBoss server thinking of RHQ server

Comment 7 Jay Shaughnessy 2013-10-03 13:22:52 UTC
I agree, this doesn't look like an issue.  Furthermore, the up front validation likely negates this test case, and more behavioral changes are imminent given Bug 1006353 changes.

Comment 8 Thomas Segismont 2013-10-03 13:24:23 UTC
Me stupid. jboss.bind.address.management is not jboss.bind.address ...

Re-opening.

Apologies, Armine

Comment 9 Thomas Heute 2013-10-03 13:34:39 UTC
Jay, I think  you pointed to wrong BZ ;)

Comment 10 Thomas Segismont 2013-10-03 13:35:52 UTC
"Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:7080" 

So because the server was not installed correctly, the server chose a default value of "127.0.0.1". RHQ server GUI is listening on 127.0.0.1. It cannot be reached from outside.

Anyway, see Jay's #c7, the installer will no longer start the server if the property is not set.

Comment 11 Simeon Pinder 2013-10-08 07:41:45 UTC
Moving to ON_QA for testing.

Comment 12 Armine Hovsepyan 2013-10-08 11:35:58 UTC
verified
No service is started without passing bind.address