Table of Contents

There was no default abort_plugins_after option in the configuration. This value can be added in Config.nmis:
```
'overtime_schedule' => {
    'abort_plugins_after' => 7200, # Seconds
   ...
}
```
The schedule keeps adding these jobs into the queue. The workers can discard these jobs changing the configuration options postpone_clashing_schedule to 0.
```
'postpone_clashing_schedule' => 0,
```

After theses two changes, nmis9d daemon needs to be restarted.

...

If you edit or transfer NMIS files across machines then some file permissions may change for the worse, and the NMIS9 selftest may alert you about invalid file permissions.
The fastest way to resolve this is to use the nmis cli with the act=fixperms argument.
The config-backup argument instructs nmis-cli to produce a backup of your configuration files right now;
normally configuration backups are performed automatically and daily.

Performance data

From nmis 9.2, new actions where introduced in NMIS 9.2 to collect performance data:
collect-top-data will collect and process the information of the top data and place it on a csv file. It will run every 5 minutes by a cron job. The files will be purge every 8 days by default:

Code Block
./nmis-cli act=collect-top-data

collect-performance-data will run a set of commands specified in the file conf/performance.nmis. It will run every hour by a cron job and will be purged every 8 days by default:

Code Block
./nmis-cli act=collect-performance-data

Logging and Verbosity

...