OMD status: defective installation

After restoring my Checkmk site from Debian 12 to a new Debian 13 server using omd backup and omd restore, the site shows “defective installation” in the OMD status check. All site services are running correctly and omd status reports everything OK. The Checkmk version is 2.4.0p21 on both systems and editions match. Running omd update shows no available updates. Permissions and symlinks were checked and seem correct. However, the problem remains and no clear error message is shown.

OMD mysite status  defective installation
$ omd status --bare --auto
agent-receiver 0
mkeventd 0
rrdcached 0
redis 0
npcd 0
automation-helper 0
ui-job-scheduler 0
nagios 0
apache 0
crontab 0
OVERALL 0

**CMK version: **
$ cmk --version
This is Check_MK version 2.4.0p21 CRE

OS version: Debian 13

Error message: OMD mysite status defective installation


OMD[mysite]:~$ cmk --debug -vvn $(hostname)
value store: loading from disk
Checkmk version 2.4.0p21
+ FETCHING DATA
  Source: SourceInfo(hostname='mon-01.example.local', ipaddress='10.0.0.10', ident='agent', fetcher_type=<FetcherType.TCP: 8>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7ff286ff9610]
Read from cache: AgentFileCache(path_template=/omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local, max_age=MaxAge(checking=0, discovery=90.0, inventory=90.0), simulation=False, use_only_cache=False, file_cache_mode=6)
Not using cache (Too old. Age is 54 sec, allowed is 0 sec)
Connecting via TCP to 10.0.0.10:6556 (5.0s timeout)
Detected transport protocol: TransportProtocol.TLS
Reading data from agent via TLS socket
Reading data from agent
Detected transport protocol: TransportProtocol.PLAIN
Closing TCP connection to 10.0.0.10:6556
Write data to cache file /omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local
Trying to acquire lock on /omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local
Got lock on /omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local
Releasing lock on /omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local
Released lock on /omd/sites/mysite/tmp/check_mk/cache/mon-01.example.local
[cpu_tracking] Stop [7ff286ff9610 - Snapshot(process=posix.times_result(user=0.010000000000000009, system=0.0, children_user=0.0, children_system=0.0, elapsed=2.25))]
  Source: SourceInfo(hostname='mon-01.example.local', ipaddress='10.0.0.10', ident='piggyback', fetcher_type=<FetcherType.PIGGYBACK: 4>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7ff286fd25a0]
Read from cache: NoCache(path_template=/dev/null, max_age=MaxAge(checking=0.0, discovery=0.0, inventory=0.0), simulation=False, use_only_cache=False, file_cache_mode=1)
0 piggyback files for 'mon-01.example.local'.
0 piggyback files for '10.0.0.10'.
Get piggybacked data
[cpu_tracking] Stop [7ff286fd25a0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
[cpu_tracking] Start [7ff287372390]
+ PARSE FETCHER RESULTS
<<<check_mk>>> / Transition NOOPParser -> HostSectionParser
<<<cmk_agent_ctl_status:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<checkmk_agent_plugins_lnx:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<labels:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<df_v2>>> / Transition HostSectionParser -> HostSectionParser
<<<df_v2>>> / Transition HostSectionParser -> HostSectionParser
<<<systemd_units>>> / Transition HostSectionParser -> HostSectionParser
<<<nfsmounts_v2:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<cifsmounts>>> / Transition HostSectionParser -> HostSectionParser
<<<mounts>>> / Transition HostSectionParser -> HostSectionParser
<<<ps_lnx>>> / Transition HostSectionParser -> HostSectionParser
<<<mem>>> / Transition HostSectionParser -> HostSectionParser
<<<cpu>>> / Transition HostSectionParser -> HostSectionParser
<<<uptime>>> / Transition HostSectionParser -> HostSectionParser
<<<lnx_if>>> / Transition HostSectionParser -> HostSectionParser
<<<lnx_if:sep(58)>>> / Transition HostSectionParser -> HostSectionParser
<<<tcp_conn_stats>>> / Transition HostSectionParser -> HostSectionParser
<<<diskstat>>> / Transition HostSectionParser -> HostSectionParser
<<<kernel>>> / Transition HostSectionParser -> HostSectionParser
<<<md>>> / Transition HostSectionParser -> HostSectionParser
<<<vbox_guest>>> / Transition HostSectionParser -> HostSectionParser
<<<postfix_mailq>>> / Transition HostSectionParser -> HostSectionParser
<<<postfix_mailq_status:sep(58)>>> / Transition HostSectionParser -> HostSectionParser
<<<fileinfo:sep(124)>>> / Transition HostSectionParser -> HostSectionParser
<<<livestatus_status:sep(59)>>> / Transition HostSectionParser -> HostSectionParser
<<<livestatus_ssl_certs:sep(124)>>> / Transition HostSectionParser -> HostSectionParser
<<<mkeventd_status:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<cmk_site_statistics:sep(59)>>> / Transition HostSectionParser -> HostSectionParser
<<<job>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_status:cached(1772494701,60)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_apache:sep(124)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_diskusage:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_broker_status:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_broker_queues:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_broker_shovels:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<omd_info:sep(59)>>> / Transition HostSectionParser -> HostSectionParser
<<<timesyncd>>> / Transition HostSectionParser -> HostSectionParser
<<<timesyncd_ntpmessage:sep(10)>>> / Transition HostSectionParser -> HostSectionParser
<<<local:sep(0)>>> / Transition HostSectionParser -> HostSectionParser
<<<logwatch>>> / Transition HostSectionParser -> HostSectionParser
  HostKey(hostname='mon-01.example.local', source_type=<SourceType.HOST: 1>)  -> Add sections: ['check_mk', 'checkmk_agent_plugins_lnx', 'cifsmounts', 'cmk_agent_ctl_status', 'cmk_site_statistics', 'cpu', 'df_v2', 'diskstat', 'fileinfo', 'job', 'kernel', 'labels', 'livestatus_ssl_certs', 'livestatus_status', 'lnx_if', 'local', 'logwatch', 'md', 'mem', 'mkeventd_status', 'mounts', 'nfsmounts_v2', 'omd_apache', 'omd_broker_queues', 'omd_broker_shovels', 'omd_broker_status', 'omd_diskusage', 'omd_info', 'omd_status', 'postfix_mailq', 'postfix_mailq_status', 'ps_lnx', 'systemd_units', 'tcp_conn_stats', 'timesyncd', 'timesyncd_ntpmessage', 'uptime', 'vbox_guest']
  HostKey(hostname='mon-01.example.local', source_type=<SourceType.HOST: 1>)  -> Add sections: []
Received no piggyback data
ACCOUNT_FAILED_LOGINS no failed logins found
CPU load             15 min load: 1.72, 15 min load per core: 0.43 (4 cores)
CPU utilization      Total CPU: 28.96%
Check_MK Agent       Version: 2.4.0p21, OS: linux, Agent plug-ins: 1, Local checks: 3
Disk IO SUMMARY      Read: 809 kB/s, Write: 2.26 MB/s, Latency: 51 microseconds
FIREWALL             firewall up and running
File /var/log/lynis-output.log Size: 0 B, Age: 26 minutes 6 seconds
File /var/log/lynis.log Size: 0 B, Age: 26 minutes 6 seconds
Filesystem /         Used: 53.32% - 5.57 GiB of 10.4 GiB, trend per 1 day 0 hours: +99.8 MiB, trend per 1 day 0 hours: +0.93%, Time left until disk full: 49 days 23 hours
Filesystem /boot     Used: 13.53% - 127 MiB of 942 MiB, trend per 1 day 0 hours: +0 B, trend per 1 day 0 hours: +0%
Filesystem /home     Used: 6.41% - 28.7 MiB of 447 MiB, trend per 1 day 0 hours: +460 B, trend per 1 day 0 hours: +<0.01%
Filesystem /opt/omd  Used: 79.63% - 7.76 GiB of 9.75 GiB, trend per 1 day 0 hours: +51.7 MiB, trend per 1 day 0 hours: +0.52%, Time left until disk full: 39 days 7 hours
Filesystem /var      Used: 37.66% - 24.0 GiB of 63.9 GiB, trend per 1 day 0 hours: +241 MiB, trend per 1 day 0 hours: +0.37%, Time left until disk full: 168 days 21 hours
Filesystem /var/log  Used: 26.28% - 746 MiB of 2.77 GiB, trend per 1 day 0 hours: -9.48 MiB, trend per 1 day 0 hours: -0.33%
Interface 2          [ens18], (up), MAC: 00:11:22:33:44:55, Speed: unknown, In: 90.0 kB/s, Out: 98.4 kB/s
Interface 3          [docker0], (up), MAC: 00:11:22:33:44:56, Speed: 10 GBit/s, In: 4.55 kB/s (<0.01%), Out: 42.2 kB/s (<0.01%)
Kernel Performance   Process Creations: 29.93/s, Context Switches: 9814.23/s, Major Page Faults: 33.61/s, Page Swap in: 0.00/s, Page Swap Out: 0.00/s
Log /var/log/auth.log 35 WARN messages (Last worst: "2026-03-02T22:16:25.683808+01:00 mon-01 sudo: mysite : user NOT in sudoers ; TTY=pts/4 ; PWD=/opt/omd/sites/mysite ; USER=mysite ; COMMAND=/omd/versions/2.4.0p21.cre/bin/cmk-monitor-otel-collector")
Log /var/log/lynis-output.log No error messages
Log /var/log/lynis.log No error messages
Log /var/log/mail.err No error messages
Log /var/log/mail.warn No error messages
Log /var/log/pkgcheck/pkgcheck.log 4 WARN messages (Last worst: "2026-03-02 02:02:11,112 - WARNING - Found 144 unauthorized packages:")
Log /var/log/syslog  No error messages
Log /var/log/telegraf/telegraf.log No error messages
Log /var/mail/root   543 WARN messages (Last worst: "mon-01.example.local : Mar 2 22:16:25 : mysite : user NOT in sudoers ; TTY=pts/4 ; PWD=/opt/omd/sites/mysite ; USER=mysite ; COMMAND=/omd/versions/2.4.0p21.cre/bin/cmk-monitor-otel-collector")
Memory               Total virtual memory: 66.97% - 7.83 GiB of 11.7 GiB, Committed: 148.24% - 17.3 GiB of 11.7 GiB virtual memory (warn/crit at 100.00%/150.00% used)(!), 7 additional details available
Mount options of /   Mount options exactly as expected
Mount options of /boot Mount options exactly as expected
Mount options of /home Mount options exactly as expected
Mount options of /opt/omd Mount options exactly as expected
Mount options of /var Mount options exactly as expected
Mount options of /var/log Mount options exactly as expected
Number of threads    1262, Usage: 1.32%
OMD mysite Event Console Current events: 1013, Virtual memory: 223 MiB, Overall event limit inactive, No hosts event limit active, Event limit active for 1 rules (telegraf-other-failures)(!), Received messages: 0.00/s, Rule hits: 0.00/s, Rule tries: 0.00/s, Message drops: 0.00/s, Created events: 0.00/s, Client connects: 0.07/s, Rule hit ratio: -, Processing time per message: -, Time per client request: 13.92 ms
OMD mysite apache  Requests: 0.02/s, Seconds serving: 0.00/s, Sent: 97.4 B/s
OMD mysite disk usage Total: 6.14 GiB, Agents: 0 B, Core: 1.51 MiB, History: 24.0 KiB, Inventory: 122 KiB, Local: 3.26 KiB, Logs: 5.50 MiB, OTel: 0 B, PNP4Nagios: 2.78 GiB, RRDs: 0 B, Tmp: 213 MiB
OMD mysite performance Livestatus version: 2.4.0p21, Host checks: 0.3/s, Service checks: 27.5/s
OMD mysite status  defective installation
Postfix Queue default Deferred queue length: 0, Active queue length: 0
Postfix status default Status: the Postfix mail system is running, PID: 1022
Process influxdb     Processes: 1, Virtual memory: 21.8 GiB, Resident memory: 4.27 GiB, CPU: 1.32%, Running for: 5 days 4 hours
Process nginx        Processes: 4, Virtual memory: 117 MiB, Resident memory: 49.9 MiB, CPU: 1.75%, Running for: 5 days 4 hours
Process rsyslog      Processes: 1, Virtual memory: 370 MiB, Resident memory: 11.4 MiB, CPU: 0.44%, Running for: 26 minutes 4 seconds
Process mysite agent receiver Processes: 2, Virtual memory: 120 MiB, Resident memory: 87.5 MiB, CPU: 0%, Running for: 2 hours 20 minutes
Process mysite apache Processes: 5, Virtual memory: 1.01 GiB, Resident memory: 690 MiB, CPU: 0.44%, Youngest running for: 2 hours 18 minutes, Oldest running for: 2 hours 20 minutes
Process mysite automation helpers Processes: 3, Virtual memory: 2.83 GiB, Resident memory: 419 MiB, CPU: 0%, Running for: 2 hours 20 minutes
Process mysite event console Processes: 1, Virtual memory: 223 MiB, Resident memory: 58.3 MiB, CPU: 0%, Running for: 2 hours 20 minutes
Process mysite redis-server Processes: 1, Virtual memory: 153 MiB, Resident memory: 14.4 MiB, CPU: 0%, Running for: 2 hours 20 minutes
Process mysite rrdcached Processes: 1, Virtual memory: 544 MiB, Resident memory: 31.1 MiB, CPU: 0.44%, Running for: 2 hours 20 minutes
Process telegraf     Processes: 1, Virtual memory: 5.45 GiB, Resident memory: 69.7 MiB, CPU: 0%, Running for: 5 days 3 hours
Process wazuh-agentd Processes: 1, Virtual memory: 244 MiB, Resident memory: 5.25 MiB, CPU: 0%, Running for: 5 days 1 hour
Process wazuh-execd  Processes: 1, Virtual memory: 26.5 MiB, Resident memory: 2.86 MiB, CPU: 0%, Running for: 5 days 1 hour
Process wazuh-logcollector Processes: 1, Virtual memory: 130 MiB, Resident memory: 3.18 MiB, CPU: 0%, Running for: 5 days 1 hour
Process wazuh-modulesd Processes: 1, Virtual memory: 485 MiB, Resident memory: 4.17 MiB, CPU: 0%, Running for: 5 days 1 hour
Process wazuh-syscheckd Processes: 1, Virtual memory: 146 MiB, Resident memory: 4.30 MiB, CPU: 0%, Running for: 5 days 1 hour
Proxmox VE Memory Usage PEND Check plug-in received no monitoring data
Proxmox VE VM Info   PEND Check plug-in received no monitoring data
Proxmox VE VM Snapshot age PEND Check plug-in received no monitoring data
ROOTSH               rootsh script was modified (2026-02-25 15:21:22.661186218 +0100)! If the change was done on purpose, please acknowledge the check result for seven day.
Site mysite statistics Total hosts: 25, Problem hosts: 2, Total services: 1308, Problem services: 197
Systemd Service Summary Total: 157, Disabled: 5, Failed: 0
Systemd Socket Summary Total: 22, Disabled: 4, Failed: 0
Systemd Timesyncd Time Offset: 41 milliseconds, Time since last sync: 12 minutes 36 seconds, Time since last NTPMessage: 12 minutes 36 seconds, Stratum: 3.00, Jitter: 21 milliseconds, Synchronized on 10.0.0.1
TCP Connections      Established: 95
Uptime               Up since 2026-02-25 20:15:01, Uptime: 5 days 4 hours
+ EXECUTING INVENTORY PLUGINS
 cisco_meraki_power_supplies: skipped (no data)
 cisco_meraki_power_supplies: skipped (no data)
 cisco_meraki_org_device_info: skipped (no data)
 cisco_meraki_org_device_info: skipped (no data)
 suseconnect: skipped (no data)
 suseconnect: skipped (no data)
 checkpoint_vpn_tunnels: skipped (no data)
 checkpoint_vpn_tunnels: skipped (no data)
 infoblox_systeminfo: skipped (no data)
 infoblox_systeminfo: skipped (no data)
 win_os: skipped (no data)
 win_os: skipped (no data)
 kube_deployment: skipped (no data)
 kube_deployment: skipped (no data)
 perle_chassis_slots: skipped (no data)
 perle_chassis_slots: skipped (no data)
 inv_esx_vsphere_hostsystem: skipped (no data)
 inv_esx_vsphere_hostsystem: skipped (no data)
 lnx_cpuinfo: skipped (no data)
 lnx_cpuinfo: skipped (no data)
 ibm_mq_queues: skipped (no data)
 ibm_mq_queues: skipped (no data)
 fortisandbox_software: skipped (no data)
 fortisandbox_software: skipped (no data)
 solaris_pkginfo: skipped (no data)
 solaris_pkginfo: skipped (no data)
 couchbase_nodes_ports: skipped (no data)
 couchbase_nodes_ports: skipped (no data)
 citrix_controller: skipped (no data)
 citrix_controller: skipped (no data)
 kube_pod: skipped (no data)
 kube_pod: skipped (no data)
 kube_namespace: skipped (no data)
 kube_namespace: skipped (no data)
 checkmk_agent_plugins: ok
 checkmk_agent_plugins: skipped (no data)
 docker_node_images: skipped (no data)
 docker_node_images: skipped (no data)
 solaris_cpus: skipped (no data)
 solaris_cpus: skipped (no data)
 primekey: skipped (no data)
 primekey: skipped (no data)
 ipmi_firmware: skipped (no data)
 ipmi_firmware: skipped (no data)
 docker_container_labels: skipped (no data)
 docker_container_labels: skipped (no data)
 win_wmi_updates: skipped (no data)
 win_wmi_updates: skipped (no data)
 lnx_packages: skipped (no data)
 lnx_packages: skipped (no data)
 mem: ok
 mem: skipped (no data)
 fortiauthenticator_system: skipped (no data)
 fortiauthenticator_system: skipped (no data)
 win_ip_r: skipped (no data)
 win_ip_r: skipped (no data)
 lnx_sysctl: skipped (no data)
 lnx_sysctl: skipped (no data)
 aix_packages: skipped (no data)
 aix_packages: skipped (no data)
 fireeye_sys_status: skipped (no data)
 fireeye_sys_status: skipped (no data)
 mobileiron_inventory: skipped (no data)
 mobileiron_inventory: skipped (no data)
 docker_container_network: skipped (no data)
 docker_container_network: skipped (no data)
 hp_proliant_systeminfo: skipped (no data)
 hp_proliant_systeminfo: skipped (no data)
 lnx_uname: skipped (no data)
 lnx_uname: skipped (no data)
 docker_node_network: skipped (no data)
 docker_node_network: skipped (no data)
 lnx_ip_r: skipped (no data)
 lnx_ip_r: skipped (no data)
 oracle_systemparameter: skipped (no data)
 oracle_systemparameter: skipped (no data)
 inventory_esx_vsphere_virtual_machines: skipped (no data)
 inventory_esx_vsphere_virtual_machines: skipped (no data)
 solaris_prtdiag: skipped (no data)
 solaris_prtdiag: skipped (no data)
 win_cpuinfo: skipped (no data)
 win_cpuinfo: skipped (no data)
 inventory_docker_container_node_name: skipped (no data)
 inventory_docker_container_node_name: skipped (no data)
 inv_cisco_vlans: skipped (no data)
 inv_cisco_vlans: skipped (no data)
 infoblox_osinfo: skipped (no data)
 infoblox_osinfo: skipped (no data)
 kube_node: skipped (no data)
 kube_node: skipped (no data)
 fortisandbox_system: skipped (no data)
 fortisandbox_system: skipped (no data)
 win_reg_uninstall: skipped (no data)
 win_reg_uninstall: skipped (no data)
 win_disks: skipped (no data)
 win_disks: skipped (no data)
 perle_chassis: skipped (no data)
 perle_chassis: skipped (no data)
 win_bios: skipped (no data)
 win_bios: skipped (no data)
 aix_service_packs: skipped (no data)
 aix_service_packs: skipped (no data)
 enviromux_micro_information: skipped (no data)
 enviromux_micro_information: skipped (no data)
 lnx_distro: skipped (no data)
 lnx_distro: skipped (no data)
 dmidecode: skipped (no data)
 dmidecode: skipped (no data)
 kube_statefulset: skipped (no data)
 kube_statefulset: skipped (no data)
 solaris_addresses: skipped (no data)
 solaris_addresses: skipped (no data)
 winperf_if: skipped (no data)
 winperf_if: skipped (no data)
 fortigate_ha: skipped (no data)
 fortigate_ha: skipped (no data)
 dell_hw_info: skipped (no data)
 dell_hw_info: skipped (no data)
 kube_daemonset: skipped (no data)
 kube_daemonset: skipped (no data)
 win_system: skipped (no data)
 win_system: skipped (no data)
 kube_cronjob: skipped (no data)
 kube_cronjob: skipped (no data)
 ibm_mq_managers: skipped (no data)
 ibm_mq_managers: skipped (no data)
 perle_psmu: skipped (no data)
 perle_psmu: skipped (no data)
 aruba_wlc_aps: skipped (no data)
 aruba_wlc_aps: skipped (no data)
 fortinet_firewall_network_interfaces: skipped (no data)
 fortinet_firewall_network_interfaces: skipped (no data)
 fortimail_system: skipped (no data)
 fortimail_system: skipped (no data)
 check_mk: ok
 check_mk: skipped (no data)
 ibm_mq_channels: skipped (no data)
 ibm_mq_channels: skipped (no data)
 inventory_esx_vsphere_clusters: skipped (no data)
 inventory_esx_vsphere_clusters: skipped (no data)
 mem_used: skipped (no data)
 mem_used: skipped (no data)
 snmp_quantum_storage_info: skipped (no data)
 snmp_quantum_storage_info: skipped (no data)
 win_exefiles: skipped (no data)
 win_exefiles: skipped (no data)
 lnx_video: skipped (no data)
 lnx_video: skipped (no data)
 win_wmi_software: skipped (no data)
 win_wmi_software: skipped (no data)
 win_computersystemproduct: skipped (no data)
 win_computersystemproduct: skipped (no data)
 lnx_if: ok
 lnx_if: skipped (no data)
 juniper_info: skipped (no data)
 juniper_info: skipped (no data)
 docker_node_info: skipped (no data)
 docker_node_info: skipped (no data)
 inv_if: ok
 inv_if: skipped (no data)
 inventory_checkmk: ok
 inventory_checkmk: skipped (no data)
 citrix_state: skipped (no data)
 citrix_state: skipped (no data)
 aix_baselevel: skipped (no data)
 aix_baselevel: skipped (no data)
 aix_lparstat_inventory: skipped (no data)
 aix_lparstat_inventory: skipped (no data)
 prtconf: skipped (no data)
 prtconf: skipped (no data)
 win_computersystem: skipped (no data)
 win_computersystem: skipped (no data)
 allnet_ip_sensoric: skipped (no data)
 allnet_ip_sensoric: skipped (no data)
 kube_cluster: skipped (no data)
 kube_cluster: skipped (no data)
 lparstat_aix: skipped (no data)
 lparstat_aix: skipped (no data)
 hp_proliant_mem: skipped (no data)
 hp_proliant_mem: skipped (no data)
 win_video: skipped (no data)
 win_video: skipped (no data)
 mssql_clusters: skipped (no data)
 mssql_clusters: skipped (no data)
 lnx_block_devices: skipped (no data)
 lnx_block_devices: skipped (no data)
 kyocera_printer: skipped (no data)
 kyocera_printer: skipped (no data)
 solaris_uname: skipped (no data)
 solaris_uname: skipped (no data)
 snmp_extended_info: skipped (no data)
 snmp_extended_info: skipped (no data)
 solaris_routes: skipped (no data)
 solaris_routes: skipped (no data)
 snmp_info: skipped (no data)
 snmp_info: skipped (no data)
 win_networkadapter: skipped (no data)
 win_networkadapter: skipped (no data)
 azure_load_balancer: skipped (no data)
 azure_load_balancer: skipped (no data)
 hp_proliant_da_phydrv: skipped (no data)
 hp_proliant_da_phydrv: skipped (no data)
 mssql_instance: skipped (no data)
 mssql_instance: skipped (no data)
 oracle_instance: skipped (no data)
 oracle_instance: skipped (no data)
 oracle_tablespaces: skipped (no data)
 oracle_tablespaces: skipped (no data)
 oracle_recovery_area: skipped (no data)
 oracle_recovery_area: skipped (no data)
 oracle_dataguard_stats: skipped (no data)
 oracle_dataguard_stats: skipped (no data)
 oracle_performance: skipped (no data)
 oracle_performance: skipped (no data)
 esx_systeminfo: skipped (no data)
 esx_systeminfo: skipped (no data)
 netapp_ontap_info: skipped (no data)
 netapp_ontap_info: skipped (no data)
 netapp_ontap_disk: skipped (no data)
 netapp_ontap_disk: skipped (no data)
 fritz: skipped (no data)
 fritz: skipped (no data)
 redfish_firmware: skipped (no data)
 redfish_firmware: skipped (no data)
 redfish_firmware_hpe_ilo4: skipped (no data)
 redfish_firmware_hpe_ilo4: skipped (no data)
Trying to acquire lock on /omd/sites/mysite/tmp/check_mk/status_data/mon-01.example.local
Got lock on /omd/sites/mysite/tmp/check_mk/status_data/mon-01.example.local
Releasing lock on /omd/sites/mysite/tmp/check_mk/status_data/mon-01.example.local
Released lock on /omd/sites/mysite/tmp/check_mk/status_data/mon-01.example.local
0 piggyback files for 'mon-01.example.local'.
[cpu_tracking] Stop [7ff287372390 - Snapshot(process=posix.times_result(user=0.04999999999999982, system=0.010000000000000009, children_user=0.0, children_system=0.0, elapsed=0.06000000238418579))]
[agent] Success, [piggyback] Success (but no data found for this host), Missing monitoring data for plugins, proxmox_ve_mem_usage(!), proxmox_ve_vm_info(!), proxmox_ve_vm_snapshot_age(!), execution time 2.3 sec | execution_time=2.310 user_time=0.060 system_time=0.010 children_user_time=0.000 children_system_time=0.000 cmk_time_agent=2.240

so check this as site user

# 1. Status test
omd status

# 2. Python-Version & Path test
python3 --version
which python3
ls -l $(which python3)

# 3. Site-Python test
~/bin/python3 --version
~/bin/python3 -c "import sys; print(sys.executable); print(sys.path)"

# 4. looking for error messages
omd status apache
tail -n 50 ~/var/log/web.log | grep -i error
tail -n 50 ~/var/log/cmc.log

# 5. clear tmp
omd stop 
rm -rf ~/tmp/*
omd start

Hello Bernd, Thank you for your reply. I executed the recommended commands and compared the results with a server that does not show the defective installation error; the outputs are identical. I also reviewed the logs and did not find any configuration-related issues. Additionally, I cleaned up the /tmp folder and restarted the service.

At this point, I’m unable to determine the source of the defective installation event, as there is no relevant information in the logs.

omd status
agent-receiver:     running
mkeventd:           running
rrdcached:          running
redis:              running
npcd:               running
automation-helper:  running
ui-job-scheduler:   running
nagios:             running
apache:             running
crontab:            running
---------------------------
Overall state:      running

Hi, I can’t find a solution for this. When I check the omd_status.cache file, I find empty values for the service status. However, on another server, I can see the OK status for omd_status, and the file is populated with the service status.

cat /var/lib/check_mk_agent/cache/omd_status.cache
<<<omd_status>>>
[mysite]

When I run check_mk_agent | grep -A20 omd_status, I also get empty values.

<<<omd_status:cached(1772595420,60)>>>
[mysite]

Which permissions might not be properly configured? The logs only show this:

var/log/nagios.log:[1772584559] Warning: Check result queue contained results for service 'Unimplemented check omd_status / mysite' on host 'mon-01.example.local', but the service could not be found!  Perhaps you forgot to define the service in your config files?


no im running out of options from far …

sorry … behaps other ideas will comming up

so check this:

sudo omd status --bare - perhaps a permission issue so the test as sudo or root

Debian 13 (Trixie) comes with stricter security settings. Check:

# check omd has the rigth permissions
ls -la /omd/versions/2.4.0p21.cre/bin/omd
ls -la /usr/bin/omd

# omd should suid-root:
# -rwsr-xr-x 1 root root ... /usr/bin/omd
# if the 's'-Bit is missing:
chmod u+s /usr/bin/omd

latest idea is to reinstall the agent

I assigned the +s bit to /usr/bin/omd but the problem persists.

Just for the record: I have another server where the omd_status check is working properly, and /usr/bin/omd does NOT have the SUID bit set on that server.

Further investigation shows that the omd_status section is built directly into the check_mk_agent script (line 1230), not delivered as a plugin. The relevant line is:

_run_cached_internal "omd_status" 60 60 180 120 "echo '<<<omd_status>>>'; ${ROOT_OR_SUDO} omd status --bare || true"

This line is identical on both servers. The cache file /var/lib/check_mk_agent/cache/omd_status.cache is populated correctly on the working server but remains empty on the broken one, suggesting that ${ROOT_OR_SUDO} is unable to execute ‘omd status --bare’ with sufficient privileges on the restored server.

Any idea what could cause this privilege resolution difference between the two servers?

1 Like

Great debugging work — you’ve narrowed it down perfectly. The key is how ${ROOT_OR_SUDO} gets set in the agent script. Look at the init_sudo() function near the top of the agent:

agent_linux

Line 40-47

init_sudo() {
    if inpath sudo && [ "$(whoami)" != "root" ]; then
        ROOT_OR_SUDO="sudo --non-interactive"
    else
        ROOT_OR_SUDO=""
    fi
}

This means:

  • If the agent runs as rootROOT_OR_SUDO is empty, omd status --bare runs directly as root — works.
  • If the agent runs as non-rootROOT_OR_SUDO becomes sudo --non-interactive, which requires a proper sudoers configuration.

Please check the following on both servers (working and broken):

bash

# 1. Who is actually running the agent?
ps aux | grep check_mk_agent

# 2. Check the systemd unit for the agent controller:
systemctl cat cmk-agent-ctl-daemon.service

# 3. Check if the agent is configured for non-root deployment:
cat /etc/systemd/system/cmk-agent-ctl-daemon.service | grep User

# 4. On the broken server, test as the agent user:
sudo -u <agent_user> /usr/bin/check_mk_agent 2>/dev/null | grep -A 20 "omd_status"

# 5. Check if a sudoers template was deployed:
ls -la /etc/sudoers.d/ | grep -i cmk
cat /etc/sudoers.d/checkmk_agent 2>/dev/null || echo "No sudoers file found"

# 6. Check the sudoers template that came with the agent:
cat /opt/checkmk/agent/default/package/agent/checkmk_agent_sudoers_template 2>/dev/null

My suspicion: After the omd backup/restore migration to Debian 13, the agent might be running as a non-root user (which is a feature since Checkmk 2.4 — see Werk #17901), but the sudoers configuration was not restored or is missing on the new server. On the working server, either the agent still runs as root, or the sudoers file is correctly in place.

Quick fix to test the theory:

bash

# Check if agent runs as root:
ps aux | grep "[c]heck_mk_agent"

# If it does NOT run as root, copy the sudoers template:
cp /opt/checkmk/agent/default/package/agent/checkmk_agent_sudoers_template /etc/sudoers.d/checkmk_agent
chmod 440 /etc/sudoers.d/checkmk_agent
visudo -c  # validate syntax

# Then clear the cache and test:
rm -f /var/lib/check_mk_agent/cache/omd_status.cache
check_mk_agent | grep -A 20 "omd_status"

If the agent does run as root and the cache is still empty, the problem might be something else entirely — for example, a waitmax timeout (the cached command has a 120-second timeout). In that case, try running the command directly as root and check if it hangs:

bash

time omd status --bare

so let`s check :partying_face: before getting crazy :sweat_smile:

Issue resolved. I had NoNewPrivileges set to true in /etc/systemd/system/check-mk-agent-async.service.d/security.conf for hardening purposes. This systemd hardening feature silently prevents subprocesses from elevating privileges even when running as root, which caused omd status --bare to return empty output when called from the agent. Setting it to false fixed the issue.

Note: this problem only appears on Debian 13, the same configuration with NoNewPrivileges=true works fine on Debian 12 with the same Checkmk version.

1 Like

hopefully not in my environment … still on Debian 12 :sweat_smile:

1 Like

Hi @dorancemc

If one of the answers helped you solve your question, please mark it as the solution. This way, you thank the person who helped you and also indicate that the question has been resolved. This, in turn, helps others who come across the same question.

Greetz

Thank you Bernd for your help. I now have a better understanding of how Checkmk and the agent work internally.

1 Like