[Release] Checkmk stable release 2.3.0p33

Announcements
, , , ,
1

Dear friends of Checkmk,

the new stable release 2.3.0p33 of Checkmk is ready for download.

This stable release ships with 43 changes affecting all editions of Checkmk,
0 changes for the Enterprise editions, 1 Cloud Edition specific and
0 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

BI

  • 17897 BI: improve compiler performance…

Checks & agents

  • 18010 Netapp ontap aggregates: add monitoring of root aggregates…
    NOTE: Please refer to the migration notes!
  • 18015 fortimail_cpu_load: Enable explicitly configuring no upper thresholds…
  • 17985 SEC: jar_signature: Fix privilege escalation via insecure JAVA_HOME path handling…
  • 18023 FIX: mk_docker: do not collect Environment dump…
    NOTE: Please refer to the migration notes!
  • 18022 FIX: multipath: fix division by zero crash…
    NOTE: Please refer to the migration notes!
  • 17966 FIX: Age of Latest Backup by Timemachine: Handle ‘.backup’ suffix in filename…
  • 17962 FIX: Bulk discovery: Apply changes to existing services if ‘Update host labels’ is selected…
  • 17642 FIX: Extension packages: prevent duplicate display of files…
  • 18012 FIX: Netapp environment sensors: handling states different from normal…
  • 17882 FIX: Ruleset API: Migration of AgentConfig rulespecs…
  • 18013 FIX: agent_prism: handle connection timeouts gracefully…
  • 17770 FIX: aws_dynamodb_table: Fix parsing issue…
  • 17768 FIX: brocade_sfp: Fix SFPs not getting discovered…
  • 18026 FIX: check CRIT in case of broken paths…
  • 18056 FIX: cisco_asa_conn: Report lone-standing IP addresses instead of crashing…
  • 17740 FIX: cisco_vpn_tunnel: Skip tunnels without phase 1…
  • 17938 FIX: docker container diskstat: fix parsing of io.stat line…
  • 18020 FIX: docker_container_status_health: fix check when health logs are empty…
  • 18051 FIX: esx_vsphere_datastore_io: Discard metrics with negative values…
  • 17944 FIX: fortimail_disk_usage: Fix “Invalid check parameter” error in service discovery page…
  • 18009 FIX: haproxy: Support for different socket paths…
  • 18005 FIX: hp_proliant_da_cntlr: Convey meaning of state “other”…
  • 17898 FIX: hp_proliant_da_cntlr: handle missing data…
  • 17744 FIX: prism_hosts: Optionally alert if Acropolis state is disconnected…

Core & setup

  • 17939 FIX: Core restart did not correctly check for updated files…

Event console

  • 17858 FIX: Correct escaping of double backslashes in notifications…

HW/SW inventory

  • 18031 FIX: HW/SW Inventory: Do not store zipped status data trees

Notifications

  • 18071 FIX: Also match service labels for custom checks…
  • 17857 FIX: Notification test: Fix sending of notifications…

Other components

  • 18187 SEC: NagVis: Updated to 1.9.47…
  • 18188 FIX: NagVis: Fix business intelligence backend…

REST API

  • 17952 FIX: REST-API: Improve documentation for rule endpoints…

Setup

  • 17854 FIX: Migrate all bulk discovery settings on update…
  • 18121 FIX: Remove 0-24 weekday prefill when adding new time period…
  • 17823 FIX: views: cloning builtin views should clone everything from the original view…

Site management

  • 14846 FIX: Readd utils.pm symlink…

User interface

  • 17926 Add exact match filter for Host & Service check commands…
  • 17856 FIX: Correct indentation for “Tree of folders” snapin…
  • 17927 FIX: Fix filter delete button floating in Safari…
  • 17719 FIX: Host name validation on “Add host” page…
  • 17925 FIX: Rename filters “Host/Service check command” to indicate using regex…
  • 17717 FIX: Selection of metrics starting with a digit now possible…

Changes in the Checkmk Enterprise Edition:

NO CHANGES

Changes in the Checkmk Cloud Edition:

Checks & agents

  • 17743 FIX: azure_resource_health: Fix ‘Item not found in monitoring data’…

Changes in the Checkmk Cloud (SaaS):

NO CHANGES

Changes in the Checkmk Managed Services Edition:

NO CHANGES

You can download Checkmk from our download page: Download Checkmk for free | Checkmk

List of all changes: Werks

We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

2 Likes
2

After the update from check mk raw edition 2.3.0.p32 to → 2.3.0p33 all the HP ILO’s are giving this warning for the HW Controller service;

Condition: ok, Board-Condition: other (The instrument agent does not recognize the status of the controller. You may need to upgrade the instrument agent.) WARN , Board-Status: other (The instrument agent does not recognize the status of the controller. You may need to upgrade the instrument agent.) WARN ,

This change should be the reason why Werk #18005: hp_proliant_da_cntlr: Convey meaning of state “other”

Currently i’m not yet using redfish for the ILO’s but rather still SNMPv2.
I know SNMP is outdated so it is probably smarter to start using Redfish and ditch SNMP.

I also found this topic and their solution was to switch to redfish; HPE Integrated Lights-Out (ILO) 5 3.0 breaks storage monitoring on SNMP Management Board - Troubleshooting - Checkmk Community.

Does someone have an idea for the solution with SNMP or should is start using Redfish?

1 Like
3

I would suggest starting RedFish,

i myself started using it a few patches ago ( on 2.3.0pX - dont really recall what patch-level, but i think it was somewgere around p25)

For me my setup is HP DL360Gen9, with iLo version 2.82 , and have had no issues since switching.

  • Glowsome
1 Like
4

Here you find the current mapping table: checkmk/cmk/base/legacy_checks/hp_proliant_da_cntlr.py at 0b68be456036a63c34633d33e9231a5930e253b7 · Checkmk/checkmk · GitHub

Maybe you can check the value of this OID?
I think the value “1” means the message in the screenshot.

image
image1174×388 86.3 KB

1 Like
5

Now that you have fixed escaping in Notifications (which I hadn’t noticed tbh) I think the Werks page also needs the same fix :rofl:

Even texts like “\HOSTNAME\PATH\FILE” were shown as “\HOSTNAME\PATH\FILE” in the resulting notification.

git commit:

Even texts like "\\HOSTNAME\PATH\FILE" were shown as "\HOSTNAME\PATH\FILE" in
the resulting notification.
6

Hi everyone,
is it just me or did this patch break the “Service check command (exact match)” search filter in views?
No matter which command I select from the list of available commands, there are no more search results to be found.
Werk #17925: Rename filters "Host/Service check command" to indicate using regex hints to a change here but I’m also unable to find the renamed filter…?

1 Like
7

Hi all,
we can confirm this, the “Service check command (exact match)” search filter in views has no search results anymore in p33.

8

Hi @fabian.binder , Hi @T.Schmitz
Thanks for reporting this. This was already fixed yesterday Werk #17929: Fix filterquery for host/serice check command (exact match) filter and will be part of the next patch release. You can ignore the versions. Its a display issue.

2 Likes