Problems starting a service discovery using REST API

CMK version: Checkmk Raw Edition 2.2.0p7
OS version: latest docker image

**Error message:

Bulk discovery started…
2023-08-01 16:49:37,864 [30] [cmk.web.automations 2274] ‘check_mk --automation service-discovery --timeout 108 @scan fix_all lab.local’ returned '‘FIX_ALL’

2023-08-01 16:49:37,869 [40] [cmk.web.automations 2274] Error running ‘check_mk --automation service-discovery --timeout 108 @scan fix_all lab.local’ (exit code 2)
2023-08-01 16:49:37,873 [40] [cmk.web.background-job 2274] Error during discovery of lab.local on site cmk
Traceback (most recent call last):
File “/omd/sites/cmk/lib/python3/cmk/gui/watolib/bulk_discovery.py”, line 198, in _bulk_discover_item
response = discovery(
^^^^^^^^^^
File “/omd/sites/cmk/lib/python3/cmk/gui/watolib/check_mk_automations.py”, line 131, in discovery
_automation_serialized(
File “/omd/sites/cmk/lib/python3/cmk/gui/watolib/check_mk_automations.py”, line 53, in _automation_serialized
cmdline, serialized_result = check_mk_local_automation_serialized(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/omd/sites/cmk/lib/python3/cmk/gui/watolib/automations.py”, line 146, in check_mk_local_automation_serialized
raise local_automation_failure(
cmk.utils.exceptions.MKGeneralException: Error running automation call service-discovery (exit code 2), error:

‘FIX_ALL’

Bulk discovery finished.
Hosts: 1 total (0 succeeded, 0 skipped, 1 failed)
**

Hi team, it’s me again … Today with another error using the REST API.

Whenever I start a bulk service-discovery (using the ‘default’ values used by the API doc) using the REST API I get the following error. Using the Web GUI works pretty fine. I tried different “modes”. Do I need special rights to start a service discovery?

Regards
Marc

1 Like

I have the same issue with the mode ‘fix_all’ in a “start a bulk discovery job”. Even tho according to the REST-API documentation ‘fix_all’ is a valid mode for it.

Apparently the issue is even older than expected: