ID: 0345
Title: Linux agent: fix detaching of background plugins
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i1
The asynchronous execution of background processes in the Linux agent has
been fixed. Before it could have happened that the agent starts background
processes but - however - waits for all of them to finish until finishing
itself. This has now been fixed. All plugins started with run_cached are
now correctly detached from the agent.
ID: 0367
Title: Now using /dev/null instead of closing stdin in linux agent
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i1
Some programs might not be working when stdin is closed. A more portable
approach seems to use /dev/null as stdin.
ID: 0316
Title: hitachi_hnas_cpu: New check for CPU utilization of Hitachi HNAS devices
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
ID: 0244
Title: New features for WATO page Backup & Restore
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i1
The WATO "Backup & Restore" feature now allows the user to select what kind of data
is included in the snapshot. In previous versions only the Check_MK configuration
and the local authentication data where included. In the new version logs, performance data and various
other historic data can also be included.
It is also possible to set an optional comment in the created snapshot.
For further information please refer to the official documentation.
ID: 0339
Title: blade_bays blade_blades blade_blowers blade_health blade_mediatray blade_powerfan blade_powermod: fix scan function
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i1
Due to a previous precision in the scan function API the scan functions of
the blade_* checks where never successful anymore. That way those checks
were not detected on new devices. This has been fixed. Existing checks
were not affected.
ID: 0338
Title: Introduce time limit on availability queries
Component: Reporting & Availability
Level: 2
Class: Bug Fix
Version: 1.2.5i1
The availability view now imposes an upper limit on the execution of the
underlying livestatus query. The default is 30 seconds. This can be configured
in the reporting options. This limit keeps the system usable in situations
where a query over a long time range would need a very long time to execute.
ID: 0336
Title: Limit the number of lines read from a single logfile
Component: Livestatus
Level: 2
Class: Bug Fix
Version: 1.2.5i1
If for some reason you have very large history logfiles with millions of
entries then Livestatus would consume large amounts of memory while parsing
these when you access the <tt>log</tt> table. This could lead to a hanging
system or even a crash.
In order to avoid such situations the number of lines that are read from each
individual file are now limited. The default limit is one million lines. You
can change this default by defining the variable <tt>max_lines_per_logfile/tt>
in your <tt>nagios.cfg</tt>. The following example sets the maximum number
to 20 million lines:
F+:
broker_module=/some/path/livestatus.o max_lines_per_logfile=20000000 ...
F-:
When using the Check_MK Micro Core the configuration can be done
via WATO global setting <i>Maximum number of parsed lines per log file</i>.
ID: 0058
Title: Fix email notifications containing non-ASCII characters in some situtations
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.5i1
On some systems the locale C.UTF-8 was not always available. One of these is
Debien Squeeze. Sending a notification email containing non-ASCII characters
like german Umlauts failed in these situations.
This now has been fixed by scanning all available encodings (output of locale
-a) and selecting an existing UTF-8 encoding. Please make sure that at least
one such encoding exists.
This fix also makes sure that the output of a failed mail submission is
being logged in the notification log (if you have enabled it).
ID: 0089
Title: CSV export of event console was broken
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.3i8
For views of event console the CSV export did produce a file containing only
an error message. This is fixed now.