...
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.
...
Allows you to compare the files:
- /usr/local/nmis9/installconf-default/Config.nmis and /usr/local/nmis9/conf/Config.nmis/usr/local/omk/install/opCommon.nmis and /usr/local/omk/conf/opCommon.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.
...