General Shinken Enterprise troubleshooting steps to resolve common issue

• Are all daemons running?

• Have you reviewed your Shinken Enterprise daemon specific logs for errors or tracebacks

• Are you using the same Shinken Enterprise version on all your hosts running a Shinken Enterprise daemon

• Have you enabled debugging logs on your daemons

• Have you executed/tested your plugin command as the Shinken Enterprise user

• Have you defined a module on the wrong daemon (ex. NSCA receiver module on a Broker)

• System logs /var/log/messages

• Use top to look for memory, cpu and process issues.

Use the health check command

A fast way to check at your Shinken Enterprise environnement is to use the shinken-healtcheck command.

FAQ Answers

Review the daemon logs

A daemon is a Shinken Enterprise process. Each daemon generates a log file by default.
The configuration of a daemon is set in the .ini configuration file (ex. brokerd.ini).
Logging is enabled and set to level INFO by default.

Default log file location ''local_log=%(workdir)s/schedulerd.log''

The log file will contain information on the Shinken Enterprise process and any problems the daemon encounters.

Changing the log level in the configuration

Edit the <daemon-name>.ini file, where daemon name is pollerd, schedulerd, arbiterd, reactionnerd, receiverd.
Set the log level to: DEBUG
Possible values:

• DEBUG
• INFO
• WARNING
• ERROR
• CRITICAL

Re-start the Shinken Enterprise process.

Changing default linstening port for all daemons

First you have to change listening port for running daemon.

In the /etc/shinken/daemons/ directory, edit your daemon .ini file. Then find the "port=" directive and change listening port.

At this step, if you restart shinken service your daemon will be listening on new port but the arbiter is not configured to query on the right port tou have toi change the daemon ressource on the arbiter server.

In /etc/shinken/, change directory to daemons configuration directory (ie. /etc/shinken/pollers), edit ressource daemon cfg file and change target port.

Restart Shinken arbiter service

For synchronizer daemon, you must change :

/etc/shinken/synchronizers/synchronizer-master.cfg

and 

et il doit ensuite être changé dans le module d'import de l'arbiter vers le synchronizer:/etc/shinken/modules/synchronizer-import.cfg.