[Release] Checkmk stable release 2.1.0p11

Dear friends of Checkmk,

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

This maintenance release ships with 27 changes affecting all editions of Checkmk,
4 Enterprise Edition specific changes and 0 Managed Services Edition specific changes.

Support periods can be found here: Checkmk versions

Changes in all Checkmk Editions:

Agent bakery:

  • 14531 FIX: azure special agent: fix usagedetails section
  • 14610 FIX: super_server: Missing systemd units/xinetd services after agent update (RPM)
    NOTE: Please refer to the migration notes!
  • 14731 FIX: super_server: Reenable “Checkmk agent network service (Linux)” ruleset
    NOTE: Please refer to the migration notes!

Checks & agents:

  • 14675 Add universal scan function for cisco ip sla check
  • 14552 FIX: Invalid rule configuration for static checks after upgrade
  • 14553 FIX: Prometheus: Bad request url /api/v1/api/v1/status/buildinfo
  • 14761 FIX: SAP Hana fileinfo: negative file age causes crash
  • 14672 FIX: The Ceph MGRs check now checks if epoch information is available
  • 14764 FIX: apc_mod_pdu_modules: total power measurement displayed at wrong scale
  • 14693 FIX: clustering: Fix clustering in case of failover
  • 14505 FIX: heartbeat_crm_resources: services not discovered under pacemaker version >= 2
  • 14674 FIX: ibm csv eventlog check now compatible with IBM FlashSystem 900
  • 14762 FIX: mk_postgres.py: instances not found under Linux for PostgreSQL version >= 13
  • 13427 FIX: ucs_rack_server_psu_voltage no longer discovers fabric interconnect PSUs
  • 14671 FIX: vsphere memory check is stale for powered off machines
  • 14694 FIX: bluecoat_sensors: Fix duplicate service names
    NOTE: Please refer to the migration notes!
  • 14140 FIX: kemp_loadmaster_realserver: incorporate virtual services
    NOTE: Please refer to the migration notes!


  • 14381 SEC: Fix command injection in SMS notification script
  • 14745 FIX: Fix “Data: b’'” in notification result of event console bulk notifications

Other components:

  • 14291 SEC: NagVis: Updated to 1.9.34 (Fix security issues)


  • 14673 FIX: Allow to GET bi aggregation state with wato disabled
  • 13956 FIX: The BI Pack endpoints will now check if the given contact groups actually exist


  • 14717 Local customizations might need adjustment due to structural refactorings in GUI code
    NOTE: Please refer to the migration notes!
  • 14382 SEC: Don’t leak LDAP server address when connection fails
  • 14383 SEC: Fix code injection in watolib

User interface:

  • 14473 FIX: Fix GUI crash if unknown theme was used in global settings
  • 14742 FIX: Fix combined search for tag groups

Changes in the Checkmk Enterprise Edition:

Agent bakery:

  • 14718 FIX: SAP HANA bakery plugin: Handle user store key correctly
  • 14732 FIX: cmk-update-agent: Retry locking
  • 14609 FIX: super_server: Cleanup config files when installing a bakery package
    NOTE: Please refer to the migration notes!

Core & setup:

  • 14771 FIX: Fix ping endpoint for InfluxDB

Changes in the Checkmk Managed Services Edition:

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


Is there a specific reason, that the image is called -rc2?

docker load --input=check-mk-enterprise-docker-2.1.0p11.tar.gz 
8b45c44b15e0: Loading layer [==================================================>]  2.048kB/2.048kB
bc590ea01db6: Loading layer [==================================================>]  329.2MB/329.2MB
7832e3c2cdb4: Loading layer [==================================================>]  216.9MB/216.9MB
4244d4f08dca: Loading layer [==================================================>]  881.4MB/881.4MB
539fab142321: Loading layer [==================================================>]  6.656kB/6.656kB
Loaded image: checkmk/check-mk-enterprise:2.1.0p11-rc2

1 Like

@paulr282 with 2.1.0p11 we introduced a release candidate process for the 2.1.0 branch. So it simply means, this image is based on the 2.1.0p11-rc2 tag (which corresponds to the 2.1.0p11 tag).
Anyway - you received the 2.1.0p11 with that image :slight_smile:
Thanks for reporting, we will clean that up!


@paulr282 just a heads-up, this issue is cleanup with 2.1.0p15

1 Like