[Release] Checkmk stable release 1.6.0p16

Announcements
, ,
1

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

3 Likes
2

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

3

grafik
grafik1088×858 52.1 KB

Heads-up: SSL-Check is bugged

4

@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
5

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

1 Like
6

I switched the values, now it is warning

7

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.

8

Hello Team,
Here you fixed : mem.linux: false CRIT status when VmallocChunk is set to 0 kB
I am having 1.6.0p20, but I am getting the issue?
what I can do here?
any suggestions?

9

I have a suggestion - upgrade to a supported version of checkmk…
Even checkmk 2.0 has reached end of passive maintenance.

4 Likes
10

this is out of our boundary line, this monitoring tool is under our organization so suggest me some other solution!!

11

Hi @vishu! This is not a support portal, but a community forum. People are here mostly in their free time and they help on a voluntary basis. So the very least one should do is appreciate these people.

If you are not happy with the free support from this community, you are more than welcome to approach our sales team to acquire paid support.

6 Likes
12

Hey @robin.gierse I appreciate there suggestion but when I go and discuss to implement that I get to know it is not feasible for us!!

So I just have the question It it is fixed in 1.6.0p16 then why this comes up in 1.6.0p20.
or possible to get manual fix, so I can perform same thing to fix ,that you check_mk engineer did here!

13

Just disable the check as suggested in other posts, e.g.:

2 Likes
14

If we are talking about feasibility, then let me emphasize again what @aeckstein already said: Checkmk 1.6 is so EOL, even its successor is EOL already. If you really want to know, what Checkmk can do for you, use the current version, which is 2.2 as of writing.

4 Likes
15

Hi @vishu

While I agree with everyone, that you should update to 2.2, you may want to
consider to update at least to the latest available release of the 1.6 branch
which is 1.6.0p30.

Additionally, have you checked the value of VMallocChunk in /proc/meminfo on
the host in question? Maybe… the check is raising an alert for a reason… :slight_smile:

Nice article about “what is what” in /proc/meminfo:
RHEL KB: /proc/meminfo values and their meaning
Note: Yes, this is quite old, but as far as I know the information in this article, is still valid.

HTH,
Thomas

1 Like
16

Thank you all for the suggestions, as Suggested by Dirk looking into another forum discussion to disable VMalloc in check_mk