...
If you are running an update for all nodes it may take a while to complete; as such you may run an NMIS update in the background so you can exit the SSH session and leave it running. To run in the background add the command "nohup " to the beginning, nohup is No Hangup and means it will continue running when you exit the shell. The following command shows how force an update for one node at a time (a good way to distribute the load). You can also schedule an update for all nodes by removing the job.node argument.
| Code Block |
|---|
./bin/nmis-cli act=schedule at="now + 5 minutes" job.node=testnode job.force=1 |
To run an NMIS update for a single node, optionally with debug.debug which will result in debug files in /tmp/
| Code Block |
|---|
./bin/nmis-cli act=schedule job.type=update at="now + 5 minutes" job.node=testnode job.force=1 job.verbosity=9 |
If adding a large number of devices it might take sometime to complete the adding. This is because the first time a node is added to NMIS it needs to create all the RRD files for performance data, this only takes a few seconds per file, but each node may have 10 RRD files or more, so this compounds to a large number of seconds very fast when adding 1000's of devices at a time.
...