Upgrade cmk raw 1.6.0p11 to cmk raw 2.0.0p3 problem

Hi, after an update from cmk raw 1.6.0p11 to cmk raw 2.0.0p3, we got an error on all hosts, for service check_mk we got a critical error NULL (for all hosts but other hosts services checks works just fine). And if we make any change, we can not apply it because of an error. So when we do update from 1.6 to 2.0 at the end we got this -| Replacing ruleset non_inline_snmp_hosts with snmp_backend_hosts
-| ERROR: Invalid regular expression in service condition detected: (Ruleset: ignored_services, Folder: , Rule nr: 37, Condition: \Check_MK Discovery, Exception: bad escape \C at position 0)
-| ERROR: Invalid regular expression in service condition detected: (Ruleset: ignored_services, Folder: , Rule nr: 38, Condition: \Check_MK Discovery, Exception: bad escape \C at position 0)
Updating core configuration…
Generating configuration for core (type nagios)…Configuration Error: Error creating configuration: Invalid regular expression ‘(?:(?:Interface\ 1$)|(?:Postfix\ Queue$)|(?:Postfix\ status$)|(?:\Check_MK Discovery))’: bad escape \C at position 65
Finished update.
We have Check_mk on Development and Production, and after upgrade Cmk on Development, everything is working fine. Does anyone have some solution for this?
Thanks in advance

Hi Ninoslav,
as the error states, you have an invalid regular expression in your config. The python3 regex interpreter is unfortunately not as tolerant of those anymore as it was in python2.

Try to find the rules.mk as your checkmk site user: grep “status.*Check_MK Discovery” ~/etc/check_mk/conf.d/wato/

and in that file, remove the “\” in front of Check_MK Discovery, then try to update your config again by running “cmk-update-config”

If you get alerts on any other regex issues, use the same troubleshooting process again :slight_smile:

Yeah,
Thank you very much, this info. solve all my problems…
Cheers

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.