Bug 1083572 - RHQ installer fails on Solaris 10
Summary: RHQ installer fails on Solaris 10
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 1083557
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-02 13:31 UTC by bkramer
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description bkramer 2014-04-02 13:31:52 UTC
Running "rhqctl install" on a Solaris 10 fails with:

...
./rhq-server.sh: syntax error at line 569: `max_wait_seconds=$' unexpected
15:35:29,279 INFO  [org.jboss.modules] JBoss Modules version 1.2.2.Final-redhat-1
15:35:29,380 INFO  [org.rhq.enterprise.server.installer.InstallerServiceImpl] The server is preconfigured and ready for auto-install.
15:35:29,473 INFO  [org.xnio] XNIO Version 3.0.7.GA-redhat-1
15:35:29,488 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
15:35:29,496 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.16.GA-redhat-1
15:35:39,802 ERROR [org.rhq.enterprise.server.installer.Installer] The installer will now exit due to previous errors: java.lang.Exception: Cannot obtain client connection to the RHQ app server!!
....
Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out

The reason is simple:

$RHQ-SERVER/bin/internal/rhq-server.sh

line 569:

  max_wait_seconds=$(expr $RHQ_SERVER_STOP_DELAY \* 60)

and line 572:

  waited_seconds=$(expr $waited_seconds + 2)

The $() syntax does not work on Solaris 10 (it does on Solaris 11)

Those lines need to become:

  max_wait_seconds=`expr $RHQ_SERVER_STOP_DELAY \* 60`
...
  waited_seconds=`expr $waited_seconds + 2`

which will work on all *NIX based platforms (old and new)


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