ID: 0389
Title: Showing LDAP settings on site specific global settings page now
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The site specific global settings page should show all configuration
options. Independent of the fact that they are related to LDAP or
the event console. This has been fixed now.
ID: 0388
Title: Moved Event Console related settings to own settings page
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.5i1
The event console global settings configuration has been moved to
its own configuration page to clearify which settings need a reload
of the event console daemon and which ones need a restart of the
monitoring core.
ID: 0351
Title: local: Catch invalid state codes and map to 3 (UNKNOWN)
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
If the the state of a line of the <tt>local</tt> section is
not in the allowed range (from <tt>0</tt> to <tt>3</tt>) then
we now assume <tt>3</tt>. Up to now Check_MK ran into an exception.
ID: 0387
Title: df*: Negative filesystem space levels get a more clear text in check output
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
Instead of just displaying negative values, the text "levels at free space below XX.XX/YY.YY)
is displayed in plugin output.
ID: 0386
Title: Added all active checks to check_mk -L output
Component: Core & Setup
Level: 1
Class: New Feature
Version: 1.2.5i1
check_mk -L did list all tcp and snmp based check, but the
active checks were missing. They have been added now.
ID: 0385
Title: Better error handling for invalid service regex in rule conditions
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.5i1
Previous versions of the rule editor in WATO did not check whether or not
the regular expressions provided for matching services are valid. This
change adds a regular expression validation.
ID: 0384
Title: Trying to prevent problem when restarting mkeventd
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.5i1
In some situation, when restarting the mkeventd, the old process has
been stopped, but when the new process comes up, the builtin syslog
server can not open the port, because it is somehow still opened.
The error message is:
Cannot bind TCP socket for syslog-tcp to port: Address already in use
This change tries to prevent the problem.
ID: 0350
Title: nfsmounts: correctly handle mount points with spaces
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
If you have a space in the name of your <b>moint point</b> (not in the name
of the export) then the Linux agent would show this mount point always as
<tt>hanging</tt>. The reason is that in <tt>/proc/mounts</tt> spaces are
displayed as <tt>\040</tt>. This has now been fixed in the agent, which
outputs spaces correctly. Also the according check has been modified so that
it can deal with spaces in the names of the mount points.