...
This document is based on the tests mentioned on the Device Troubleshooting Process in NMIS page .
Table of Contents
...
Problem description
In order to run the Troubleshooting Wizard, we must have a very detailed description from the client that gives us a good overview of the situation that it is presenting.
...
Troubleshooting Wizard: Install and Run
The script installation file (**********sh) and the two complementary scripts for its execution (**********), can be downloaded from the following GitHub link: * ***************
All three must be uploaded to the same folder on You can find the necessary files in the following links (Troubleshooting Wizard file and 2 companion scripts):
Link: https://github.com/tom-tics/TS_Wizard_NMIS9_OPMANTEK
Similarly, a README file showing installation instructions:
The three main files must be uploaded to the server where the analysis will be performed using an FTP client (such as FileZilla).
Once the three files are already on the server, it with the necessary permissions, the script must be executed with the command: sh *************.sh
Once we have executed the file, we will access the initial screen, where the as follows: sh TS_WIZARD_OMK-9.sh
A welcome screen will be displayed and the Enter key must be pressed to access the main menu.
Pressing the Enter key will show some details of the Operating System are shown, such as the version of Linux the Operating System and a small summary of the memory and CPU of the system.
In the same way, the Main Menu is shown, where we will find the different options that we can access:
- Execute Healthcheck: we can perform a complete review of the server.
- Review NMIS Configuration Consistency: we will be able to review the consistency of the most important NMIS configuration files.
- Nodes Troubleshooter: we will be able to review the behavior of the nodes added to NMIS.
- Execute Smart Diagnostics – Creates : creates a full system diagnostic in a .tar.gz file, which can be attached in case a ticket needs to be opened with Opmantek Support.
- Create System Backup File: Creates creates a .tar.gz file that will contain a backup of the /etc/* and /usr/local/* folders.
- Execute Support Automation Tool – Generates : generates an NMIS and an OMK support file, which can be attached in case a ticket needs to be opened with Opmantek Support.
...
Similarly, check that SELinux is disabled.
If any service is detected to be down and is important for system operation, it must be restarted as indicated by the script.
...
1. Compare file configurations
Allows you to compare the files:
...
the files:
- /usr/local/nmis9/conf-default/Config.nmis/usr/local/omk/install/opCommon.nmis and /usr/local/omknmis9/conf/opCommonConfig.nmis
In order to find any inconsistency in the configuration that may be causing a problem with NMIS and/or the modulesthe operation of NMIS.
2. Execute fixperms
...
rutine
Automatically executes the command /usr/local/nmis8nmis9/admin/ fixperms.plbin/nmis-cli act=fixperms , which allows the operator to general fix the permissions of all system files.
...
3. Crontab checking
Runs a configuration check of each of the cron files that NMIS and the modules work with, to check that there is no routine that is causing a conflict that could affect the operation of the system.
In the same way, it executes an ll in /etc/cron.d/ to check that there are no backups inside that folder, since it can cause problems for the execution of the tasks and it gives a tip so that, if backups are found, are moved from folder or deleted.
4. Last changed files
...
At the end, a tip is displayed for the operator to check if any recent file changes are causing a problem in the system.
5. Server Performance Tuning
...
At the end of the execution, it shows the Wikipedia in which all this movement for tuning is detailed: Configuration Options for Server Performance Tuning .
3. Nodes Troubleshooter
...
The command /usr/local/nmis9/bin/nmis-cli is executed act=schedule job.type=collect job.verbosity=1 job.node=nodename job.force=1
8. Event search
It allows searches in the /usr/local/nmis9/logs/ and /usr/local/omk/logs/ folders, which will make it easier for the operator to investigate any fact or event that is causing a server failure.
...