ID: 5238
Title: WATO users now only see their configured sites in the Site-DropdownChoice
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
A user can be configured only to see/configure a subset of the available sites.
The site dropdown choice, however, always showed all available sites. This has been fixed.
ID: 5409
Title: Windows eventlog: wrong last state saved
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
The initial run of Windows agent after fresh installation caused an
incorrect last state to be written in the state file eventstate.txt.
As a result, no new entries were read from the eventlog. Broken since
commit 91797ac9f7d69fc94119c08ea0df4baccaea2b6.
ID: 5429
Title: Fixed broken event history expiration (when using default settings)
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.5.0i1
The Event Console was not deleting outdated entries from the event history.
With the default settings it is intended to delete entries older than 365
days from the EC archive. This did not work.
A message like this can be found each "Housekeeping interval", normaly 1 minute:
[1509618281.352829] Error expiring log files: year out of range
This time window can be configured with the setting "Event history lifetime".
As a workaround you can simply open this setting and save it with the default
value. This will make the event deletion work as expected.
When you are affected, this may result in a way too huge Event Console archive
directory (<tt>~/var/mkeventd/history</tt>) which may result in slow
"Event Console History" views (depends on your filtering). You could clean up
the archive directory by hand to improve the situation.
After applying the update, the next housekeeping run will clean up all your old
archived events.
ID: 5441
Title: mk_oracle: Werk 5321 introduced usage of nawk for SunOS but was implemented incorrectly for Linux
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
ID: 5261
Title: Improve agent bakery robustness when baking new agents
Component: agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Depending on the complexity of the underlying configuration ruleset, some agents accidently could be marked as to be rebaked although there is no config change for them.
This is now mitigated by applying a more robust hashing algorithm for the agent config hashes.
After updating, no further action is required to apply the fix. Notably, no re-bake of existing agents is required.
ID: 5427
Title: Fixed different XSS issues triggerd from BI aggregation/rule titles/descriptions
Component: BI
Level: 1
Class: Security fix
Version: 1.5.0i1
Different fields in the BI configuration (titles, ...) could be used to inject JS code
into the WATO dialogs and the BI status views. This could be triggered by users with
permission to administrate WATO.
ID: 5351
Title: check_http: Use HTTPS instead of HTTP in service description for SSL/TLS connections
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
For Check HTTP checks the service description now uses HTTPS instead of
HTTP if a connection via SSL/TLS is used. This makes it easy to distinguish
if a Check uses HTTP or HTTPS for a connection.
This feature is automatically enabled for new Check_MK installations.
If you upgrade an existing Check_MK installation you have to enable it
in the global settings via the option "Use new service descriptions"
in the section "Execution of checks". Be aware that the change may effect
existing rules, performance data (if present), and the availability
history.
ID: 5425
Title: Fixed broken bookmark list management for users with non ascii characters in User IDs
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i1