ID: 8260
Title: Improved handling of baking errors in Agent Bakery
Component: agents
Level: 1
Class: Bug fix
Version: 1.2.7i3
When baking of one agent failed for any reason, the following agents were
not baked anymore. This has been changed now. The error message is printed
out to the user and the bakery continues to build the other agents.
Improved handling of unbacked agents for hosts.
ID: 8261
Title: Fixed using cached agent data during regular checks
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.7i3
During runtime of the CMC it might happen that the data gathered
by the Check_MK Helpers is not up-to-date since they were using
cached data during checks. This only happened when having the
"Check_MK Discovery" service activated which regularly checks for
new services to be monitored.
Once the "Check_MK Discovery" services was executed for one host
in a helper process, this problem occured for all further checks
being performed by this helper.
ID: 8254
Title: Bakery: MySQL credentials can now be configured (for Linux and Windows)
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.2.7i1
ID: 8255
Title: Agent configs containing a customized "agent path" were not visible in the GUI
Component: agents
Level: 2
Class: Bug fix
Version: 1.2.7i3
None of the baked agents which used the rule "Installation paths for agent files (Linux, UNIX)"
were baked correctly and available on the filesystem, but not shown in the GUI.
ID: 8256
Title: Printing an error message when starting the Microcore when the config is missing
Component: cmc
Level: 1
Class: Bug fix
Version: 1.2.7i3
ID: 8257
Title: Fixed crashing of core when rendering a lot of performance graphs in a short time
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.7i3
The core could crash when a single user or multiple users were requesting a lot
of performance graphs in a short time. This was caused by a non thread safe
code in the used rrdtool library which made the core crash.
ID: 8252
Title: Fixed invalid data returned by SNMP GET requests executed after the bulkwalks
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.7i1
After all bulkwalks which return an empty set of data without having an error situation,
an SNMP GET is performed to verify that there really is no data at the requested OID.
The inline SNMP code was treating some error situations like NOSUCHOBJECT or NOSUCHINSTANCE
which occur when a device does not know the requested OID wrong. It returned an empty string
instead of no data which might confuse our SNMP engine or checks.
ID: 8251
Title: Inline-SNMP did not use bulkwalk for SNMPv3 hosts
Component: inline-snmp
Level: 1
Class: Bug fix
Version: 1.2.7i1
Inline-SNMP was using normal SNMP walks which are way less
performant than bulkwalks when just SNMPv3 was configured
without marking the hosts as bulkwalk hosts. But we intended
to make ALL SNMPv3 hosts use bulkwalk.
ID: 8228
Title: emc_isilon_quota: OID Range for SNMP Walk can now be limited.
Component: inline-snmp
Level: 1
Class: New feature
Version: 1.2.7i3
This prevents timeouts if you have thousands of quotas.
You can configure that in the WATO rule: "Limit SNMP OID Ranges for Bulkwalks".