There’s more than one way to start, stop, and restart Shinken. Here are some of the more common ones...
Always make sure you verify your configuration before you (re)start Shinken.
linux:~ # /etc/rc.d/init.d/shinken start
linux:~ # /usr/bin/shinken/shinken-scheduler -d -c /etc/shinken/daemons/schedulerd.ini
linux:~ # /usr/bin/shinken/shinken-poller -d -c /etc/shinken/daemons/pollerd.ini
linux:~ # /usr/bin/shinken/shinken-reactionner -d -c /etc/shinken/daemons/reactionnerd.ini
linux:~ # /usr/bin/shinken/shinken-broker -d -c /etc/shinken/daemons/brokerd.ini
linux:~ # /usr/bin/shinken/shinken-arbiter -d -c /etc/shinken/shinken.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 <configobjects/arbiter_pid>
linux:~ # /usr/bin/shinken-arbiter -d -c /etc/shinken/shinken.cfg
linux:~ # /etc/rc.d/init.d/shinken stop
linux:~ # kill <configobjects/arbiter_pid> <configobjects/scheduler_pid> <configobjects/poller_pid> <configobjects/reactionner_pid> <configobjects/broker_pid>