Installing the Analytics server

Install the Analytics server by using an .rpm file on a separate server.

  1. To install the Analytics ETL and embedded Jaspersoft software, enter the following command, as the root user, based on the RPM version you are installing:
    rpm -ivh zenoss_analytics-<version>.noarch.rpm
    Replace <version> with the version number you want to install, e.g., 5.0.6-1
  2. Change to the zenoss user and execute the initial database creation procedure. This creates the jaspersoft database (zenoss_analytics), populates it with Zenoss examples and creates a blank data warehouse database (reporting):
    su - zenoss
    /opt/zenoss_analytics/bin/upgrade_db.py

    If this process errors out, you have some environmental issue. Typically, the environmental procedure has not been followed. In the first instance make sure localhost resolves to 127.0.0.1 and that you do not have any files in /tmp that we left over from a previous installation attempt. Correct issues and then rerun the above process again as the zenoss user.

  3. Once this process completes, change back to the root user and enable Analytics to start on boot and then start the service for the first time.
    exit
    systemctl enable zenoss_analytics 
    systemctl start zenoss_analytics
  4. You should immediately tail the Analytics application log (this is a Tomcat log) and watch the log as Analytics starts up for the first time:
    tail -F /opt/zenoss_analytics/logs/catalina.out
  5. On first startup, the data warehouse schema will be adjusted and populated with configuration information appropriate to the current version of Analytics. This process usually takes about 5 minutes, during which the Analytics application will be unavailable. Success of the process is confirmed by the following message in this log and you should wait for it to appear before proceeding further:
    INFO: Server successfully started in <time in ms>
  6. If this first startup errors out, you have some environmental issue. Typically the environmental procedure has not been followed. In the first instance, make sure you have the correct version of mariadb installed. Version 10.0.x is required.
    rpm -qa | grep -i maria