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: 0357
Title: megaraid_bbu: Fixed expected state checking
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The check was unable to check the hard coded expected states. This
made the check never raise expected alerts.
ID: 0337
Title: New header for limiting the execution time of a query
Component: Livestatus
Level: 1
Class: New Feature
Version: 1.2.5i1
The new Livestatus header Timelimit: sets an upper limit
for the execution time of a query. Specify the timeout as
a number of seconds. The following query will stop after
5000 lines of output. If that takes longer than 30 seconds,
then the query <b>fails with no output</b>:
F+:query.lql
GET log
Columns: message
Timelimit: 30
Limit: 5000
F-:
Please note, that <tt>Limit:</tt> and <tt>Timelimit:</tt> have
a different behaviour when the limit is reached:
<li class=list><tt>Limit:</tt> end the query, output all rows that
have been found so far.</li>
<li class=list><tt>Timelimit:</tt> abort the query with an error,
do not output any lines.</li>
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: 0355
Title: heartbeat_crm: Now handling "Failed actions:" output in agent
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
When there is a "Failed actions:" info block provided by the agent,
the inventory code of the check failed with an exception. This has
been fixed now.
ID: 0356
Title: Fixed exception caused by utf8 chars in tooltip text
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.5i1
When displaying a view with a column showing utf8 chars in
the tooltip text, this resulted in an exception:
<tt>UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 19: ordinal not in range(128)</tt>
This has been fixed now.
ID: 0334
Title: cisco_fantray: Fixed error on Cisco devices which do not support this check
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i1
When doing an inventory on cisco devices which did not support this check, the
check created an error message.
ID: 0333
Title: Fixed too long page title during performing several actions
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The page title reflects the current page. A bug caused this page title
to be appended to the current title instead of being replaced. This resulted
in too long page titles when performing e.g. actions in WATO
ID: 0332
Title: Own host tag groups without topics resulted in two groups "Host tags" in the rule editor
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i1
ID: 0335
Title: Parse state of downtime notification log entries correctly
Component: Livestatus
Level: 1
Class: Bug Fix
Version: 1.2.5i1
The state information of log messages of notifications that are
triggered by downtimes was not correctly parsed. This has been
fixed.