High cpu usage due to mknotifyd

CMK version:
2.2.0p24.cme

OS version:
Debian12

Error message:
CPU utilization: Total CPU (55 min average): 135.63% (warn/crit at 85.00%/95.00%)

The CPU usage on one of our satellite containers is constantly high. Already added 2 cpu’s and tried killing the process that is causing this.
The process that is constantly displaying high cpu is mknotifyd.

root@:~# ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%cpu | head
    PID    PPID CMD                         %MEM %CPU
   1069    671  python3 /omd/sites//b       1.3  66.4

The process is referring to /omd/sites//bin/mknotifyd.
The pid refers to the following path: /opt/omd/versions/2.2.0p24.cme/bin/python3.11*

I have checked the mknotifyd logfiles and they are empty.
I’ve also killed the mknotifyd process, but as it automatically restarts the cpu usage peaks again.

OMD[]:~$ omd config show
ADMIN_MAIL:
AGENT_RECEIVER: on
AGENT_RECEIVER_PORT: 8000
APACHE_MODE: own
APACHE_TCP_ADDR: 0.0.0.0
APACHE_TCP_PORT: 5000
AUTOSTART: on
CORE: cmc
LIVEPROXYD: on
LIVESTATUS_TCP: on
LIVESTATUS_TCP_ONLY_FROM: 0.0.0.0 ::/0
LIVESTATUS_TCP_PORT: 6557
LIVESTATUS_TCP_TLS: on
MKEVENTD: on
MKEVENTD_SNMPTRAP: off
MKEVENTD_SYSLOG: off
MKEVENTD_SYSLOG_TCP: off
MULTISITE_AUTHORISATION: on
MULTISITE_COOKIE_AUTH: on
TMPFS: off
top - 16:49:09 up 1 day,  5:15,  0 users,  load average: 1.69, 1.73, 1.55
Tasks:  73 total,   2 running,  71 sleeping,   0 stopped,   0 zombie
%Cpu(s): 40.0 us, 14.9 sy,  0.0 ni, 43.1 id,  0.2 wa,  0.0 hi,  1.9 si,  0.0 st
MiB Mem :   3914.8 total,    239.2 free,   2390.0 used,   1285.6 buff/cache
MiB Swap:    980.0 total,    809.7 free,    170.3 used.   1233.3 avail Mem

Any ideas on how to help this?

Just a longshot, but this could be malformed syslog input to the event console. Can you stop all syslog being send to the event console? Also, you might be able to find the corrupt data in $OMD_ROOT/var/mkeventd/. Furthermore, update to the latest 2.2.0 release at least, just in case.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.