Issue

• I try to install new JBoss ON version in our dev environment but rhqctl script always show usage:

Execute command:

/opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl upgrade --from-agent-dir /opt/jboss/jon-agent --from-server-dir /opt/jboss/jon-server-3.1.2.GA --run-data-migrator

Output:

RHQ_SERVER_HOME: /opt/jboss/jon-server-3.2.0.ER3
RHQ_SERVER_JBOSS_HOME: /opt/jboss/jon-server-3.2.0.ER3/jbossas
No embedded JRE found - will try to use JAVA_HOME: /usr/lib/jvm/java-oracle/
RHQ_SERVER_JAVA_HOME: /usr/lib/jvm/java-oracle/
RHQ_SERVER_JAVA_EXE_FILE_PATH: /usr/lib/jvm/java-oracle//bin/java
RHQ_CONTROL_JAVA_OPTS: -Xmx512M -XX:MaxPermSize=128M -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djava.awt.headless=true -Drhq.server.properties-file=/opt/jboss/jon-server-3.2.0.ER3/bin/rhq-server.properties -Drhq.control.logdir=/opt/jboss/jon-server-3.2.0.ER3/logs -Drhq.control.loglevel=DEBUG -Drhq.server.basedir=/opt/jboss/jon-server-3.2.0.ER3 -Drhqctl.properties-file=/opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
RHQ_CONTROL_ADDITIONAL_JAVA_OPTS:
_JBOSS_MODULEPATH: /opt/jboss/jon-server-3.2.0.ER3/modules:/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules
22:21:57,299 INFO  [org.jboss.modules] JBoss Modules version 1.2.2.Final-redhat-1
22:21:57,392 DEBUG [org.jboss.modules] Module org.slf4j:main defined by local module loader @438da386 (finder: local module finder @7ead510 (roots: /opt/jboss/jon-server-3.2.0.ER3/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules/system/layers/base))
22:21:57,410 DEBUG [org.jboss.modules] Module org.slf4j.impl:main defined by local module loader @438da386 (finder: local module finder @7ead510 (roots: /opt/jboss/jon-server-3.2.0.ER3/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules/system/layers/base))
22:21:57,427 DEBUG [org.jboss.modules] Module org.apache.commons.beanutils:main defined by local module loader @438da386 (finder: local module finder @7ead510 (roots: /opt/jboss/jon-server-3.2.0.ER3/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules/system/layers/base))
22:21:57,447 DEBUG [org.jboss.modules] Module org.apache.commons.collections:main defined by local module loader @438da386 (finder: local module finder @7ead510 (roots: /opt/jboss/jon-server-3.2.0.ER3/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules/system/layers/base))
22:21:57,451 DEBUG [org.jboss.modules] Module org.apache.commons.lang:main defined by local module loader @438da386 (finder: local module finder @7ead510 (roots: /opt/jboss/jon-server-3.2.0.ER3/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules,/opt/jboss/jon-server-3.2.0.ER3/jbossas/modules/system/layers/base))
22:21:57,480 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,483 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,498 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,499 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,499 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,500 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,501 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,501 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,502 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,503 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,504 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,504 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
22:21:57,506 DEBUG [org.apache.commons.configuration.ConfigurationUtils] ConfigurationUtils.locate(): base is /opt/jboss/jon-server-3.2.0.ER3/bin, name is rhqctl.properties
22:21:57,506 DEBUG [org.apache.commons.configuration.ConfigurationUtils] Loading configuration from the path /opt/jboss/jon-server-3.2.0.ER3/bin/rhqctl.properties
usage: rhqctl upgrade [options]

Upgrades RHQ services from an earlier installed version
    --from-agent-dir <arg>            Full path to install directory of
                                      the RHQ Agent to be upgraded.
                                      Required only if an existing agent
                                      exists and is not installed in the
                                      default location:
                                      <from-server-dir>/../rhq-agent
    --from-server-dir <arg>           Full path to install directory of
                                      the RHQ Server to be upgraded.
                                      Required.
    --run-data-migrator <arg>         This option is valid only when
                                      upgrading from older systems that
                                      did not have storage nodes. The
                                      existing metric data needs to
                                      migrate to the metric storage.  The
                                      upgrade process can trigger this or
                                      give you an estimate on the
                                      duration. If you want to have fine
                                      control over the process, please run
                                      the migrator on the command line.
                                      Options are none (do nothing),
                                      estimate (estimate the migration
                                      time only), print-command (print the
                                      command line for a manual run),
                                      do-it (run the migration)
    --start                           If specified then immediately start
                                      the services after upgrade.  Note
                                      that services may be started and
                                      shut down as part of the upgrade
                                      process, but will not be started or
                                      left running by default.
    --storage-data-root-dir <arg>     This option is valid only when
                                      upgrading from older systems that
                                      did not have storage nodes. Use this
                                      option to specify a non-default base
                                      directory for the data directories
                                      created by the storage node. For
                                      example, if the default directory is
                                      not writable for the current user
                                      (/var/lib on Linux) or if you simply
                                      prefer a different location.
    --use-remote-storage-node <arg>   By default a server is co-located
                                      with a storage node. However, if
                                      this option is set to true, no local
                                      storage node will be upgraded and it
                                      is assumed a remote storage node is
                                      configured in rhq-server.properties.

• The rhqctl upgrade command given in the JBoss ON 3.2.0 Installation Guide is incomplete and will always display usage parameters