...
Note: from command line interface, each command provides '--help' option that will print the usage of respective command.
Tools
...
Health Check
shinken-healthcheck
This tool is used to check the state of your Shinken Enterprise installation
and installation and configuration.
Usage:
shinken-healthcheck
Options:
| Name | Description |
|---|---|
--version | Show program's version number and exit. |
-h, --help | Show this help message and exit. |
-w, --write-output | Write output that can be send to the Shinken Solutions. |
Sample Output
| Code Block | ||
|---|---|---|
| ||
########################################
This tool is used to check the state of your Shinken Enterprise (2.03.02) installation and configuration
########################################
[ .................................................................................................... ] 100%
Architecture
OK: [/etc/shinken/synchronizers/synchronizer-master.cfg:13] connection to daemon is
OK
OK: [/etc/shinken/schedulers/scheduler-master.cfg:14] connection to daemon is OK
OK: [/etc/shinken/brokers/broker-master.cfg:15] connection to daemon is OK
OK: [/etc/shinken/receivers/receiver-master.cfg:7] connection to daemon is OK
OK: [/etc/shinken/reactionners/reactionner-master.cfg:9] connection to daemon is OK
OK: [/etc/shinken/pollers/poller-master.cfg:9] connection to daemon is OK
OK: [/etc/shinken/arbiters/arbiter-master.cfg:13] connection to daemon is OK
AT RISK: [/etc/shinken/synchronizers/synchronizer-master.cfg:13] is defined with
localhost address, will be a problem in distributed mode. Please configure it
with the LAN IP/FQDN address instead
AT RISK: [/etc/shinken/schedulers/scheduler-master.cfg:14] is defined with localhost
address, will be a problem in distributed mode. Please configure it with the LAN
IP/FQDN address instead
AT RISK: [/etc/shinken/brokers/broker-master.cfg:15] is defined with localhost address,
will be a problem in distributed mode. Please configure it with the LAN IP/FQDN
address instead
AT RISK: [/etc/shinken/receivers/receiver-master.cfg:7] is defined with localhost
address, will be a problem in distributed mode. Please configure it with the LAN
IP/FQDN address instead
AT RISK: [/etc/shinken/reactionners/reactionner-master.cfg:9] is defined with localhost
address, will be a problem in distributed mode. Please configure it with the LAN
IP/FQDN address instead
AT RISK: [/etc/shinken/pollers/poller-master.cfg:9] is defined with localhost address,
will be a problem in distributed mode. Please configure it with the LAN IP/FQDN
address instead
AT RISK: [/etc/shinken/arbiters/arbiter-master.cfg:13] is defined with localhost address,
will be a problem in distributed mode. Please configure it with the LAN IP/FQDN
address instead
Libs
OK: [lib check] pymongo is is available
OK: [lib check] pycurl is is available
OK: [lib check] gevent is is available
OK: [lib check] ldap is is available
OK: [lib check] gevent is is available
Licence key
ERROR: The licence key is invalid
ERROR: The key format is invalid.
ERROR: No licence key.
ERROR: The licence key is expired
Modules
OK: [Synchronizer] auth_secret is a custom variable
OK: [Synchronizer] master_key is a custom variable
OK: [WebUI] auth_secret is a custom variable
Storage
OK: [Synchronizer] mongodb server is available: mongodb://localhost/?safe=false
OK: [graphite] server localhost:2003 is available
OK: [webui::mongodb module /etc/shinken/modules/mongodb.cfg:5] mongodb server is
available: mongodb://localhost/?safe=true
OK: [webui::graphite] server 127.0.0.1 is available with 10 top level elements
|
Output parts
The healthcheck output is separated into several parts:
- Architecture: about your daemons configuration
- Libs: about installed librairies need by Shinken Enterprise
- Licence key: all about your licence key
- Modules: information about UIs
- Storage: information about the mongodb and graphite storage system
There are 3 level for output:
- OK: all is valid
- At Risk: it works, but something can go wrong in the future if you don't fix something
- Error: this part is in error and must be fix now
Common issues and Error:
Outdated or invalid licence key
If you are using a invalid or an outdated licence key, you will have ERRORS on the Licence key part. You will also have a At Risk level near the end of the key validity date. [
Backup and restore
shinken-restore
Usage:
shinken-restore DIRECTORY-TO-RESTORE
...