![]() This host is marked as DOWN by CheckMK, but still is able to get the services status.QTS is the operating system for entry- and mid-level QNAP NAS. I’m using Kubernetes Special Agent to monitor the resources in a Kubernetes Cluster (host), but when I execute the connection tests on this host, only the tests “Agent” and “Traceroute” work, the remaining tests don’t work. We shouldn't notify about this recovery. The host is either down or unreachable, so we won't notify contacts about this service. We shouldn't re-notify contacts about this host problem. On etc/nagios/nagios.d/logging.cfg I enabled log_passive_checks and updated debug_verbosity to 2 (Very Detailed) and finally I could get some useful logging: ** Host Notification Attempt ** Host: '.com', Type: 0, Options: 0, Current State: 1, Last Notification: Fri Dec 10 13:31:49 2021 I’m not sure if it is something that I’m missing or if it is a bug. Ideally it should be possible to see which conditions are not allowing the notifications to be sent, otherwise troubleshooting is very hard. Can this be a bug in the monitoring core itself? ** Host Notification Attempt ** Host: '.com', Type: 0, Options: 0, Current State: 1, Last Notification: Fri Dec 10 13:31:49 2021Īccording to the documentation the problem is identified on the monitoring core since the file var/nagios/debug.log is related to this component. ** Service Notification Attempt ** Host: '.com', Service: 'CPU resources', Type: 0, Options: 0, Current State: 0, Last Notification: Thu Jan 1 00:00:00 1970 ** Service Notification Attempt ** Host: '.com', Service: 'CPU resources', Type: 0, Options: 0, Current State: 2, Last Notification: Thu Jan 1 00:00:00 1970 I updated the nagios debug_level to 32 as mentioned at Notifications - via Email, SMS, Ticketsystems and more (), tested again and got the following logs on var/nagios/debug.log: ** Host Notification Attempt ** Host: '.com', Type: 0, Options: 0, Current State: 1, Last Notification: Fri Dec 10 13:31:49 2021 I did setup Mattermost notification configuration, but for some reason the only notifications that are working are the custom notifications (done manually) or flappingstart/flappingstop, but I would like to see notification when the state of a service change to CRITICAL. Released lock on /omd/sites/cmk/tmp/check_mk/counters/localhostĮxecution time 0.0 sec | execution_time=0.000 user_time=0.000 system_time=0.000 children_user_time=0.000 children_system_time=0.000 cmk_time_agent=0.000 Releasing lock on /omd/sites/cmk/tmp/check_mk/counters/localhost Got lock on /omd/sites/cmk/tmp/check_mk/counters/localhost Trying to acquire lock on /omd/sites/cmk/tmp/check_mk/counters/localhost Fetch with cache settings: NoCache(base_path=PosixPath('/omd/sites/cmk/tmp/check_mk/data_source_cache/piggyback/localhost'), max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False) Source: SourceType.HOST/FetcherType.PIGGYBACK Released lock on /omd/sites/cmk/var/check_mk/ipaddresses.cache Releasing lock on /omd/sites/cmk/var/check_mk/ipaddresses.cache Got lock on /omd/sites/cmk/var/check_mk/ipaddresses.cache Trying to acquire lock on /omd/sites/cmk/var/check_mk/ipaddresses.cache ![]() Updating IPv4 DNS cache for localhost: 127.0.0.1 Released lock on /omd/sites/cmk/var/check_mk/license_usage/next_run Releasing lock on /omd/sites/cmk/var/check_mk/license_usage/next_run ![]() Released lock on /omd/sites/cmk/var/check_mk/license_usage/history.json ![]() Releasing lock on /omd/sites/cmk/var/check_mk/license_usage/history.json Got lock on /omd/sites/cmk/var/check_mk/license_usage/history.json Trying to acquire lock on /omd/sites/cmk/var/check_mk/license_usage/history.json Got lock on /omd/sites/cmk/var/check_mk/license_usage/next_run Trying to acquire lock on /omd/sites/cmk/var/check_mk/license_usage/next_run Output of “cmk -debug -vvn hostname”: Checkmk version 2.0.0p16 Running on docker image checkmk/check-mk-raw 2.0.0-latest.Įrror message: Don’t get any error message ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |