[Release] Checkmk stable release 2.1.0p25

Dear friends of Checkmk,

the new stable release 2.1.0p25 of Checkmk is ready for download.

This maintenance release ships with 23 changes affecting all editions of Checkmk,
6 Enterprise Edition specific changes and 1 Managed Services Edition specific changes.

Support periods can be found here: Checkmk versions

Changes in all Checkmk Editions:

Agent bakery:

  • 15457 FIX: agent-receiver: Update old symlinks to fix crash after omd cp…


  • 14186 FIX: BI configuration: do not duplicate hints in call-a-rule argument fields

Checks & agents:

  • 14800 Update pymssql to 2.2.7
  • 15496 esx_vsphere_snapshot: Added vm name to the snapshot summary
  • 15446 mssql_instance: support Microsoft SQL Server 2022
  • 14591 FIX: Electrical Power for Devices with only one phase: Remove error message during discovery…
  • 14593 FIX: KUBE: Fix crash upon specifying a resource of 1k Pods…
  • 14597 FIX: KUBE: Handle Pod with a non-existing Node…
  • 14730 FIX: Logwatch EC forwarding using spool files…
  • 14188 FIX: Logwatch Monitoring: Fixed disappearing log lines when fetching data from an older 2.0 agent
  • 14592 FIX: PSU Capacity Levels: Remove error message during discovery…
  • 15245 FIX: Remove unexpected service for certain cluster setups…
  • 15246 FIX: Stale services on cluster nodes when the cluster is excluded from monitoring…
  • 15419 FIX: Windows agent: Run plugins/local checks using non-system account…
  • 14589 FIX: apache_status: Handle Permission Errors…
  • 15456 FIX: mailbox: Fix exchangelib warning in the service summary…
  • 15247 FIX: Prefer enforced services over discovered ones if clustered…
    NOTE: Please refer to the migration notes!


  • 15069 SEC: Fix Email HTML Injection…


  • 13975 FIX: ‘group’ parameter has been removed from rulset search…
  • 15476 FIX: Fix error if only auxiliary tag help is updated via REST API
  • 15434 FIX: agent: return better respones for GET collection…
  • 15435 FIX: password: return better responses for GET collection…

Site management:

  • 14799 FIX: pip3 command…

Changes in the Checkmk Enterprise Edition:

Agent bakery:

  • 15418 FIX: Agent bakery: Provide AIX tar.gz package in USTAR format…

Core & setup:

  • 14952 FIX: Fix microcore crash caused invalid data in history files…
  • 14949 FIX: Malformed UTF-8 data no longer result in loss of state file…


  • 14950 FIX: Correct processing of the rule Install Python runtime environment…

The Checkmk Micro Core:

  • 15254 FIX: Fixed incorrect availability calculation when a host was removed and added again…

User interface:

  • 15255 FIX: Fixed removal of persistent acknowledgements

Changes in the Checkmk Managed Services Edition:


  • 14189 FIX: Fixed incorrect assignment of customer sensitive host data to other customers

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

List of all changes: Werks

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


There is error during the update

/omd/versions/2.1.0p25.cre/bin/python3: error while loading shared libraries: libcrypt.so.2: cannot open shared object file: No such file or directory

Do you have any idea how to resolve this error?


Which Operating system are you running your Checkmk instance on ?

|OS Type|Linux|
|OS Version|8.7|
|OS Name|Rocky|
|OS Platform|64-bit|

Can you share the output of the below command:

rpm -qa|grep -i mk

Hi @jsinic ,
could you post the full name of the rpm sourcefile you’ve downloaded & installed?


Install libcrypt with python

apt install libxcrypt
pip install pygcrypt

sudo apt install libcrypt1:i386
sudo dpkg --add-architecture i386
sudo apt update

This will 100% not work on Rocky linux

1 Like

This commands is for Ubuntu or Debian, you can search equivalents comands for rocky

Seems that p25 has one nice bug. Clear log is not working

It says, log cleared, but then if you Rechedule next check, log contains again messages which were cleared. And check is not going to green. It stays now critical forever.

edit: And another bugs. When scheduling downtime via ‘Custom time range’ button for multiple services, it set downtime for random services, not all, despite all are checked.

Same applies for ‘Acknowledge’. From 79 selected rows, it Acknowledged for 5 random services only.