ID: 3969
Title: CentOS 5.5: Fixed incompatibility with the available OpenSSL 0.98
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.4.0i2
When opening the GUI, the following error occured, making the GUI unusable:
RuntimeError: You are linking against OpenSSL 0.9.8, which is no longer support by the OpenSSL project. You need to upgrade to a newer version of OpenSSL.
This has been fixed now.
ID: 3829
Title: Skype for Business checks: refactored most of the checks
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i2
Note: Due to a bug in the windows agent these check weren't discovered, anyway.
ID: 3968
Title: Notifications / Alert handling: Fixed configuring nth notifications without state changes
Component: Notifications
Level: 1
Class: Bug Fix
Version: 1.4.0i2
This is especially important for the Enterprise Edition specific alert handling when constructing
rules matching on the nth check attempt. But it has been added as generic option for notifications
and alert handling.
ID: 3966
Title: apc_symmetra raritan_emx: Fixed wrong include "temperature.includes"
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.4.0i2
The checks were including non existant check include files which lead to an
error:
IOError: [Errno 2] No such file or directory: '/omd/sites/test/share/check_mk/checks/temperature.includes'
When using nagios core, this made the whole compilation of the configuration
fail in case the checks are used.
ID: 3965
Title: Nagios: Improved handling of broken core config
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.4.0i2
In case of configuration validation issues, the broken config, which
will be replaced by the former config on validation issues, is copied
to /omd/sites/[site]/tmp/check_mk/check_mk_objects.cfg.broken for
diagnose actions.
ID: 3650
Title: Fixed bash versionitis, unbreaking cached check results.
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i2
Our shebang lines in scripts explicitly state which bash they want, and the
bash instances we start from the script should better use the exact same
version. If there is a version mismatch, lots of funny things can happen,
the most prominent being that caching check results doesn't work anymore
(e.g. when using MRPE). This is caused by the bash fixes for the
Shellshock vulnerability which change (among other things) how functions are
exported to sub-shells. The consequence is that a pre-Shellshock bash
doesn't see the functions exported by a post-Shellshock bash, and vice
versa. This setup can happen when the shebang and the user's PATH have
different ideas about which bash to use.
To fix this, we use the same absolute path for starting the bash
sub-processes as the one stated in the corresponding shebang.