Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

opCharts 3

Info
titleInstaller Versions

If you are installing a version of opCharts compiled prior to 2016 please see this page: Pre 2016 Installations

Table of Contents
maxLevel2

Prerequisites

Installation Procedure

Preparing the pre-requisites

On Debian and derivatives, run this as root:

Code Block
languagebash
apt-get install apache2 rrdtool apache2-utils unixodbc odbcinst tdsodbc

On CentOS/RHEL, run the following commands as root:

 

Code Block
yum install http://mirror.optus.net/epel/6/i386/epel-release-6-8.noarch.rpm
yum install httpd-tools freetds unixODBC rrdtool httpd
echo -e "[FreeTDS]\nDriver = /usr/lib64/libtdsodbc.so.0" | odbcinst -i -r -d 

Installing opCharts

  • Download opCharts and the custom rrdtool from the Opmantek website.
    Copy the two tarballs to the server in question, using scp or sftp or similar. Make a record of where you put the tarball (likely root's home directory).
  • Become root and unpack the tarballs:

    Code Block
     # as root
    cd /usr/local
    # if the tarball was saved in a different location, adjust the ~ in the following command 
    tar xzf ~/opCharts-THEVERSION.tar.gz
    tar xzf ~/rrdtool-binpkg.tgz
    cd /usr/local/omk 
    cp -r install/*.nmis install/charts install/users.dat install/data_sources.json conf/
  • Create the required nmis user
    As root run

    Code Block
    useradd nmis

...

  • NMIS installed on the same server that opCharts is being installed (NMIS version >=8.5.6G).
  • The individual performing this installation has a small bit of Linux experience.
  • Root access is available.

...

  • Internet access is required for installing any missing but required software packages.
  • opCharts License (evaluation available here).
  • All licenses are added/updated at https://<hostname>/omk/opLicense .

Preparation

Installation

opCharts is distributed in a self-extracting download format that simplifies the installation process. More information on running the installer can be found on The Opmantek Installer page.

Transfer the opCharts installer file onto the server in question, either by direct download from the Opmantek website, or from your desktop with scp or sftp or a similar file transfer tool.

  • Start the interactive installer and follow its instructions:

    Code Block
    sudo sh ./opCharts-Linux-x86_64-3.0.7.run
    ...
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    opCharts (3.0.7) Installation script
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    ...
    This installer will install opCharts into /usr/local/omk.
    To select a different installation location please rerun the
    installer with the -t option.


  • The installer will interactively guide you through the steps of installing opCharts. Please make sure to read the on-screen prompts carefully.
  • When the installer finishes, opCharts is installed into /usr/local/omk, and the default configuration files are in in /usr/local/omk/conf, ready for your initial config adjustments.

Initial System Configuration and Integration steps

  • Make sure the opCharts logs are rotated
    If your system runs  logrotate daily and automatically (i.e. Debian/Ubuntu), simply copy conf/omk-rotate.conf to /etc/logrotate.d/.

    Code Block
    themeEmacs
    # on Debian/Ubuntu, as root:
    cp /usr/local/omk/conf/omk-rotate.conf /etc/logrotate.d/

    On other systems you will have to create a suitable cron job:

    Code Block
    # as root: crontab -e# insert the following lines, then save and quit 
    # Check to rotate the logs 02:05 every day
    2 5 * * * /usr/sbin/logrotate /usr/local/omk/conf/omk-rotate.conf
  • Integrate opCharts with the web server
    become root and run the following commands:

    Code Block# as root # non-debian: cp A detailed log of the installation process is saved as /usr/local/omk/install.log, and subsequent upgrades or installations of other Opmantek products will add to that log file.

Initial Configuration

  • You will need to adjust the NMIS-related settings:
    open /usr/local/conf/opCommon.nmis in an editor, go to the nmis section and change the nmis_dir to reflect your NMIS installation. 
    The result should look similar to the following (but there might be extra settings related to other products):

    Code Block
    'nmis' => {
        'nmis_dir' => '/usr/local/nmis8',
        'nmisConf' => 'Config',
        '<nmis_logs>' => '/usr/local/nmis8/logs',
        'nmis_host_base' => 'http://localhost',
        'nmis_cgi_url_base' => '/cgi-nmis8',
        'prefer_local_nmis' => 'false'    
      },


  • After completing your configuration changes you'll need to restart the opCharts daemon. Run the following commands as root: 

    Code Block
    # don't forget to become root, using sudo sh or su
    service opchartsd restart
    service omkd restart
    # to verify the status of the daemons:
    service opchartsd status
    service omkd status


  • Authentication
    The installer will backup /usr/local/omk/conf/

...

  • users.dat and then create a symlink to users.dat in your NMIS directory if it was found during installation.
    If the NMIS users.dat file could not be found during installation the existing users.dat file in /usr/local/omk/conf/

...

Note: If this step is not taken, then the opCharts web GUI will only be available on port 8042 and you'll need to adjust your web browser accordingly.

Make the opCharts service daemon start automatically with the system
become root, then run the  following commands:

...

  • will be used.
    If /usr/local/omk/conf/users.dat is not found the default users.dat file will be copied to /usr/local/omk/

...

Start the opCharts service daemon
become root, then run the following commands:

Code Block
service omkd start

...

Where to go from here

First you should test opCharts: open up a web browser, and point it to

...

http://<yourserverip>/omk/opCharts

...

, you will have to enter your license first, then you will see opCharts' main dashboard.

...

 

...

See the authentication bullet point above for user/password info.