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.
ID: 0311
Title: Fixed "Inventory failed" message when trying an inventory on clusters via WATO
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.3i8
The service inventory of cluster hosts via WATO failed all the time with an error message
like "Inventory failed for this host: Error - host is unreachable, no usable cache file present".
This error has been fixed with this change.
A WATO-inventory on a cluster node also no longer removes previously detected clustered services.
ID: 0311
Title: Fixed "Inventory failed" message when trying an inventory on clusters via WATO
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.3i8
The service inventory of cluster hosts via WATO failed all the time with an error message
like "Inventory failed for this host: Error - host is unreachable, no usable cache file present".
This error has been fixed with this change.
ID: 0086
Title: timemachine: new check
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.3i8
Checks the age of latest backup by timemachine on MAC OS and compares the age against given levels.
ID: 0057
Title: Fix exception in WATO host editor on custom tag without topic
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.3i7p1
When you've defined a host tag group in WATO that has no topic,
then the host edit dialog would be interrupted with an exception.
A simple workaround to this is to alwasy define a topic.
The problem has now been fixed. It had shortly been introduced by fixing a
problem appearing when you used a slash in the name of a tag group.
ID: 0057
Title: Fix exception in WATO host editor on custom tag without topic
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.3i8
When you've defined a host tag group in WATO that has no topic,
then the host edit dialog would be interrupted with an exception.
A simple workaround to this is to alwasy define a topic.
The problem has now been fixed. It had shortly been introduced by fixing a
problem appearing when you used a slash in the name of a tag group.