Duplicated Service Names

CMK version:2.1.0p30
OS version:Ubuntu 22.04.2 LTS

Error message:WARNING: ERROR: Duplicate service description (auto check) ‘XXX’ for host ‘YYY’!

Hi,
i’ve got a problem with two monitored Linux VMs.
The plugins mem_linux / mem_used and cpu_utilization_os / kernel_util are using the same service names.
I’ve put alot efford in trying to find a way in changing/rewriting the service name of either of them but no luck.
Aside from that, i don’t understand why this is occuring only on these two hosts although there are many other linux hosts with exactly the same host settings.

Any suggestions?

It looks like you monitor this host with agent and SNMP.
Please switch of the SNMP and only use the agent. Then rediscover the services and the duplicate entries should be gone.

SNMP is not checked in host settings.
Was my first guess too but unfortunately that’s not the case.
Like i mentioned, i’ve got a bunch of other linux-hosts with exactly the same settings (except hostname of course) and even labels, so the same rules and plugins apply to them too.
The hosts all run the same OS (even version and patchlevel) and even the same Agent.
I really don’t get why there are those additional plugins active on those two hosts.

cpu_utilization_os i get only for “simple” devices like containers.
The same for mem_used only on containers and SNMP devices.

Is it possible that you have a container with the same name as this host inside your environment? Then you will see the piggyback data from this container on your host.

1 Like

Well, that helped alot!
Turns out the docker-plugin sent the cpu and memory usage from these two hosts as piggiback data.
I don’t really understand why this applys only to this two hosts yet (or docker containers) but disabling cpu- and memory usage in the docker-plugin on affected hosts by rule (or simply disabling it at all in the docker-plugin) solved the problem.

Thanks alot Andreas!

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.