ID: 3648
Title: Fixed log file parsing of host states
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.4.0i2
When parsing log/history files, the host state 'DOWN' was incorrectly
handled. This has been fixed.
ID: 3739
Title: Fix exception in displaying check parameter of grouped interfaces
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.4.0i1
In the list of services WATO would show an exception about an invalid
key <tt>aggr_item_member</tt>. This has been fixed and the parameter
is now correctly being displayed.
ID: 3816
Title: WATO-Web API: fixed bug in API request validation
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i1
Recent code changes did not consider that only the keys of the request
object itself got validated. The validiation function now got feeded with
some additional keys, e.g effective_attributes, didn't accept these keys
and returned an "Invalid request" as result.
This has been fixed.
ID: 3905
Title: barracuda_mailqueues, nullmailer_mailq, postfix_mailq, qmail_stats: these checks now have items, postfix can now monitor multi directories
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i1
Note: existing ruleset mailqueue length is now deprecated. These checks will
work further on but the related ruleset won't be applied any more except default levels.
Please use new service descriptions for these checks below global settings, rediscover the
affected hosts and use new mail queue length ruleset.
ID: 3738
Title: Fixed sporadic pending changes due to (not) changed contact groups
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.4.0i1
The LDAP connector sometimes creates pending changes because of changed
contact groups. But the groups have not really changed. Just the order
of the groups in the answer from the LDAP server has changed. This
has been fixed.
ID: 3893
Title: Predictive levels: Improved handling of broken prediction files (empty files)
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.4.0i1
In previous versions it could happen that the predictive levels feature created empty
(zero byte sized) files below var/check_mk/prediction which made the predictive levels
not work anymore for the affected service. This situation is now being repaired
automatically.