- The individual performing this installation has a bit of Linux experience.
Root access is available.
- A working copy of NMIS (starting from an NMIS VM is a good idea, if you prefer to install it yourself see the NMIS 8 Installation Guide) on the same server that opTrend is being installed on.
- An (evaluation) license for opTrend
- Download opTrend from the Opmantek website.
Copy the opTrend tarball to the server in question, using
sftpor similar. Make a record of where you put the tarball (likely
root's home directory).
Become root and unpack the tarball:
Start the interactive installer and follow its instructions
- The installer will interactively guide you through the steps of installing opTrend. Please make sure to read the on-screen prompts carefully.
- When the installer finishes, opTrend is installed into
/usr/local/omk, and the default configuration files are in
/usr/local/omk/conf, ready for your initial config adjustments.
- 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 logfile.
For detailed information about the interactive installer please check the Opmantek Installer page.
Post Installation Steps
Stop all optrend cron jobs by commenting them out
If the seds collection is capped it will need to be "uncapped" which is not a simple task. Note, that if it has been capped for a while (and running WiredTiger) it will not have been working so your server will not have been working and the history is useless. Note: the history can be recreated, 3 weeks worth is no problem.
If you can handle losing the data take that path, it is possible to bring back old data, to drop the database the command is db.dropDatabase(), use this command very carefully, verify what you are dropping with the command db.getCollectionNames(), the result should be like below.
- If not, use mongodump to dump just the seds collection, then drop the seds collection, then re-import the data to the seds collection which should bring it back un-capped
Collections in opTrend are no longer capped, each entry is set to expire after 21 days. This value is configurable, adjust opCommon: 'optrend_seds_expire_after_seconds'
Set expire_at value on existing documents, if you have not existing documents skip this step, be sure to change the date to a date that makes sense for you:
opTrend documents for the current week need to be replaced with the newer format, to do this force an update which will replace them:
If you have dropped/removed old data you can re-create it by running these commands:
Enable all optrend cron jobs by removing comments added in the first step: