There’s more than one way to start, stop, and restart Shinken. Here are some of the more common ones...
Always make sure you Verifying Your Configuration before you (re)start Shinken.
linux:~ # /etc/rc.d/init.d/shinken start
linux:~ # /usr/local/shinken/bin/shinken-scheduler -d -c /usr/local/shinken/etc/schedulerd.ini
linux:~ # /usr/local/shinken/bin/shinken-poller -d -c /usr/local/shinken/etc/pollerd.ini
linux:~ # /usr/local/shinken/bin/shinken-reactionner -d -c /usr/local/shinken/etc/reactionnerd.ini
linux:~ # /usr/local/shinken/bin/shinken-broker -d -c /usr/local/shinken/etc/brokerd.ini
linux:~ # /usr/local/shinken/bin/shinken-arbiter -d -c /usr/local/shinken/etc/nagios.cfg -c /usr/local/shinken/etc/shinken-specific.cfg
Important
Enabling debugging output under windows requires changing registry values associated with Shinken
Restarting/reloading is nececessary when you modify your configuration files and want those changes to take effect.
linux:~ # /etc/rc.d/init.d/shinken restart
linux:~ # kill <arbiter_pid>
linux:~ # /usr/local/shinken/bin/shinken-arbiter. -d -c /usr/local/shinken/etc/nagios.cfg
linux:~ # /etc/rc.d/init.d/shinken stop
linux:~ # kill <arbiter_pid> <scheduler_pid> <poller_pid> <reactionner_pid> <broker_pid>