This document covers Linux Agent installs. Because of the nature of different Linux versions, there are a few additional steps needed for Viakoo Activation. In summary, they are as follows:
- Download the agent to a location on your Linux server.
- Change their permission state to executable
- Run the Reader Agent (ViakooRA) installer under root privileges.
- Run the Communication Agent (ViakooCA) installer under root privileges.
- Bring up the Communication Agent’s web console to complete activation.
- Verify that your local system(s) firewall settings are enabled for ViakooRA
Download the Linux Agents
Click on the Linux Recorder Agent (RA) Installer and then the Linux Communication Agent (CA) Installer to download both installers. Copy the Linux Recorder Agent (RA) Installer onto every Linux server you want to monitor.
Change to Executables
From a “Terminal” window in your Linux system, you need to change both installers to “executable” with the following command:
chmod +x viakoora*.run viakooca*.run
To verify you done it correctly, type the following command:
ls -l *.run
You should see the two installers with the following permissions:
$ ls -l *.run
-rwxrwxr-x 1 root root 129604396 Jun 11 15:25 viakooca-1.0.4746.run
-rwxrwxr-x 1 root root 155232499 Jun 11 15:25 viakoora-1.0.4746.run
The ‘x’ in the permissions indicates they have been set to executable.
The installers need to run under ‘root’ permissions in order for them to collect necessary information. It is useful to install the RA first and then the CA.
Run the Recorder Agent Installer
To install the Recorder Agent, enter the following command:
The system will prompt you for the ‘root’ password for your system. Enter it and hit return. You should see the following:
$ sudo ./viakoora*.run
Copying to a temporary location...
Verifying archive integrity... All good.
Uncompressing recorderagent 100%
Enter install path: [/opt/viakoo]
The system gives you the option of installing the Recorder Agent’s programs and configuration information in a different location. If you would like it to install the agent somewhere else, enter that path. Otherwise, hit <CR> (return key).
You will then see the installer storing files on your system.
Repeat this process for each linux system at your site you wish to include in your Viakoo collection.
Run the Communication Agent Installer
Repeat this process only typing in the following command for the Communication Agent:
You will be prompted for the root password and then the storage location if you want to change it. After you hit enter, you will see information indicating the installer is storing files onto your system.
Bring up the Communication Agent Console
Open a browser window and enter the following URL:
This should bring up your CA’s Activation screen. Go through the steps to activate your site and configure your RAs into the collection cycle, following the same procedures as you would on Windows systems.
Verify Local Firewall Settings Are Enabled
If you are having trouble reaching your Linux-based ViakooRA(s) from your ViakooCA, you may have to adjust your firewall settings on your Linux system(s) that maybe blocking communication between the CA and RA. The Windows agent installer automatically adjusts local firewall settings to make sure communication ports between the CA and RAs within a site are open. Because Linux systems use a variety of firewalls, the Linux installer agent requires the installation administrator to verify and adjust these settings manually.
The ViakooRA listens on port 10106. This port needs to be opened in each systems' firewall settings to enable the ViakooCA to communicate with the ViakooRA. This is needed even when the ViakooCA and ViakooRA are on the same system.
Additionally, there maybe more than one service that controls access to these ports depending on your configuration of Linux and each one may need adjustment to enable the ViakooRA communication port.
Firewall setting on Ubuntu Linux:
- Uncomplicated Firewall (ufw) configuration is most common way to configure firewall settings
- if necessary, see configuring iptables directly when ufw is not present (versions prior to 8.04)
- It is possible that your system could be using firewalld instead of ufw (more common on RedHat Fedora/CentOS Linux).
If, after confirming that port 10106 is open and the ViakooCA is still unable to reach the ViakooRA, you may have an additional layer of application security that might be blocking access. In this case, investigate whether you have application security running and their settings are properly configured to enable the ViakooRA to communicate through port 10106. The most likely application security services are as follows:
- apparmor - most common application security on Ubuntu Linux
- If apparmor is not present, investigate whether you have selinux running (more common on Fedora/CentOS Linux)