Checkmk Distributed Monitoring - Activation Failure Between Primary & Secondary

Troubleshooting
, , ,
1

The issue involves a distributed monitoring setup where activating changes fails, affecting configuration replication and causing monitoring disruptions.

Current Setup:
Version: Checkmk Managed Services Edition 2.3.0p28
Monitoring Mode: Distributed Monitoring (Primary & Secondary) - Working as expected
Issue: No activate any changes between Primary y Secondary servers

image
image1827Ă—450 24.4 KB

2

To debug this, I’d first try to manually reload the site with debug options and check if anything is wrong:

cmk --debug -Rvv

If this doesn’t help, try restarting the slave site:

omd restart

Finally, check ~/tmp/check_mk/wato/activation/ for any old directories and move them out of the way if necessary.

Hope this helps.

1 Like
3

Hi dtuecks

Thank you for your suggestion. I followed your steps, but unfortunately, the solution wasn’t viable.

I ran the commands you provided:

  1. cmk --debug -Rvv to reload the site with debug options, but the issue wasn’t resolved.
  2. I tried restarting the slave site with omd restart, but the problem still persists.
  3. I also checked the ~/tmp/check_mk/wato/activation/ directory, and I didn’t find any old directories that could be causing the issue.

Could you suggest any other alternatives or additional steps I could try to fix it?

Thanks for your help.

Best regards,
José Hernández

4

Hello Community,

Current Configuration:
Version: Checkmk Managed Services Edition 2.3.0p28
Monitoring Mode: Distributed Monitoring (Primary and Secondary) – Operating as expected
Issue: Changes are not being triggered between the primary and secondary servers.

Regarding this issue, it has been confirmed that the Cortex Security Agent is preventing CheckMK from functioning properly.

The Security Team has requested the following information:

  • File Paths
  • File Hashes
  • File Descriptions

I would greatly appreciate your assistance and guidance in gathering the details for these points.

Thank you very much for your support.

Sincerely,
José Hernández

5

All under /opt/omd

You need to hash all the files under the path mentioned by yourself i think.

6

Help Needed – CheckMK and Cortex Agent Compatibility

@andreas-doehler , thank you in advance for your support.

If you help us to obtain specific details about CheckMK to ensure its seamless coexistence with the Cortex agent. If there is any official CheckMK documentation covering these aspects, it would be highly useful as a reference.

Requested Information:

Processes used by CheckMK
Key file and directory paths
Relevant files (executables, configuration files)

This request arises due to detections from the Cortex agent’s Exploit and Malware module. We need to identify any CheckMK components that might be triggering these alerts.

Any insights or guidance on this matter would be greatly appreciated.

Best regards,
José Hernández

7

From my point of view this is a problem of the Cortex agent itself.
CheckMK is no monolithic software so the question for processes and key file is not possible to answer. Every installation can be different, it depends on the selected and active components inside your site.

As i said before - consider all files inside /opt/omd/ as important and relevant for the operation of CheckMK.

1 Like