Can't activate changes, or bake a agent after upgrade to 2.4.0p4

Feedback 2.4 Beta
1

CMK version: 2.4.0p4
OS version: RHEL 9.5

Error message: Failed to start discovery: Got response: HTTP 404: {“detail”:“Not Found”}

after updating from 2.3.0p30 → (latest) 2.3.0p34 → (latest) 2.4.0p4

eg. bulk changes

brave_ALXVf33XCn

or Activate pending changes

brave_8VXpgDbccN

or bake agents

brave_bGEXF38jgx

what I see at 1st glance is the following entry in the logfile:

SAL@lnzcheckmk01:[~]\> less ./var/log/web.log
....
2025-06-13 17:49:48,817 [40] [cmk.web 808221] error calling AJAX page handler
Traceback (most recent call last):
  File "/omd/sites/SAL/lib/python3/cmk/gui/pages.py", line 102, in handle_page
    action_response = self.page()
                      ^^^^^^^^^^^
  File "/omd/sites/SAL/lib/python3/cmk/gui/wato/pages/activate_changes.py", line 1013, in page
    activation_id = manager.start(
                    ^^^^^^^^^^^^^^
  File "/omd/sites/SAL/lib/python3.12/contextlib.py", line 81, in inner
    return func(*args, **kwds)
           ^^^^^^^^^^^^^^^^^^^
  File "/omd/sites/SAL/lib/python3/cmk/gui/watolib/activate_changes.py", line 1492, in start
    self._start_activation()
  File "/omd/sites/SAL/lib/python3.12/contextlib.py", line 81, in inner
    return func(*args, **kwds)
           ^^^^^^^^^^^^^^^^^^^
  File "/omd/sites/SAL/lib/python3/cmk/gui/watolib/activate_changes.py", line 1796, in _start_activation
    raise result.error
cmk.gui.job_scheduler_client.StartupError: Got response: HTTP 404: {"detail":"Not Found"}

what could I do to investigate further?

After upgrade to 2.4.0p8, connection tests fail with "API Error:Error running automation call"
2

Which CheckMK package did you install for the 2.4.0p4 update? What messages can be found in “~/var/log/apache/error_log”

3

it was https://download.checkmk.com/checkmk/2.4.0p4/check-mk-enterprise-2.4.0p4-el9-38.x86_64.rpm

meanwhile I restored to 2.3.0p34 and will update again in the near future. I’ll keep you informed

4

Are you using a Proxy by any chance which you have defined manually in the site .bashrc or .bash_profile ?
You can login as site user and then do the following to check this:

env|grep -i proxy

As a test, comment out the environment variable , source the dot files and try again.

1 Like
5

very good hint, thank you! :slightly_smiling_face:
I indeed use a proxy, and here I’ve seen are expired settings.
So I’ve updated this now, and hope the best for the update then.

6

relates to my ticket from july 2025 After upgrade to 2.4.0p8, connection tests fail with "API Error:Error running automation call"

7

We fixed it as well Werk #18305: Avoid "HTTP 404: {"detail":"Not Found"}" in Checkmk UI and REST API . Hopefully p9 will be out next week.

8

solved with v2.4.0p10 :slightly_smiling_face:

2 Likes