Troubleshooting
CloudShark Enterprise 4.0.0 and later is distributed as an OVA virtual machine image. These legacy instructions should only be followed after contacting support@qacafe.com for assistance.
If you already have CloudShark Enterprise installed on a virtual machine, please follow the OVA Migration instructions to upgrade.
CloudShark runs on top of a RHEL-based Linux installation which meets our system requirements. The system can be bare metal hardware, a virtual machine, or on your public or private cloud infrastructure.
If you are having trouble with the installer, the following additional options may help resolve your issue. As always, contact QA Cafe Support for help. Customers have access to unlimited tech support and we are happy to help!
Installer Flags
Usage: ./cloudshark-installer-v4.0.0.el8.run -- [options]
Install CloudShark
-h, --help Display help for this command
-l, --license license_file License to copy to /usr/qacafe/licenses/
-d, --debug Enable verbose output
-f, --force Ignore errors
--upgrade Do not prompt if this requires an upgrade from the
previous version. The default behavior is to prompt
the user to continue if an older version is detected.
--repo-only Create the 'cloudshark' repository only
--trust-yum Leave the yum repos that are enabled alone when
performing any actions. The default is to disable
everything but the new 'cloudshark' repository.
Debug Output
The --debug
flag turns on Bash command logging (set -x) for every
command run by the installer. This can be helpful for determining where
a command is failing, and may be requested by Support.
To save the output of the installer while also seeing it on screen, use
the tee
command to save to a file:
./cloudshark-installer-v4.0.0.el8.run -- --debug 2>&1 | tee debug.log
Force
By default, the installer will bail out and exit if any subcommand fails. In a normal installation, we do not expect any errors, however it may be necessary for the installer to ignore any errors it encounters and continue.
Combining this option with --debug
is recommended.
./cloudshark-installer-v4.0.0.el8.run -- --force --debug
Repo-Only
If you are setting up a local mirror repository and wish to include
CloudShark, or are an integrator who wants to perform a custom
installation, you can use the --repo-only
flag to copy the packages to
the system, but do not install them.
./cloudshark-installer-v4.0.0.el8.run -- --repo-only
The repository will be created under /usr/cloudshark/repo
and a new
repository named cloudshark
is configured under /etc/yum.repos.d/
to
use.
Missing Dependencies
If the system was not installed with the stock Rocky Linux 8 Minimal image, it is possible that certain dependencies are not available. These may still be retrieved from the system’s YUM repositories.
These must be configured correctly either to connect to the internet, or to access local DVD media containing a package repository.
The CloudShark Installer by default disables all other repositories when
installing CloudShark locally. This behavior can be disabled by
including the --trust-yum
option when running:
./cloudshark-installer-v4.0.0.el8.run -- --trust-yum
Please mention to QA Cafe Support if you are trying this option as it will help troubleshooting efforts.