This document explains the most essential installer features.
- Installation of Opmantek Applications
- Uninstalling Opmantek Applications
Installation of Opmantek Applications
- With the exception of Open-AudIT, which can be installed on Windows Server or Linux, all Opmantek applications are available for Linux 64-bit systems only.
Redhat/CentOS6, Debian 7, Ubuntu 10 and newer are supported (basically anything running glibc 2.3 and up).
- The latest versions of our applications can be found at : https://opmantek.com/network-tools-download/
- To run the installer you need superuser/root access on the system in question.
- Please note that as of Feb 2017, all Opmantek applications require that
/tmpis mounted with execute permissions (i.e. mounted without the
See below for an alternate procedure if your
Opmantek Applications Download Formats
In the past our applications were provided in the form of a compressed tar file, which required some manual steps for unpacking and installer invocation. As of February 2016 we've switched to a self-extracting download format which make this aspect much more user-friendly.
All Opmantek product releases from 16 June 2016 onwards include the installer in both pre-compiled and source form, to ensure that you can install the software on a system without Perl present. The source form of the installer is provided for diagnostic purposes; by default the self-extracting run file will start the pre-compiled installer version.
When you download an Opmantek Application, the file will be called
<product name>-<version>.run and your browser will likely prompt you regarding what to do with this '.run' file; you should tell it to Save the file. If you are installing the application onto a different system than the one where you downloaded the file, you'll have to use
scp or some other file transfer method of your choice to transfer the .run file to the target system.
Starting the Installer
Starting the self-extracting installer is trivial: you simply tell your shell to run it.
Assuming your downloaded file is called
opProduct-version.run, you would do one of the following:
- The simplest way to achieve this is to type "
- You can also modify the permissions of the .run file to indicate that it is executable, then start it directly
To do so, you'd run
"chmod u+x ./opProduct-version.run" followed by "
The installer will first run an archive integrity check, decompress the archive, then start the interactive phase of the installation.
Please note that the installer needs to run with
root privileges, and will terminate with an error message if this requirement is not met.
Alternative procedure if your /tmp should be mounted
As pointed out above, the installer needs do extract the product files into a temporary directory and then restart using the extracted programs.
This fails if the standard temp directory
/tmp is mounted with the
noexec mount flag.
The simplest workaround is to pick a different location for the temporary directory that is not affected by
noexec and tell the installer about it by setting the environment variable
- Become the superuser with
Pick a suitable directory
root's home directory is likely ok. Running
mountshould confirm - look for
noexec. We recommend that you use an empty new temporary directory for the installer as that simplifies cleanup.
Tell the installer to use this local temporary directory and start the installation
Clean up the temporary directory
NOTE: It is important to understand that the omkd daemon, which is required for rendering the GUI via Apache also requires the /tmp directory to be mounted as executable or the daemon will crash after start. You can. however, redefine the /tmp directory for omkd by adding the following lines into /etc/init.d/omkd
Add them at line 18 (after the line # Do NOT "set -e").
Obviously, /tmpdir will need to exist. If the admin of the box needs to run any OMK programs manually, they will need to have exported /tmpdir before they do so.
Available Installer Options
You can see an overview of the available options related to the self-extracting aspect when you start a run file with
--keepensures the unpacked data left behind (in the
opProduct-versiondirectory) after the interactive installer component has finished.
--noexeccauses no interactive installer component to be run.
The combination of
--keep provides the equivalent of unpacking the tar files provided with earlier releases.
You can also pass options to the interactive installer component, but these must follow after a "
--" delimiting argument:
- If you want to perform a simulation run of the installation, use the
-noption: the installer will only print what it would do, what files it would copy and so on, but will not perform any of these steps.
- By default the installer is interactive and will prompt you for decisions and confirmations; If you want to run it in non-interactive batch mode, use the
In this case all dialogs and prompts are automatically answered with the default answer (usually 'y').
- Please note that in non-interactive mode the installer will abort upgrades if critical incompatibilities (e.g. license type) are detected; the option to overrule the installer in such situations is only present when the installer is running interactively.
- Certain installer choices can be preset for non-interactive mode:
- Setting the environment variable
NO_LOCAL_MONGODBto a non-empty value instructs the installer to not install a local MongoDB server even if none is present.
- Setting the environment variable
- If you want to install the product into a non-standard directory, you can pass the argument
-t <targetdir>to the installer component.
Please note that you will have to adjust a number of configuration files in this case.
- It is possible to generate more detailed diagnostic output in the installer log file, using the
sh ./opFlow-3.0.5.run --keep -- -n would start the installer in simulation mode (
-n) and leave the unpacked files behind (
--keep) when done.
Logs and Backups
The installer saves a log of all actions taken, files copied etc. in the installation directory as
install.log, ie. normally it'll be in
/usr/local/omk/install.log. Subsequent upgrades or installations of other Opmantek products will add to that logfile, so you may very well want to remove or clear the install.log file before upgrading or adding extra software.
Unless this is the very first installation of an Opmantek product on this system, the installer will offer taking a backup of all affected files before the installation commences. This backup will be saved in the
root user's home directory as omk-backup-YYYY-MM-DD.tgz. The backup includes:
- all the directories that the installer will later copy files to,
- the old software manifest,
- and the old install.log.
Wherever possible the installer will help you with the installation of any missing software dependencies, using
apt-get depending on your operating system platform.
You'll see a prompt similar to this:
If you answer this prompt with 'n' the installer will continue the installation, but the software will likely not work (at all or partially) until you manually fix the missing dependency.
In other cases where the dependency is a "soft" one or where automatic installation isn't an option you will be shown a warning dialog about the missing dependency and the installer will wait until you confirm before continuing.
Product Coexistence, Migration and Upgrades
Before installing any Opmantek software components, a thorough check of the existing state of your system will be made to ensure that the new product does integrate correctly with other already existing Opmantek products. This check relies on the software manifests stored in the installation directory (default
/usr/local/omk) and the product tarball, and thus won't be fully precise if no manifests exist.
When an installation of older/legacy Opmantek products is detected or if the manifest is missing, then the installer will take a comprehensive backup snapshot of your installation directory first. This is to ensure that you could revert back to the pre-installation state quickly and with minimal downtime, should the installer unexpectedly fail the coexistence check or break existing old applications. Here is an example of the prompts in this situation:
If the installer detects an unresolvable conflict between the module dependencies for your existing products and the new product, it will abort the installation with a detailed error message: in this case we recommend that you contact Opmantek Support for a resolution.
For product upgrades the installer will perform the same check and upgrade only the files and modules that are required, taking great care to not damage the function of any other existing Opmantek products. In that case the installer will also recommend a shut down of any Opmantek daemons before the installation commences, so that all files can be copied safely and without negatively affecting running daemons.
Integration and Initial Configuration
After all necessary files have been installed in their appropriate locations the installer will take care of integrating your product with the operating system, web servers and so on.
Typically this will at the minimum involve the installation of up-to-date init scripts for the Opmantek daemon, integration of the Opmantek GUI with your Apache webserver, setting up of log rotation and the optional first start of the Opmantek daemon. The dialogs in question are all very similar to the following:
If you answer the prompt with 'n' the installer will continue after displaying a brief outline of the steps you'll have to take manually later and a confirmation dialog:
The installer will also offer to copy any missing default configuration files from the
install to the
conf directory to provide you with a basic initial configuration to start with.
In case of an upgrade it'll offer to import any new default config settings. Furthermore, you will be given the opportunity to have all your configuration files compared to the defaults:
Finally, at the end of the installation process you'll see a message like this:
- What's this warning about "incorrect checksum detected"?
This can happen very infrequently, if you are installing an older Opmantek application on top of newer ones, or if you've made extensive changes to your system's Opmantek files.
We strive hard to line up our releases properly so that everything meshes cleanly, but every now and then there are minor changes to files that older installer versions aren't quite aware of.
In general this warning dialog is safe to answer with 'yes' and the installer will leave your system in a consistent working state (by replacing the unrecognizable/mismatching file with a known good version from the shipped product).
Please feel free to submit your comment here or email us with your questions!
Uninstalling Opmantek Applications
Because Opmantek applications share code and modules wherever possible, uninstalling a single application is not completely trivial.
Using the Uninstaller
As of September 2016, all application releases include an unistaller tool which performs a limited uninstallation of a particular application. It's easy to use, but primarily disables an application without removal of application data or files. The uninstaller offers a simulation mode, too. You simply start it up with the application module in question, e.g.
If you desire a more permanent and complete application removal you will have to remove all Opmantek applications: it is infeasibly complicated to determine which files and code modules are removable and which have to remain behind to keep the remaining applications in working shape.
A checklist for complete removal would involve the following steps:
- Removal of all Opmantek daemon init scripts from
This may include init scripts for
You should stop the daemons before removing the init scripts.
- Removal of
cronschedules for the Opmantek applications
This may include files in
- Removal of all of
The latter two may not be present (but will be if your system started as an Opmantek Virtual Appliance).
- Cleanup or removal of the Opmantek applications' MongoDB databases
Unless you are actively using MongoDB you might simply stop the
mongoddaemon and remove the database files (typically under
/data/mongodbfor the Opmantek VM).