2.3 Beta Update aborted with Error: Failed to migrate autochecks

Hallo,
nachdem ich diverse alte Plugins deaktiviert bzw. gelöscht habe hängt ein Update jetzt an dieser Stelle. Update.log gibt keine weiteren Hinweise.
Hat jemand Tips wo ich suchen sollte?
Gruß
Ralf

Fehler während des Updates:
OMD-Befehl omd -f -V 2.3.0b3.cee update --conflict=install comline_intern konnte nicht ausgeführt werden: Cleaning up tmp directory…OK
2024-03-22 08:32:59 - Updating site ‘comline_intern’ from version 2.2.0p22.cee to 2.3.0b3.cee…

  • Installed dir local/lib/python3/cmk_addons
  • Installed dir local/lib/python3/cmk/plugins
  • Installed dir local/lib/python3/cmk_addons/plugins
  • Installed dir etc/default
  • Updated etc/nagvis/apache.conf
  • Updated etc/check_mk/apache.conf
  • Installed file etc/default/cmc
  • Updated etc/nagios/conf.d/check_mk_templates.cfg
  • Updated etc/ssl/openssl.cnf.dist
  • Updated etc/ssl/openssl.cnf
  • Installed dir etc/ssl/saml2/builtin/encryption
  • Updated etc/ssl/misc/tsget.pl
  • Updated etc/ssl/misc/CA.pl
  • Identical etc/ssl/misc/tsget
  • Updated etc/mk-livestatus/nagios.cfg
  • Updated etc/init.d/agent-receiver
  • Updated etc/init.d/cmc
  • Installed file etc/logrotate.d/security
  • Installed file etc/logrotate.d/audit
  • Vanished etc/cron.d/cmk_discovery
    Creating temporary filesystem /omd/sites/comline_intern/tmp…ATTENTION
    Some steps may take a long time depending on your installation.
    Please be patient.

Cleanup precompiled host and folder files
Verifying Checkmk configuration…
01/05 Rulesets…
02/05 UI extensions…
03/05 Agent based plugins…
04/05 Autochecks…

Update aborted with Error: Failed to migrate autochecks.
Your site has not been modified.
The update can be retried after the error has been fixed.
OK

Führe mal nun den “cmk-update-config -vvv” aus. Da dürfte wesentlich mehr zum Fehler kommen.

Hallo,
es scheint robotmk zu sein das gerade klemmt.
Zeit die changelogs zu lesen da sich da ja ein komplette Änderung ergibt.

Es war robotmk.
Ich habe das System auf dem der robot agent lief aus dem Monitoring entfernt.
Für meine Testumgebung ok aber in einer produktiven Umgebung wird das ein Thema,
Gruß

Hier noch die Meldung zum Problem:

11/26 Autochecks…
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.‘, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(’.
’, ‘3’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
Transform failed: host=‘srvrobotcmk’, plugin=‘robotmk’, ruleset=‘robotmk’, params={‘robot_discovery_settings’: [(‘.*’, ‘2’, ‘’)]}, error=AssertionError(‘non-empty params vanished’)
12/26 Remove unused host attributes…

Das wäre nicht nötig - einzig das alte Autocheck File stellt hier ein Problem dar.
Dieses einfach löschen und nach dem Update wieder per Discovery neu erzeugen lassen. Sollte im Normalfall kein Problem sein.
Autocheck File Probleme gibt es öfters wenn Checks halt irgendeinen Parameter hier speichern.

1 Like