From d717e6292d2432f8900bfd512f149362974d8f7d Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Fri, 22 Aug 2014 15:42:01 +0200 Subject: [PATCH] Documentation: Fix markdown formatting in troubleshooting chapter --- doc/7-troubleshooting.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/doc/7-troubleshooting.md b/doc/7-troubleshooting.md index 9e5914d1b..4a4e81f26 100644 --- a/doc/7-troubleshooting.md +++ b/doc/7-troubleshooting.md @@ -32,10 +32,11 @@ Additionally you can enable the debug log using * Check the debug log 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](#features) feature is enabled. - # sudo -u icinga /usr/lib/nagios/plugins/check_ping -4 -H 127.0.0.1 -c 5000,100% -w 3000,80% +Examples: -* Make sure the [checker](#features) feature is enabled. + # sudo -u icinga /usr/lib/nagios/plugins/check_ping -4 -H 127.0.0.1 -c 5000,100% -w 3000,80% # icinga2-enable-feature checker The feature 'checker' is already enabled. @@ -53,14 +54,14 @@ Verify the following configuration * Do the notification attributes `states`, `types`, `period` match the notification conditions? * Do the user attributes `states`, `types`, `period` match the notification conditions? * Are there any notification `begin` and `end` times configured? - * Make sure the [notification](#features) feature is enabled. +* Does the referenced NotificationCommand work when executed as Icinga user on the shell? + +Examples: # icinga2-enable-feature notification The feature 'notification' is already enabled. -* Does the referenced NotificationCommand work when executed as Icinga user on the shell? - ## Feature is not working * Make sure that the feature configuration is enabled by symlinking from `features-available/` @@ -136,7 +137,7 @@ Use tools like `netstat`, `tcpdump`, `nmap`, etc to make sure that the cluster c happens (default port is `5665`). # tcpdump -n port 5665 -i any - + # netstat -tulpen | grep icinga # nmap yourclusternode.localdomain @@ -147,10 +148,11 @@ If the cluster communication fails with cryptic SSL error messages, make sure to the following * File permissions on the SSL certificate files +* Does the used CA match for all cluster endpoints? - # ls -la /etc/icinga2/pki +Examples: -* Does the used CA match for all cluster endpoints? + # ls -la /etc/icinga2/pki ### Cluster Troubleshooting Message Errors -- 2.40.0