ID: 5796
Title: Fixed race condition in counter computation if a host uses real time checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
There was a risk that the counter data for the Check_MK checks could get lost or reset
to an earlier state, when the host received regular updates through the realtime check mechanism.
This has been fixed. As a side effect, the counter data is now only saved back to disk when there were
actual changes.
ID: 5920
Title: Windows: use standard file matching patterns for fileinfo
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
Until now, Windows agent was using a non-standard way of defining recursive
wildcards. From now on, the supported wildcard patterns '*', '?' and '**' work
in a standardized way. Recursive patterns can be defined with '**', matching
all descendants of the path so far. Previous patterns with single '*'s on
several directory levels will from now on work as non-recursive patterns
conforming to the standard.
ID: 5912
Title: mk_jolokia: Fixed exception in Bakery rule if an instance is set
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
A typo prevented the bakery ruleset to work correctly and has been introduced
in werk #5762.
ID: 5752
Title: cisco_stackpower: only inventorize enabled ports, show operational status in service output
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i4
ID: 5907
Title: CentOS/RedHat: Add explicit dependency to php-cli to fix possible broken PNP graphs
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.5.0i4
The previous Check_MK packages were not explicitly declaring the dependency
to the php-cli package which is needed to make Dokuwiki, NagVis and PNP4Nagios
work.
The dependency was only declared for php which normally implies php-cli.
Unfortunately there are third party packages that don't have this implicit
dependency.
To make Check_MK work out of the box with those PHP installations, we now added
php-cli as explicit dependency.
ID: 5742
Title: windows_tasks: show the hexadecimal representation of the status code
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i4
schtasks.exe used by the check plugin windows_tasks.ps1 returns a signed
integer value as the last result of a task. However, the status codes
(e.g. on MSDN) are usually represented as a hexadecimal value. To make
it easier to lookup a status code the hexadecimal value is now shown by
the check plugin.
ID: 5777
Title: ucs_bladecenter_fans.temp: Made item name unique
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
The check plugins {{ucs_bladecenter_fans.temp}} and
{{ucs_bladecenter_psu.chassis_temp}} created same
item names and both use the WATO ruleset {{Temperature}}.
That means that if a rule applied to a service generated
by one of these check plugins, this rule automatically
applied to the related one, too. No distinction was possible.
You have to perform a rediscovery on the affected hosts.
Performance data will be preserved.
Example:
ucs_bladecenter_fans.temp generated the services
- Temperature Ambient Chassis 1 FAN
- Temperature Ambient Chassis 2 FAN
and ucs_bladecenter_psu.chassis_temp generated the services
- Temperature Ambient Chassis 1
- Temperature Ambient Chassis 2
the item names were {{Ambient Chassis 1}} and {{Ambient Chassis 2}}
in both cases. The temperature rule matching the sensor ID
{{Ambient Chassis.*}} automatically applied to all four services.
Now the item names for
ucs_bladecenter_fans.temp look like
- {{Ambient Chassis 1 FAN}}
- {{Ambient Chassis 2 FAN}}
and for ucs_bladecenter_psu.chassis_temp
- {{Ambient Chassis 1}}
- {{Ambient Chassis 2}}
Independent rules may be created in the following order:
- {{Ambient Chassis.*FAN}}
- {{Ambient Chassis.*}}