Overview of the Major Components of NMIS9

**starting directory is "/usr/local/nmis9" for the following examples below **

The NMIS9 daemon bin/nmisd

...

When the Updates and Collects last occurred can be found using :the GUI, in the Menu "System > Configuration Check > Node Admin Summary".

Fault-recovery

If a job remains stuck as active job for too long then the nmis daemon will abort it and reschedule a suitable new job. Such stuck jobs can appear in the queue if you terminate the nmis daemon with act=abort  or service nmis9d stop, because these actions immediately kill the relevant processes and don't take active operations into account.

...

• 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.

...