Bug 1148873
| Summary: | Installing and starting JON server using rhqctl isn't able to correctly detect that rhq server is already started | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Radim Hatlapatka <rhatlapa> | ||||||
| Component: | Installer | Assignee: | RHQ Project Maintainer <rhq-maint> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | JON 3.3.0 | CC: | fbrychta, lfuka, mazz, rhatlapa | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | JON 3.3.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-10-03 06:51:29 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: | |||||||||
| Attachments: |
|
||||||||
Note with JON 3.3.0.ER3 it worked. can you attach your rhq-server.properties file? Created attachment 943449 [details]
rhq-server properties
Providing requested property file.
OK, I know one thing that is wrong. Look at rhq-server.proeprties. We saw this earlier with some other QE failure. Something is up with your QE scripts. It is blowing away "jboss.bind.address.management" and is replacing it with "jboss.bind.address" ==== jboss.bind.address=10.16.180.235 # By default only local management connections jboss.bind.address=10.16.180.235 ==== Please correct the rhq-server.properties so you don't lose the jboss.bind.address.managment - that setting needs to be there. And it should be left with the default 127.0.0.1 (though things should still work if you change it to some other valid setting). But with that missing, I think the installer client doesn't know what IP to use when trying to connect to the server to see if its working. Please try that again and let me know what happens when you fix the rhq-server.properties. (and fix your QE script so we don't keep seeing these types of errors :) ) Thanks a lot, that fixed the issue, I have updated our scripts and it should be now ok. |
Created attachment 943408 [details] JON server + installer logs Description of problem: When installing and starting JON server using rhqctl, rhqctl fails to detect that the server is already started, see attached logs Version-Release number of selected component (if applicable): 3.3.0.ER4 How reproducible: always Steps to Reproduce: 1. install and start JON server using rhqctl => ${JON_HOME}/bin/rhqctl install --storage-data-root-dir ${RHQ_STORAGE} ${JON_HOME}/bin/rhqctl start --storage ${JON_HOME}/bin/rhqctl start --server Actual results: rhqctl is waiting for the server to start even though it is already started Expected results: rhqctl correctly detects that server is already started Additional info: