tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Troubleshooting: Explain how to fetch the executed command 

fixes #10964
This commit is contained in:
Michael Friedrich 2016-01-13 16:48:43 +01:00
parent 7f4af89a56
commit c49fed204a
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/16-troubleshooting.md
View File

@ -113,9 +113,19 @@ on upgrade, so please send modifications as proposed patches upstream. The defau
You should add your own command definitions to a new file in `conf.d/` called `commands.conf`
or similar.
## <a id="checks-not-executed"></a> Checks are not executed
## <a id="troubleshooting-checks"></a> Checks
* Check the debug log to see if the check command gets executed
### <a id="checks-executed-command"></a> Executed Command for Checks
* Use the Icinga 2 API to [query](9-icinga2-api.md#icinga2-api-config-objects-query) host/service objects
for their check result containing the executed shell command.
* Use the Icinga 2 [console cli command](8-cli-commands.md#cli-command-console)
to fetch the checkable object, its check result and the executed shell command.
* Alternatively enable the [debug log](16-troubleshooting.md#troubleshooting-enable-debug-output) and look for the executed command.
### <a id="checks-not-executed"></a> Checks are not executed
* Check the [debug log](16-troubleshooting.md#troubleshooting-enable-debug-output) to see if the check command gets executed
* Verify that failed depedencies do not prevent command execution
* Make sure that the plugin is executable by the Icinga 2 user (run a manual test)
* Make sure the [checker](8-cli-commands.md#enable-features) feature is enabled.