Sticky/stubborn ruleset from prototype check

Troubleshooting
,
1

CMK version: 2.3.0p29
OS version: Ubuntu 22.04.5 LTS

Error message: check_mk: Found configured rules of deprecated check group “custom_ruleset_name”. These rules are not used by any check plug-in. Maybe this check group has been renamed during an update,

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

This was initially caused by accidentally removing the custom ruleset file before removing all the rules created with it. I’ve repeatedly sanitized and checked the ~/etc/check_mk/conf.d/wato/rules.mk file, and the .mk files in the directories associated with my host folders – up to and including completely removing the rules.mk files and manually rebuilding the rules I’ve set up. This ruleset and associated check were not part of a package, as this was an in-development custom check. Any ideas on how to get rid of this? This error is disabling the new versions of the ruleset that apply, so I can’t really develop it any further.

1 Like
2

Did you try reenabling the custom ruleset or adding a new one with the same name?

3

I did try that. I even tried adding a copy of the ruleset in question to the directory for a different check plugin, and the error persisted.

4

It seems that you are playing with production environment. I won’t be able to solve your issue but I will provide a recommendation based in a similar issue that I faced:

  • Create a new checkmk site with the same version in a Virtual Machine.

  • Add the same extension, create a rule and then remove it in the same way that you did but this time evaluate the behavior change in mk files. The idea here is to generate the same issue in a controlled environment.

  • After doing changes you can run a file search for recently modified files to identify was else was changed during the inclusion of the new rules besides the mk files that you changed.

Sorry if I was not helpful. Please let us know if you were able to solve the issue or found any other piece of information that you seem useful.

Just another thing to check, were you able to delete this host, apply changes and then create it again?

5

Nah, this is a lab VM specifically set up for tinkering like this – no production servers were harmed in the attempt. I haven’t tried removing/re-adding the host yet, that’s a good check! Push comes to shove I’ll take you up on the fresh/minimal server and site route.

1 Like