...
NMIS has configurable features to ensure that the polling operations keep up and complete timely while not overloading the polling server.
TABLE OF CONTENTS
| Table of Contents |
|---|
RELATED ARTICLES
NMIS Poll Cycle Overview
NMIS performs two main operations periodically, collect and update. An update is really a node discovery, and determines what a node can do and how it should be managed. Updates are performed infrequently, usually just once a day. The collect operation on the other hand is the 'work horse' of NMIS where the main SNMP and other protocol polling activity happens. Collects are performed every 5 minutes by default.
Depending on your configuration, the thresholding and summary processes will run with the main collect operation or can be run seperatelyseparately; details about that separation can be found in the article Scaling NMIS Polling.
...
By default this is set to undef, and the feature is disabled if the value is undef or 0 (zero).
When enabled (by setting the value to the maximum allowed runtime in seconds), this feature sets up a process timeout (alarm) for each NMIS child process (in the documentation also often called a "thread"), which terminates the process if it remains stuck or running for too long. This serves as a safeguard for nodes that are totally unresponsive or much too slow in responding, and which would otherwise keep the collect operation from completing.
...
Please note that the operation of the max_child_runtime feature is independent of ignore_running; that is, you can use neither, one, or both of these features at the same time.