How to turn the Statistics Poller off at the command line (Legacy KB ID CNC TS22076 )

Document ID : KB000052042
Last Modified Date : 14/02/2018
Show Technical Document Details
This is an example of how to use the startup.cfg to control the poller.   Note again: no changes will take effect until the nhServer stop and then the nhServer start commands are issued.


In the $NH_HOME/sys directory, find the file named startup.cfg. Copy it to startup.cfg.polleron and again to startup.cfg.polleroff. Edit startup.cfg.polleroff, comment out all the lines that look like this:
-----------------------------------------------------
program nhiPoller {
restart all # Restart everything so UI is informed
disable $(_isDistributedConsole) # Disable on Dist. Console
}


program nhiPoller {
restart all # Restart everything so UI is informed
arguments "-dlg" # Dialog poller
disable $(_isDistributedConsole) # Disable on Dist. Console
}


program nhiPoller {
restart all # Restart everything so UI is informed
arguments "-import" # Import Poller
disable $(_isDistributedConsole) # Disable on Dist. Console
}


program nhiPoller {
restart all # Restart everything so UI is informed
arguments "-live" # Fast Live Poller
disable $(_isDistributedConsole) # Disable on Dist. Console
}
-----------------------------------------------------


To turn polling on:
nhServer stop
cp startup.cfg.polleron startup.cfg
nhServer start


To turn polling off:
nhServer stop
cp startup.cfg.polleroff startup.cfg
nhServer start


Keep both copies, and they can be switched at will. This can also be made into a batch/shell script file to make the stop, switch, start as needed.



Related Issues/Questions:
How to turn the Statistics Poller off at the command line
Is there a way to turn off Polling via script
Can eHealth be started without the Stats Poller running

Problem Environment:
eHealth

Causes of this problem:
The Poller cannot be turned off at the command line, however, a similar effect can be achieved by working with the startup.cfg file.  The only caveat is that the eHealth services must be restarted to make any changes in the startup.cfg take effect.

Additional Information:
What starts with eHealth when the services are started (nhServer start) is controlled by a file in $NH_HOME/sys called startup.cfg.  This file controls: what starts, in what order, what options to use, how long to wait before starting the next and what to restart if a process dies.


(Legacy KB ID CNC TS22076 )