ID: 5771
Title: Created wrong SNMP cache folder 'var/check_mk/HOST'
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 1.5.0i4
The right folder for SNMP cache data is 'var/check_mk/snmp_cache/HOST'.
This was introduced with Check_MK version 1.5.0i2. Fixed that!
ID: 5893
Title: Fixed some report table layout problems
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.5.0i4
The following problems have been fixed:
<ul>
<li>Single dataset tables: (host/service details) had no top border</li>
<li>Single dataset tables: Disable row shading now also works for left headers</li>
<li>Graph columns were adding emtpy space after the graph column</li>
</ul>
ID: 5891
Title: Fixed column layout of host/service report tables (smaller titles)
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.5.0i4
The title and content columns of the single host/service reports were
using the same width which looked bad, especially for pages that contain
graphs.
ID: 5909
Title: fortigate_sessions, fortigate_cpu: Fixed duplicated discovery if needed information is at two places
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
Fortigate changed obviously the location of information for cpu utilization
and sessions in the past. We support these by using two different check
plugins. With this fix the service discovery does not create duplicated
services anymore if both paths are present on the device. Instead the newer
path will be preferred.
ID: 5712
Title: cisco_mem, cisco_mem_asa, cisco_mem_asa64: No longer crash when total memory is reported as 0.
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
The state in case of 0 total memory is still UNKNOWN, but the error message is more helpful.
ID: 5711
Title: cisco_mem_asa64: Fix incorrect labelling of graph
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
Previously, the performance value would be incorrectly displayed
as absolute usage in the GUI, when it is in fact relative.
This has been fixed.
ID: 5706
Title: Windows agent: fix endianness of IP addresses
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i4
The string conversion of IP addresses was falsely done manually in
network byte order, resulting in incorrect ouput for IPv6 addresses.
Now the conversion is done correctly.
This fix will shortly break the compatibility of logwatch state files
stored by the mk_logwatch plugin of previous versions of the Windows
agent as they use the remote IP address(es) of the monitoring host(s).
When upgrading to the new agent, those log entries that are created
exactly after stopping the old agent but before starting the new agent
will be lost in monitoring. After starting the new agent, monitoring
should work as before.