Child pages
  • Regular System Maintenance for NMIS

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added fpingd info

Like any system some regular maintenance will keep NMIS running smoothly, we have automated as much as we can and will continue to do so, here are a few things to check on. 

Table of Contents

Check and Audit the configuration


These commands tell you what folders and permissions are incorrect, and then just fix it.


Code Block

Ensure that DNS or host name changes reach the relevant parties

As NMIS mostly runs periodically, out of cron, changes to your infrastructure outside of NMIS are usually picked up automatically. There is, however, one exception: runs persistently and permanently (to minimize reaction time). NMIS starts if there is none running and then leaves it to its own devices.

As a consequence, if you make changes to your DNS infrastructure or rename hosts, then it's necessary to notify of  those changes: simply run /usr/local/nmis8/bin/ restart=true after you've made your changes.

Please note that caches information heavily, so restarting it very frequently is counterproductive.

Log rotation is the most important factor