ID: 6893
Title: diskstat: Make check compatible with addional kernel versions
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previuously the diskstat check could potentially not work due to kernel dependencies.
The werk add ensures proper working for additional kernel versions.
ID: 6902
Title: apache_status: Ignore certificate for localhost
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If a https server at 127.0.0.1 or [::1] is checked, ignore the certificate in
case the name does not match.
Previously we tried to contact the server via http on port 80 instead,
but the server may not be listening on that port.
You need to change the protocol to http if you are monitoring a https
server that also listenes on port 80 and the servers address is not
either the address the certificate was issued for or one of
127.0.0.1, [::1] and "localhost".
ID: 6649
Title: PagerDuty: Notification plugin
Component: Notifications
Level: 1
Class: New feature
Version: 1.6.0i1
Check_MK now support native integration with Pager Duty and can send
notifications about state changes of hosts and services into a configured
Pager Duty service.
In Pager Duty a new integration service has to be set up. Select as
"Integration Type" Check_MK and configure your service as better suited for
your use case. Save the returned "Integration Key".
In Check_MK, under "WATO - Notifications", create an new notification rule
and select PagerDuty. Copy the "Integration Key" from Pager Duty as
parameter. Optionally you can save the integration key in Check_MK's
password manager and retrieve it here. If you want incidents in Pager Duty
to include hyperlinks back to Check_MK, enable the field URL prefix for
links to Check_MK.
ID: 6680
Title: The "Parameters for this service" page now correctly displays the computed results for timespecific parameters
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
This fixes a display error for the mentioned page, the computation itself was always correct.
ID: 6635
Title: printer_alerts: Fix handling for Sleep state
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Some printers report states not defined in the MIB. A
reasonably common case appears to be the printer going
to sleep, which should be treated as OK instead
of UNKNOWN.
ID: 6860
Title: Fixed random backup issues: "Connection reset by peer"
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.6.0i1
The "mkbackup" and "omd backup" commands could fail while backing up a site when
the rrdcached process was reloaded, restarted or stopped during the backup. This
could also be triggered by an "Activate changes" action in the GUI.
The backup was then aborted with an error like this: "Failed to perform backup: [Errno 104] Connection reset by peer".
This issue did not affect backups performed for not running sites.
ID: 6857
Title: Fixed broken links in about snapin
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
Fixed broken links in about snapin and removed version information which is
already shown in the header. The links are now opened in a new window/tab
instead of the right frame.
ID: 6856
Title: Host permission fields are now resizable with modern theme
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
When using the modern theme it was not possible to resize the permission
contact group list fields which is useful when having long group names.
ID: 6417
Title: Users may disable notifications by accident after upgrading to 1.5.0
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.6.0i1
Due to a rendering issue in the personal settings the option "Temporarily disable
all notifications" is always set in the GUI when a user or admin edits the settings
for the first time after an update to version 1.5.0.
If the user or admin then saves the settings and does not enable the notifications,
the setting is saved and the user does not receive notifications anymore. If a
user profile was not modified after an update, notifications worked as expected.
If a profile is saved for the first time after an update, the old configuration
file format is transformed to the new format. After that the setting is rendered
correctly.
To circumvent any problems please make sure that the notification settings of all
users are set properly after the update and that the settings are saved at least
once with the correct value.
For a large amount of users it may be tedious to change the settings off all users.
In this case it may be more straight forward to edit the file
~/etc/check_mk/conf.d/wato/contacts.mk directly. In the file all values for the key
"disable_notifications" have to be modified. The old value "True" has to be replaced
by the dictionary "{'disable': True}" and the old value "False" has to be replaced
by the empty dictionary "{}".
The issue is fixed in version 1.5.0p8. If you update from 1.4.0 to a version
>= 1.5.0p8 you are not affected by this issue.
ID: 6859
Title: Fixed problem creating custom graphs with many metrics
Component: metrics
Level: 1
Class: Bug fix
Version: 1.6.0i1
Since 1.5 creating custom graphs out of graphs with many metrics,
e.g. combined graphs, could fail. The custom graph was not created
when clicking on "New custom graph..." and nothing visible happened.
CMK-1219