...
shinken-healthcheck
Options:
| Name | Description |
|---|---|
--version | Show program's version number and exit. |
-h, --help | Show this help message and exit. |
- |
f, -- |
file | Write output that can be send to the Shinken Solutions team. Support file is available at /root/shinken-healthcheck_date_hour |
Sample Output
| Code Block | ||
|---|---|---|
| ||
########################################################################################## This tool is used to check the state of your Shinken Enterprise (202.03.03.02U01) installation and configuration ######################################## [ .......... Note: Global check launch as launch from a arbiter server ################################################## Versions: Original installed version: 02.03.03.U01-137.fr Updated version : 02.03.03.U01-137.fr ################################################## [.......................................................................................... ] 100% Architecture OK: [/etc/shinken/synchronizers/synchronizer-master.cfg:13] connection to daemon is ] 100% Architecture ------------ |Realm All/| ------------ -------- |In All| -------- - localhost (127.0.0.1): ^^^^^^^^^^^^^^^^^^^^^^^^ [receiver: receiver-1] AT RISK: receiver-1 is defined with the localhost address. It is a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead OK: Connection to daemon is OK at port 7773 OK: Daemon version is: 02.03.03.U01-137.fr [reactionner: reactionner-master] AT RISK: reactionner-master is defined with the localhost address. It is a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead OK: Connection to daemon is OK at port 7769 OK: Daemon version is: 02.03.03.U01-137.fr [broker: broker-master] AT RISK: broker-master is defined with the localhost address. It is a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead OK: Connection to daemon is OK at port 7772 OK: Daemon version is: 02.03.03.U01-137.fr Modules OK: Name: Livestatus Type: livestatus OK: Name: Simple-log Type: simple-log OK: Name: WebUI Type: webui OK: Name: Graphite-Perfdata Type: graphite_perfdata OK: Name: sla Type: sla - 127.0.0.1 (127.0.0.1): ^^^^^^^^^^^^^^^^^^^^^^^^ [poller: poller-central] OK: Configuration seems valid OK: Connection to daemon is OK at port 7771 OK: Daemon version is: 02.03.03.U01-137.fr - localhost (192.168.56.101): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [scheduler: scheduler-central] OK: Configuration seems valid OK: Connection to daemon is OK at port 7768 OK: Daemon version is: 02.03.03.U01-137.fr Modules OK: Name: PickleRetentionFile Type: pickle_retention_file ------------------ |Realm All/Extra/| ------------------ ---------- |In Extra| ---------- - 192.168.56.102 (192.168.56.102): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [poller: poller-distant] AT RISK: Cannot get module details from your daemon (HTTP Error 404: Not Found). Please update it. OK: Configuration seems valid OK: Connection to daemon is OK at port 7771 ------------------------- |Realm All/Extra/Extra2/| ------------------------- ----------- |In Extra2| ----------- - 192.168.56.102 (192.168.56.102): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [scheduler: scheduler-distant] AT RISK: Cannot get module details from your daemon (HTTP Error 404: Not Found). Please update it. OK: Configuration seems valid OK: Connection to daemon is OK at port 7768 - localhost (127.0.0.1): ^^^^^^^^^^^^^^^^^^^^^^^^ [arbiter: synchronizer-master] AT RISK: synchronizer-master is defined with the localhost address. It is a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead OK: Connection to daemon is OK at port 7765 OK: Daemon version is: 02.03.03.U01-137.fr Modules OK: Name: Cfg_password Type: cfg_password_webui OK: Name: syncui-import Type: syncui-import OK: Name: cfg-file-shinken Type: cfg-file-import OK: Name: active-dir Type: active-dir-import 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 : OKName: sync-vmware [/etc/shinken/receivers/receiver-master.cfg:7] connection to daemon is OK Type: sync-vmware 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:Name: cfg-file-nagios [/etc/shinken/arbiters/arbiter-master.cfg:13] connection to daemon is OK Type: cfg-file-import AT RISK: [/etc/shinken/synchronizers/synchronizer-master.cfg:13] is defined with localhost address, will be a problem in distributed mode.OK: Please configure it Name: discovery-import Type: discovery-import with the LAN IP/FQDN address instead AT RISK: [/etc/shinken/schedulers/scheduler-master.cfg:14] is defined with localhost address, will be aOK: problem in distributed mode. Please configure it with the LAN Name: ip-tag-dmz Type: sync_ip_tag 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.OK: Please configure it with the LAN IP/FQDN Name: sync-regexp-tag Type: sync-regexp-tag address instead AT RISK: [/etc/shinken/receivers/receiver-master.cfg:7] is defined with localhost [arbiter: arbiter-master] address, will be a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead AT RISK: arbiter-master is defined with [/etc/shinken/reactionners/reactionner-master.cfg:9] is defined with localhost the localhost address. It is a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead address, will be a problem in distributed mode. Please configure it with the LAN OK: Connection IP/FQDNto addressdaemon instead is OK at port AT7770 RISK: [/etc/shinken/pollers/poller-master.cfg:9] is defined with localhost address, will be a problem in distributed mode. Please configure itOK: with the LAN IP/FQDN Daemon version is: 02.03.03.U01-137.fr address instead AT RISK: [/etc/shinken/arbiters/arbiter-master.cfg:13] is defined with localhost address, Modules will be a problem in distributed mode. Please configure it with the LAN IP/FQDN address instead Libs OK: Name: synchronizer-import [lib check] pymongo is is availableType: synchronizer-import Licence key OKERROR: The licence key is invalid [lib check] pycurlERROR: is is available No licence key. Trial OK:mode Node limits : 20 Local libraries [lib checkgevent] gevent is is available OK: Library gevent is available. [lib check] ldap is is availableVersion: 0.13.8 [pycurl] OK: OK: [lib check] geventLibrary ispycurl is available Licence key ERROR: . Version: libcurl/7.19.7 NSS/3.16.2.3 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 The[pymongo] licence key is invalid ERROROK: TheLibrary key formatpymongo is invalidavailable. Version: 2.9.2 ERROR: [ldap] No licence key. ERROROK: TheLibrary licence keyldap is expired Modules OK: available. Version: 2.3.10 Modules [SynchronizerWebUI] auth_secret is a custom variable OK: [Synchronizer] master_keyAuth_secret is a custom variable OK: Mongodb server is available [WebUI] auth_secret is a custom variable Storageat: mongodb://localhost/?safe=true [Synchronizer] OK: OK: [Synchronizer] mongodbMongodb server is available at: mongodb://localhost/?safe=false OK: Auth_secret is [graphite] server localhost:2003 is available a custom variable OK: The master_key is [webui::mongodb module /etc/shinken/modules/mongodb.cfg:5] mongodb server isa custom variable Storage [graphite] OK: Graphite server available: mongodb://localhost/?safe=true OK:127.0.0.1 is available with 1 top level elements [webui::graphite] server 127.0.0.1 is available with 10 top level elementsOK: Graphite server localhost:2003 is available |
Output parts
The healthcheck output is separated into several parts:
...
shinken-local-healthcheck
Options:
| Name | Description |
|---|---|
--version | Show program's version number and exit. |
-h, --help | Show this help message and exit. |
- |
f, -- |
file | Write output that can be send to the Shinken Solutions team. Support file is available at /root/shinken-healthcheck_date_hour |
Output parts
The healthcheck output is separated into several parts:
...
shinken-global-healthcheck
Options:
| Name | Description |
|---|---|
--version | Show program's version number and exit. |
-h, --help | Show this help message and exit. |
- |
f, -- |
file | Write output that can be send to the Shinken Solutions team. Support file is available at /root/shinken-healthcheck_date_hour |
Output parts
The healthcheck output is separated into several parts:
...