ID: 8088
Title: Fix problem with Smart PING packets not being sent (Out of Buffer Space)
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i6
This problem has been fixed by splitting up the <tt>icmphelper</tt> into
a <tt>icmpsender</tt> and a <tt>icmpreceiver</tt>. Both processes now do
not need to do any <tt>select()</tt>. The pcap-library can thus be used
in a standard way. Previously it could happen that it did not see all
packets.
ID: 8089
Title: Fix instant reports in views with a context (e.g. one Services of one Host)
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.2.6b1
In non-global views the instant reports showed always empty tables. This was
due to an invalid set single-context and is now fixed.
ID: 8078
Title: All Linux agent plugins now supported by agent bakery - except ORACLE
Component: agents
Level: 3
Class: New feature
Version: 1.2.5i6
The new agent bakery now supports all official Check_MK agent plugins
for the Linux agent - in the variants RPM and DEB. The only exception
are the ORACLE agent plugins since these are currently being rewritten.
As soon as they are finished, they also will be supported.
ID: 8076
Title: New option cmk --rrd-convert for convertig existing RRDs
Component: config
Level: 2
Class: New feature
Version: 1.2.5i6
This new commanline option for the <tt>cmk</tt> tool will change exising
RRD databases to match the configuration that is done via the WATO rulesets
<i>Configuration of RRD databases of hosts</i> and <i>Configuration of RRD
databases of services</i>. Otherwise changes in these rules applied only on
new RRDs.
You can restrict the conversion to one or several hosts:
C+:
OM:cmk -v --convert-rrds myhost1 myhost2
myhost1:
HOST
- rta....uptodate
- pl....uptodate
- rtmax....uptodate
- rtmin....uptodate
Postfix Queue
- length....uptodate
- size....uptodate
CPU utilization
- user....converted, 376 KB -> 40 KB
- system....converted, 376 KB -> 40 KB
- wait....converted, 376 KB -> 40 KB
[...]
C-:
If you do not specify any hostname, then <b>all</b> RRDs will
be converted.
<b>Note:</b> this new option uses a completely new feature of the RRDTool,
which has been sponsored by Mathias Kettner: RRDTool can now change the
internal structure of RRDs on-the-fly. That way it is now for example possible
to change the range of time or precision that data is being kept.
<b>Note 2:</b> this feature uses an <b>experimental</b> version of
RRDTool. Please make a backup of your RRDs before trying this out.
ID: 8077
Title: New option --split-rrds for --rrd-convert, converts PNP storage type
Component: config
Level: 2
Class: New feature
Version: 1.2.5i6
Check_MK has now a new builtin function for converting legacy-style PNP RRDs
from storage type <tt>SINGLE</tt>, which had been the default for many years,
to <tt>MULTIPLE</tt>, which is the current default since about three years.
<tt>SINGLE</tt> means that all metrics of one host or service are stored
in a single round robin database, whereas with <tt>MULTIPLE</tt> each RRD
does contain only one single datasource.
Performance tests have revealed that - other then one might guess -
<tt>MULTIPLE</tt> is not significantly slower. But it has the advantage
that new datasources can be added on the fly. This is often needed when new
versions of Check_MK introduce new metrics. For that reason Check_MK only
fully supports storage type <tt>MULTIPLE</tt>. When using the Check_MK
Micro Core then you <b>have</b> to convert to <tt>MULTIPLE</tt>, if you do
not want to loose your historic metrics, because the CMC does not support
<tt>SINGLE</tt> at all.
Converting RRDs - essentially splitting them up - can be done with PNP4Nagios'
shipped utility <tt>lib/pnp4nagios/rrd_convert.pl</tt>, but that is a bit
clumsy to use and very slow. If you have thousands of hosts the conversion
can take many days.
For that reason Check_MK now can do the splitting into multiple RRDs during the
process of the RRD conversion. This is not only simpler for you. It is also
much faster because it uses the native C code of the recent RRDTool. This
is how to do the conversion. We assume that you are using Nagios as your
monitoring core:
<ol>
<li>Make a backup of the directory <tt>var/pnp4nagios/perfdata</tt>.</li>
<li>Stop the <tt>npcd</tt>. This avoids RRD updates while the conversion is in progress:
C+:
OM:omd stop npcd
C-:
</li>
<li>Start the conversion. The option <tt>-v</tt> selects verbose output:
C+:
OM:cmk -v --convert-rrds --split-rrds
C-:
</li>
<li>Edit the file <tt>etc/pnp4nagios/process_perfdata.cfg</tt> and
change the storage type:
F+:etc/pnp4nagios/process_perfdata.cfg
RRD_STORAGE_TYPE = MULTIPLE
F-:
</li>
<li>Start the <tt>npcd</tt> again:
C+:
OM:omd start npcd
C-:
</li>
</ol>
<b>Notes:</b>
<ul>
<li>You can specify host names as arguments to <tt>cmk --convert-rrds</tt>. The conversion
will then only be done for these hosts. But when you start <tt>ncpd</tt> again and only
some of the hosts are being converted, then hosts that do not match the storage type
in <tt>process_perfdata.cfg</tt> will loose their RRD data.</li>
<li>The splitting and the conversion to the RRD configuration that is setup via WATO
with the rulesets <i>Configuration of RRD databases of hosts</i> and
<i>Configuration of RRD databases of services</i> will be done at the same time. There
is no way to just split. But the <i>Default</i> configuration of PNP4Nagios and of
WATO for the RRDs is the same, so if you have changed neither, you essentiall will
just split.</li>
<li>Check_MK will <b>not create any backups of any files!</b> Failed modifications, unlucky RRD
configuration and software bugs can lead to data loss. Make sure you have a backup.</li>
</ul>
ID: 8071
Title: Add variables (HOST/SERVICE)ACK(AUTHOR/COMMENT) to notification context
Component: cmc
Level: 1
Class: New feature
Version: 1.2.5i6
The four variables <tt>HOSTACKAUTHOR</tt>, <tt>HOSTACKCOMMENT</tt>,
<tt>SERVICEACKAUTHOR</tt> and <tt>SERVICEACKCOMMENT</tt> can now be used. In
notifications for acknowledgements these variables reflect the author and
the comment of the acknowledgement.
ID: 8073
Title: Fix missing first character of downtime comments in logfiles
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.5i6
The first character of downtime comments where missing when parsing
the monitoring logfiles. This was an ancient bug in Livestatus, which
never has shown up since Nagios does not log anything useful in the
comment field a downtime entries.
ID: 8075
Title: Implement external commands DISABLE/ENABLE_HOST_SVC_NOTIFICATIONS
Component: cmc
Level: 1
Class: New feature
Version: 1.2.5i6
These commands are compatible with the Nagios monitoring core and allow to
enabled or disable the notifications on all services of a certain host.
ID: 8074
Title: Avoid delaying notifications for WARN/CRIT changes during periodic notifications
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i6
When you use period notifications and have a hard state change e.g. from WARN to CRIT
then the notification for this state change would be delayed until the next periodic
notification.
This has been fixed. Any non-OK state change will now immediately be notified.
Furthermore any first notification delay will <b>not</b> be applied in that case.
ID: 8066
Title: Fix problem where manual cmk -O or cmk -R would not activate changes for CMC
Component: config
Level: 1
Class: Bug fix
Version: 1.2.6b1
If you create a new host in WATO, then go to the command line, do a <tt>cmk -I<tt>
and then <tt>cmk -O</tt> or <tt>cmk -R</tt> then your changes would not be activated.
This is due the CMC Rushead Daemon. It had created a valid configuration after the
last WATO operation. Check_MK used that configuration on the next reload. Now a
<tt>cmk -O</tt> or <tt>cmk -R</tt> on the command line assumes that you have done
changes on the command line and ignores the configuration of the Rushahead daemon.
Note: There is still the problem that a change on the command line cannot be
activate with WATO. This will not be fixed. If you do something on the command line
then please activate it on the command line.