* 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.
* 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?
-
## <a id="feature-not-working"></a> Feature is not working
* Make sure that the feature configuration is enabled by symlinking from `features-available/`
happens (default port is `5665`).
# tcpdump -n port 5665 -i any
-
+
# netstat -tulpen | grep icinga
# nmap yourclusternode.localdomain
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
### <a id="troubleshooting-cluster-message-errors"></a> Cluster Troubleshooting Message Errors