/var /log /shinken

You will find in this directory, a log file for each Shinken daemon : 

• arbiterd.log
• brokerd.log
• pollerd.log
• reactionnerd.log
• receiverd.log
• schedulerd.log
• synchronizerd.log

and an other more global : 

!

• shinken.log

Note : there is a daily rotation of log files (for X days by default but you can edit this in configuration ?).

Those files are also in this directory and they are suffixed with a date like this : arbiterd.log.2015-09-02

Four levels of debugging are available : 

!

• DEBUG  ( ? ) 
• INFO
• WARNING ( = Info + Warning events ) 
• CRITICAL ( = Info + Warning + Critical events ) 
  
  

To launch Shinken in debug mode : 

• service shinken -d [debug level] restart
  or (only one)

• service shinken-[daemon name] -d [debug level] restart

arbiterd.log

In this one, you will find all events about your Shinken Architecture, because the arbiter daemon is used to check and dispatch configuration to the others daemons ( but not the Synchronizer ).

In error case : 

Very useful in complex architecture with spare daemons where you will see here rocker events.

brokerd.log

pollerd.log

reactionnerd.log

receiverd.log

schedulerd.log

synchronizerd.log