ID: 8067
Title: Delay service notification when host comes up
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.6b1
When a host is DOWN and then a service of that host goes CRIT, the
corresponding notification is put on hold. As soon as the host goes up again
the notification would immediately be sent out. Now we rather wait for the
next check of the service, in order to give it a chance to become OK again,
after the host is reachable again.
ID: 8069
Title: Support $HOSTALIAS$ in definition of active checks
Component: config
Level: 1
Class: New feature
Version: 1.2.5i5
The macro <tt>$HOSTALIAS$</tt> is now supported in all places in the
configuration where also <tt>$HOSTNAME$</tt> is allowed.
ID: 8070
Title: Fix notification type for the end of downtimes
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i6
When a downtime ends the CMC used to set the NOTIFICATION_TYPE to
<tt>DOWNTIMESTOPPED</tt>, while Nagios uses <tt>DOWNTIMEEND</tt>. This
leads to an invalid notification classification in the rule based
notification, so that instead of the type <i>Downtime Start or End</i>
a normal altert type was being assumed. That has been fixed now.
ID: 8063
Title: Recover broken RRD files after disk-full situation
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.6b1
In a situation where you are ouf of disk space RRDTool will create
empty <tt>*.rrd</tt> files. The CMC considered these later as existing
and would not attempt to recreate them. This has been fixed and
zero-sized RRD files are considered to be non-existant now.
ID: 8064
Title: Remove bogus error messages in cmc.log when core restarts
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.6b1
When you restart the core and there are currently running Check_MK checks
that have to be aborted then the CMC logfile prints a line:
F+:cmc.log
2014-12-01 10:57:26 [5] Check helper [24933] exited with status 1
F-:
This line has been reclassified from error (<tt>[3]</tt>) to notice
(<tt>[5]</tt>). This will avoid bogus error message in the logfile monitoring
of the Check_MK appliances.
ID: 8065
Title: Savely direct any verbose or diagnostic output from check_mk or checks to cmc.log
Component: cmc
Level: 2
Class: New feature
Version: 1.2.6b1
If any check outputs something to stdout or stderr (which it should not do in
production mode) or if a function in the check_mk code (such as inline SNMP)
outputs data to stdout or stderr, then this will now savely be logged to the
CMC log with the classification "warning". This will allow easier debugging
and error handling. Also the logfile <tt>cmc-helper.log</tt> will no longer
be created. Messages go into <tt>cmc.log</tt> instead.
ID: 8057
Title: Avoid SmartPING timeouts in situation of high disk I/O
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i5
In situations where the operating system in in high disk I/O and
many processes run into disk wait, the micro core seemed sometimes
to register PING timeouts. That was simply due to the fact that
the core itself was delayed and thought the PING packages didn't
arrive in time.
This has now been fixed, by assuming that when checking the
PING timeout taking into account the time since the last check:
CMC assumes now that all PING must have arrived directly at
the beginning of the current interval, not at the end.
ID: 8058
Title: Fixed problems with SNMP GET where non requested OIDs were answered
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.5i5
Some devices do not really care about the requested SNMP OID when they do
not know this OID. It happened here that a device simply answered with the
next known OID. This confused several of our checks.
The SNMP GET does now verify the OID provided with the response against
the requested OID and ignores non matching responses.