ID: 0813
Title: LDAP: Improved slightly missleading logging of LDAP sync actions
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i4
In some situations a call to WATO issued by the user are causing LDAP syncs,
for example when a user starts the sync interactively or the cache lifetime
has exceeded. In the past, the name of the triggering user was logged
to the audit / pending log, which was a bit missleading. Now, the name
of the user is not logged anymore.
ID: 0812
Title: nginx_status: New check for monitoring status information of the Nginx web server
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3
Implemented a new check which uses the Nginx stub status module to monitoring inner
information of the Nginx process about number of active connections, connections per
second, requests per second and so on.
ID: 0934
Title: Logwatch messages with class unknown ( 'u' ) now displayed as WARN
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.5i3
Certain windows messages don't have a correct error level classification
and there get reported as the error type 'u' (unknown).<br>
Unknown types were not shown correctly in the multisite logfile viewer.
ID: 0961
Title: fast_lta_volumes: new check of capacity of volumes in FAST LTA Storage Systems
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i3
Thanks to Christian Dewald / Agfa HealthCare for the donation.
ID: 0933
Title: WATO snapshots: excluded some superfluous files from nagvis backup domaim
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i3
The nagvis backup domain contained some files with hardcoded site names.
This caused problems if this snaphot was restored on a different site.
ID: 0930
Title: WATO snapshots: disabled upload of legacy snaphots and snapshots with invalid checksums
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i3
The upload of insecure snapshots has been disabled per default, because those
snapshots represent a security risk if their content were modified willingly or unwillingly.
Insecure snapshots are all legacy snapshots and snapshots of the newer type, but with an invalid checksum.
You can re-enable the upload of insecure snapshots via the new global setting<br>
<tt>Configuration GUI (WATO) -> Allow upload of insecure WATO snapshots</tt>
ID: 0929
Title: windows agent: now able to include and execute additional local and plugin scripts as different user
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3
In the <tt>[local]</tt> and <tt>[plugin]</tt> sections the new option <tt>include</tt> has been introduced.
With this option you can configure additional local and plugin directories, which should get parsed.
You can also configure the the scripts in the given directories should be executed as a different user.
<br><br>
Example configuration:<br>
F+:check_mk.ini
[plugin]
# The scripts in the following folder are executed as user \\ab
include \\ab = C:\users\ab\plugins
# The scripts in the following folder are executed without any changes to the user permission
include - = C:\scripts\plugin
F-:
<b>Important:</b> Keep in mind that the agent needs the permission to run
scripts as other user. Internally it uses the windows command <tt>runas /User:</tt>
which prompts for a password if the windows agent has no permission to change to this user.
ID: 0928
Title: runas: new plugin script to include and execute mrpe, local and plugin scripts as different user
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3
With the new plugin <tt>runas</tt> you can configure additional include files and
directories for mrpe, local and plugin scripts. You can also change the user context
of each of these scripts. It allows non-root users to add additional scripts which might
get executed with reduced permission.
This check is configured with the configuration file <tt>runas.cfg</tt>.
In a default installation this file is located within the Check_MK config directory under <tt>/etc/check_mk/runas.cfg</tt>.
The <tt>runas.cfg</tt> configuration syntax is as follow
[Script type] [User context] [File / Directory ]
The <tt>Script type</tt> can be set to <tt>mrpe</tt>, <tt>local</tt> and <tt>plugin</tt>.
The <tt>User context</tt> represents the user. If you do not want to change the context set this field to <tt>-</tt>
Depending on the script type the third value points to a file or directory.
The mrpe type requires a target file which contains the mrpe commands.
Local and plugins types require are target folder, which contains the executable local and plugin scripts.<br>
Here is an example configuration:
F+:/etc/check_mk/runas.cfg
mrpe ab /home/ab/mrpe_commands.cfg
mrpe lm /home/lm/mrpe_commands.cfg
mrpe - /root/mrpe/extra_commands.cfg
plugin ab /var/ab/plugins
local ab /var/ab/local
F-:
<b>Note:</b>You need to set up the local and plugin scripts in different folders, because the line
<tt>plugin ab /var/ab/plugins</tt> indicates that all executable files within this folder are treated as plugins.