ID: 6153
Title: Fixed broken notifications and alert handling (Regression in 1.5.0b5)
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.6.0i1
The notifications and alert handling were not working correctly at all. Better
use the 1.5.0b5 only in test environments where you don't need these features.
ID: 6155
Title: Service discovery page: Active checks were not correctly shown in specific cases
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
It could happen that some active checks were not correctly shown in the tables
"active checks" or "disabled active checks". This was caused by specific
disabled services rules. For example when using this two rules:
1. Enable all services starting with "HTTP"
2. Disable all services
In this situation the HTTP service was not displayed on the discovery page.
ID: 6152
Title: Notification conditions can now be displayed in notification rule table
Component: WATO
Level: 1
Class: New feature
Version: 1.6.0i1
The last column can now expand the number of conditions to the list of match conditions of the rule.
ID: 6151
Title: Net-SNMP: Add some patch trying to fix SNMPv3 communication in some cases
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.6.0i1
When using SNMPv3 communication issues with some devices may occur. From the user point of
view timeouts are reported by Check_MK originating from Net-SNMP not receiving a valid response.
This kind of issue is related to a broken negotiation (related to the maximum message size) between
the monitoring and the monitored device.
ID: 6149
Title: ps: The linux ps check CPU utilization calculation changed since 1.4.0p27
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The calculation of the CPU utilization of processes on linux systems was not taking the number
of CPU cores into account for a long time. This results in CPU utilizations reported with more
than 100%, up to 100%*CPU-cores. For example in case 3 processes use 3 of 6 cores at 100%, this
resulted in a usage of 300%.
The intention of the change in 1.4.0p27 was to make the windows and linux ps checks both take
the number of CPU cores into account and cap the usage at 100%. The problem with this change is
that all possibly existing thresholds that have been configured for the old scheme will not
work anymore with the new scheme.
We have now reverted the changes version 1.4.0p27 introduced to get the old behavior back.
In a future release, we will finally make the switch to the new scheme. But this will be done
in a compatible way where the already configured thresholds will still work.
ID: 6081
Title: Fixed info extension by node name of cluster-aware checks if host if not part of a cluster
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
ID: 6108
Title: Raw Edition: Don't show enterprise specific graph export links in context menu
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
ID: 6106
Title: Raw Edition: Fixed checking of some hosts when check speicific config variables are used
Component: Core & setup
Level: 2
Class: Bug fix
Version: 1.6.0i1
When check specific configuration variables are set in the Check_MK configuration,
they could make the Check_MK checks of hosts that are not using these checks fail.
This resulted in Check_MK services showing an empty output. When executing the
precompiled host checks on the command line in debug mode, errors are shown. Like
this:
python /omd/sites/beta/var/check_mk/precompiled/[hostname] -v
Cannot read in configuration file /omd/sites/[site]/etc/check_mk/conf.d/wato/rules.mk: name 'fileinfo_groups' is not defined