Skip to main content

Tarball Installation

This topic describes how to install Moogsoft Enterprise on a single host using the tarball archives, previously known as the non-root install.

Follow these steps if you do not have root access to the machine or machines on which you will install Moogsoft Enterprise.

To install Moogsoft Enterprise in a highly available environment, see High Availability Installation.

For RPM installation steps, see RPM Installation.

Before you begin

Before you start to install Moogsoft Enterprise, complete all steps in Moogsoft Enterprise - Online Tarball pre-installation or Moogsoft Enterprise - Offline Tarball pre-installation.

Install Moogsoft Enterprise

To complete a tarball installation of Moogsoft Enterprise v8.2.0, perform the following steps:

  1. Download the tarball installer, using one of the following options:

    • Download via a web browser from and user the Yum user credentials provided by Moogsoft support.

    • Use the following cURL command, substituting your "speedy" Yum repo user credentials:

      curl -L -O "https://<username>:<password>"
  2. Optional: GPG key validation of the tarball

    For users wishing to validate the tarball before installation, the following steps must be followed:

    1. Download the key from this site:
    2. Copy the key to the server onto which the tarball will be installed (it will be a .asc file)

    3. Import the key:

      gpg --import 0A8FD9AB6F1693A1967B3B8CB919E617EC6946C2.asc
    4. Download the moogsoft-enterprise-8.2.0.tgz.sig file from the same 'speedy' path:

      curl -L -O "https://<username>:<password>"
    5. Ensure both the tgz and the .sig file are both in the same folder, then copy the following command into a bash terminal and run it to perform the validation:

      gpg --verify moogsoft-enterprise-8.2.0.tgz.sig moogsoft-enterprise-8.2.0.tgz
    6. Confirm that the report states:

      Good signature from "Moogsoft Information Security Team "<>"
  3. Unzip and untar the Moogsoft Enterprise distribution archive in your working directory:

    tar -xf moogsoft-enterprise-8.2.0.tgz

    The distribution archive contains the following files:

    • A README.txt file

    • The installation script:

    • The distribution archive: moogsoft-enterprise-dist-8.2.0.tgz

    • The integration distribution archive: moogsoft-enterprise-integrations-dist-8.2.0.tgz

  4. Run the Percona installation script (this requires the 'nc' package to be present on the system as a prerequisite):


    The script guides you through the installation process.

    To configure a single database node on the same server as Moogsoft Enterprise use these settings:

    • Configure Percona as "Primary".

    • Do not set the server to "DB only".

    • Set the first database node IP address to the server IP address.

    • When prompted to enter the IP addresses of the second and third nodes, press Enter to skip these settings.

  5. Source the bashrc file:

    source ~/.bashrc
  6. If the root user installs the tarball, Moogsoft Enterprise must not be installed in the /root directory

  7. Execute the installation script in your working directory to install Moogsoft Enterprise.


    The script guides you through the installation process. The installation directory defaults to <working-directory>/Moogsoft. You can change this if you wish.

  8. Set the $MOOGSOFT_HOME environment variable to point to your installation directory, and add $MOOGSOFT_HOME/bin/utils to the path. For example:

    echo "export MOOGSOFT_HOME=~/moogsoft" >> ~/.bashrc
    echo "export PATH=$PATH:\$MOOGSOFT_HOME/bin/utils" >> ~/.bashrc && \
    source ~/.bashrc

Initialize Moogsoft Enterprise

When the installation process is complete, initialize Moogsoft Enterprise as follows:

  1. Configure the Toolrunner to execute locally by setting "execute_locally: true" in $MOOGSOFT_HOME/config/servlets.conf:

    sed -i 's/# execute_locally: false,/,execute_locally: true/1' $MOOGSOFT_HOME/config/servlets.conf
  2. To initialize Moogsoft Enterprise, you run the initialization script moog_init.

    You can run this script with the -k flag to set processes (for example Percona, RabbitMQ, Moogfarmd) to automatically restart when you reboot the system. For example:

    $MOOGSOFT_HOME/bin/utils/ -kI <zone_name> -u root

    If you do not want to set these processes to automatically restart when you reboot the system, run this script without the -k flag. For example:

    $MOOGSOFT_HOME/bin/utils/ -I <zone_name> -u root

    If you then decide after you have finished the install that you want these processes to automatically restart after all, run:

    [ -z "$(crontab -l|grep" ] && (crontab -l; echo -e "*\t*\t*\t*\t* $MOOGSOFT_HOME/bin/utils/ 2>&1") | crontab -

    The moog_init script prompts you to accept the End User License Agreement (EULA) and guides you through the initialization process.

    When asked if you want to change the configuration hostname, say yes and enter the public URL for the server.

    For more information see Configure Services to Restart.

  3. Restart Moogfarmd and Apache Tomcat:

    $MOOGSOFT_HOME/bin/utils/process_cntl moog_farmd restart
    $MOOGSOFT_HOME/bin/utils/process_cntl apache-tomcat restart

Configure Opensearch/Elasticsearch heap size

The minimum and maximum JVM heap sizes must be large enough to ensure that Opensearch/Elasticsearch starts.

See Finalize and Validate the Install for more information.

Tarball inetd crontab setup

The process which allows a programmatic check (via HTTP endpoint) of whether Percona MySQL is available (inetd) needs to start when the server itself is started or restarted (along with Percona itself).

For Tarball deployments, this is controlled using crontab which runs once per minute. The following command can be run to add the appropriate crontab entry:

[ -z "$(crontab -l|grep install\/inetd)" ] && (crontab -l; echo -e "*\t*\t*\t*\t* [ -z \"\$(ps ax|grep install\/inetd|grep -v grep)\" ] && { nohup ~/install/inetd &>> ~/inetd_\$(date +\%Y\%m\%d-\%H\%M\%S).log & }") | crontab -

If the log file is not needed this part of the command can be updated as follows:

nohup ~/install/inetd &>> >/dev/null &

If the script fails to restart the inetd service when it is stopped, ensure the PATH set in the crontab to define the main bin directories and the mysql bin directory (as it is required by the clustercheck percona script).

Disable the enhanced Content Security Policy (optional)

Allow access to external domains

Configure Moogsoft Enterprise for use with Safari

Run an unattended installation

Verify the installation

Change passwords for default users

Install Moogsoft Add-Ons

Moogsoft periodically releases add-ons to extend and enhance the core Moogsoft Enterprise functionality. For example, new Workflow Engine functions, new Workflow Engines, or Integrations tiles. All add-ons releases are cumulative and include the fixes from previous releases.

Once you have finished upgrading or installing Moogsoft Enterprise, you should install the Moogsoft Enterprise add-ons to ensure you have the latest version.

See Install Moogsoft Add-ons for more information on how to install the Moogsoft Enterprise add-ons.