[Release] Checkmk stable release 1.6.0p16

Dear friends of Checkmk,

the new stable release 1.6.0p16 of Checkmk is ready for download.

This maintenance release ships with 11 changes affecing all editions of Checkmk,
0 Enterprise Edition specific changes and 0 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

Checks & agents:

  • 11234 Check_MK service: State if “Unexpected allowed IP ranges” is configurable
  • 11302 FIX: Azure Storage: egress data levels wrongly labelled on user interface
  • 11239 FIX: Check_MK Discovery: Revert werks 10534, 11229 and 11238
  • 11238 FIX: Check_MK Discovery: Was unable to discover new SNMP check types
  • 11144 FIX: Display graph for SAP HANA License
  • 11303 FIX: mem.linux: false CRIT status when VmallocChunk is set to 0 kB

Core & setup:

  • 11263 SEC: Fix piggyback path traversal
    NOTE: Please refer to the migration notes!

Event console:

  • 11261 FIX: Fix performance regression caused by too many live status queries between EC and core

Notifications:

  • 11051 FIX: crash in notifications if “Exclude Service Groups (regex)” is used

Site management:

  • 11341 FIX: Make omd restore work with hardlinks in local dir

User interface:

  • 10544 FIX: Quicksearch: Fixed incorrect result page when querying host tags

Changes in the Checkmk Enterprise Edition:

NO CHANGES

Changes in the Checkmk Managed Services Edition:

NO CHANGES

You can download Checkmk from our download page:

Please mail bug reports and qualified feedback to feedback@checkmk.com.
We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

2 Likes

:warning: The SLES 15 SP1 CEE package misses msiinfo, msibuild and lcab to build Windows agents.

Heads-up: SSL-Check is bugged

@morbloe I have a rule “WARN if below 45 days and CRIT if below 30 days” and the plugin gets called with -C '45,30'. Yours is being called with -C 5,20 so I guess you mixed up the WARN and CRIT levels?

1 Like

maybe, but then it should have been critical by now, but it is green.

1 Like

I switched the values, now it is warning

I second that. I currently don’t have the time to look into the plugin (it’s a binary anyways, IIRC), but I agree it’s buggy. The check should be as simple as

if actual_value < crit_level:
    state=CRIT
elif actual_value < warn_level:
    state=WARN
else:
    state=OK

But maybe the plugin tries to check it the other way round:

if actual_value > warn_level:
    state=OK
elif actual_value > crit_level:
    state=WARN
else:
    state=CRIT

In that case it would return OK for your values. Wrongly.