Bug 1142108 - Unable to install the rhq server (Still waiting for server to start)
Summary: Unable to install the rhq server (Still waiting for server to start)
Status: VERIFIED
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
urgent vote
Target Milestone: ---
: RHQ 4.13
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords: Reopened
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-16 07:47 UTC by Filip Brychta
Modified: 2014-09-19 11:03 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2014-09-16 14:45:35 UTC


Attachments (Terms of Use)
server log (519.87 KB, text/plain)
2014-09-16 07:47 UTC, Filip Brychta
no flags Details
rhq-server.properties (18.29 KB, text/plain)
2014-09-16 12:44 UTC, Filip Brychta
no flags Details
standalone-full.xml (30.34 KB, text/plain)
2014-09-16 12:45 UTC, Filip Brychta
no flags Details

Description Filip Brychta 2014-09-16 07:47:14 UTC
Created attachment 937887 [details]
server log

Description of problem:
Last rhq snapshot build fails to install. Previous build 58023b7 is Ok.

Version-Release number of selected component (if applicable):
ed8b9aa

How reproducible:
Always

Steps to Reproduce:
1. ./rhqctl install


Actual results:
No errors in installer output just following msgs:
03:04:48,189 INFO  [org.rhq.server.control.command.Install] Still waiting for server to start...
03:05:18,223 INFO  [org.rhq.server.control.command.Install] Still waiting for server to start...
03:05:48,264 INFO  [org.rhq.server.control.command.Install] Still waiting for server to start...
03:06:18,291 INFO  [org.rhq.server.control.command.Install] It has been over [2] minutes - you may want to ensure your server startup is proceeding as expected. You can check the log at [/home/hudson/rhq-server-4.13.0-SNAPSHOT/logs/server.log].

Rhq server is started but there are errors in server.log
See attached full server.log

Expected results:
Installation works

Additional info:
See attached full server.log

Comment 1 John Mazzitelli 2014-09-16 12:35:03 UTC
Can you attach your standalone-full.xml and your rhq-server.properties.

BTW: the XA errors is that known issue and seems to only happen when you use "--start" option with "rhqctl install" - can you confirm you did NOT use --start?

Comment 2 Filip Brychta 2014-09-16 12:44:49 UTC
Created attachment 937989 [details]
rhq-server.properties

Comment 3 Filip Brychta 2014-09-16 12:45:10 UTC
Created attachment 937990 [details]
standalone-full.xml

Comment 4 Filip Brychta 2014-09-16 12:55:19 UTC
(In reply to John Mazzitelli from comment #1)
> Can you attach your standalone-full.xml and your rhq-server.properties.
> 
> BTW: the XA errors is that known issue and seems to only happen when you use
> "--start" option with "rhqctl install" - can you confirm you did NOT use
> --start?

I didn't use --start option.
XA errors is that known issue - yes, I'm not saying this is what's causing it.

It worked yesterday so It should be caused by one of following commits:
     Bug 1062789 - Set quoting to enabled for newly created script server resources (detail)
    [1128151] Error while upgrading from JON 3.1.2 to 3.3: [rhq.autoinstall.server.admin.password] must exist and be set to a valid string value (detail)
    [1078500] SEVERE error in Server.log file: JSF1051 (detail)
    [1035420] OOB content labels get cut off (detail)
    BZ 1141175 - make sure installer works even if the management bind address is set to 0.0.0.0 (detail)
    Related to work for 1138328. Wrap the new non-async uninv work for (detail)

Comment 5 John Mazzitelli 2014-09-16 13:50:54 UTC
Your rhq-server.properties is missing something. Looks like you deleted a needed property.

I see this:

   ...
   jboss.bind.address=0.0.0.0

   # By default only local management connections 
   jboss.bind.address=0.0.0.0
   ...

In the default, out-of-box, rhq-server.properties file, it is this:

   ...
   jboss.bind.address=0.0.0.0

   # By default only local management connections 
   jboss.bind.address.management=0.0.0.0
   ...

Notice in your rhq-server.properties, you deleted the ".management" property and replaced it with a duplicate property "jboss.bind.address" - this means you did not set "jboss.bind.address.management" property at all.

Please correct your rhq-server.properties by not deleting that ".management" property from the file and re-try your test. I suspect this is the problem.

Comment 6 Filip Brychta 2014-09-16 14:45:35 UTC
You are correct. Our installation script overwrites jboss.bind.address.management with jboss.bind.address so there was no jboss.bind.address.management in rhq-server.properties.

This was ok in previous rhq versions but it is required property now and installation without it fails.

bz 1127790 should cover this problem.

Comment 7 John Mazzitelli 2014-09-16 15:01:13 UTC
FYI: I fixed this anyway. There was a NullPointerException that was happening that caused this. I fixed that with this commit to master:

commit e39233a1469facc8ca05b01bc3bb0d0dca879f54
Author: John Mazzitelli <mazz@redhat.com>
Date:   Tue Sep 16 10:58:58 2014 -0400

    BZ 1142108 - fix NPE - in case someone deleted jboss.bind.address.management from rhq-server.properties

I flipped this to ON_QA in case this still wants to be tested. I still think we need to require people to set this property and not delete it. But just in case, this bug doesn't happen anymore when it is deleted.

Comment 8 Filip Brychta 2014-09-19 11:03:05 UTC
Verified on
Version :	
4.13.0-SNAPSHOT
Build Number :	
9aa0c46


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