...
You will find in this directory, a log file for each Shinken Enterprise daemon :
- /var/log/shinken/arbiterd.log
- /var/log/shinken/brokerd.log
- /var/log/shinken/pollerd.log
- /var/log/shinken/reactionnerd.log
- /var/log/shinken/receiverd.log
- /var/log/shinken/schedulerd.log
- /var/log/shinken/synchronizerd.log
and an other more global aggregated one:
!
- /var/log/shinken/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 :
!
You can setup the level inside your configuration file (shinken.cfg)
- DEBUG ( ? )
- INFO
- WARNING ( = Info + Warning events )
- CRITICAL ( = Info + Warning + Critical events )
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
service shinken -d [debug level] restart |
or (only one deamon)
| Code Block | ||||
|---|---|---|---|---|
| ||||
service shinken-[daemon name] -d [debug level] restart |
...
In this one, you will find all events about data management, because the broker daemon is used to export and manage data ( from schedulers ), for example, making those logs files ( and rotation ).
!! pas de screen exploitable !!
In this log you will find log output abou connection errors with the others daemons when occurs:
- schedulers
- pollers
- reactionners
- receivers
pollerd.log
In this one, you will find all events about checks plugins, because the poller daemon is used to launch checks and return results to the schedulers.
!! pas de screen exploitable !!
You will mainly find issues with the scheduler communication if occurs.
reactionnerd.log
In this one, you will find all events about communication ( mail, RSS, ... ) , because the reactionner daemon is used to issue notifications and launch event_handlers.
!! pas de screen exploitable !!
You will mainly find issues with the scheduler communication if occurs.
receiverd.log
In this one, you will find all events about passive checks, because the receiver daemon is used to receives passive check data and serves as a distributed passive command buffer that will be read by the arbiter daemon.
!! pas de screen exploitable !!
You will mainly find issues with the scheduler communication if occurs and if the receiver is in direct routing mode.
schedulerd.log
In this one, you will find all events about checks (dispatch, returns, ...), because the scheduler daemon is used to manage the dispatching of checks and actions to the poller and reactionner daemons respectively.
You will see all checks returns :
manque des screens pour ce qui concerne les erreurs de communications, actions non retournées...
synchronizerd.log
In this one, you will find all events about configuration, because the scheduler synchronizer daemon is used to manage the whole configuration. It uses modules to detect new hosts and host modifications.
!! pas de screen exploitable !!