ID: 0269
Title: brocade_fcport: fixed problem on displaying check_parameters in WATO
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The checks parameters stored in the autochecks file could not get processed and
displayed correctly by the WATO inventory.
ID: 0129
Title: Fixed permission bug in "Edit user profile" dialog.
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The Edit user profile dialog has shown even the not user editable custom fields.
ID: 0685
Title: Distributed WATO now disabled WATO on slave sites per default
Component: WATO
Level: 1
Class: New Feature
Version: 1.2.5i1
When pushing a configuration to a slave site on that site WATO is
now disabled per default. This can be configured in the site
configuration with a new check box <i>Disable configuration via WATO on this site</i>,
which is check per default.
Disabling WATO on slave sites is a good idea, because any configuration
changes via WATO will be lost on the next synchronization.
ID: 0575
Title: cmciii_lcp_airin, cmciii_lcp_airout, cmciii_lcp_waterin, cmciii_lcp_waterout: improved handling of warning state
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
A unit state of warning no longer leads to a critical state of the check itself
ID: 0574
Title: if64: check now supports clustering
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
If you have a cluster of two or more hosts, and the check is configured
as a clustered service for an interface, the interface with the highest
output traffic is considered the active interface, and only this interface
is monitored and assigned to the cluster. The check denotes from which node
the interface data is taken.
ID: 0268
Title: wato inventory: fixed missing services
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.5i1
If a host had more inventorized services than they were specified in
the global option "Limit the number of rows shown in tables" specified,
the excess services got ignored.
ID: 0267
Title: Fixed auth.serials permission problem in check_mk standalone installation
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.2.5i1
In a standalone installation the path <tt>/usr/local/nagios/etc</tt> is not writable by the apache user.<br>
The user management module tried to create a file <tt>/usr/local/nagios/etc/auth_serials.new</tt> and rename it to
<tt>/usr/local/nagios/etc/auth_serials</tt> afterwards -> failed<br>
The workaround is that no <tt>auth_serials.new</tt> file will be created on standalone installations.
The user management module now directly writes in <tt>auth_serials</tt>.
ID: 0266
Title: windows_agent: now supports mrpe include files
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i1
This version introduces the mrpe configuration option <tt>include</tt>.
With this option you can define addiontal include files and the user domain in
which include files should be executed.
F+:check_mk.ini
[mrpe]
# Run classical Nagios plugins. The word before the command
# line is the service description for Nagios. Use backslashes
# in Windows-paths.
check = Dummy mrpe\check_crit
check = IP_Configuration mrpe\check_ipconfig 1.2.3.4
check = Whatever c:\myplugins\check_whatever -w 10 -c 20
# Additional mrpe configs
# The include files can be changed during the runtime
include \\ab = C:\includes\ab_mrpe.cfg
include \\NT-AUTORITÄT\SYSTEM = C:\includes\system_mrpe.cfg
# If you omit the user the file is executed with the current user
include = C:\includes\default.cfg
F-:
The syntax in the mrpe include file is the same as in the mrpe section, with the exception
that you cannot add further includes in a include file. There is also no need to define a <tt>[mrpe]</tt>
section in an included file. You just need to define the <tt>check</tt> lines here.
F+:ab_mrpe.cfg
check = Dummy mrpe\check_crit
check = IP_Configuration mrpe\check_ipconfig 1.2.3.4
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 agent has no permission to change to this user.<br>
In this case the check_mk agent will get stuck!
ID: 0684
Title: New notification variables NOTIFY_LASTSERVICEOK and NOTIFY_LASTHOSTUP
Component: Notifications
Level: 1
Class: New Feature
Version: 1.2.5i1
These two variables have been added to <tt>check_mk_templates.cfg</tt>.