Hi Joel,
ok, your agent cannot execute the robotmk scripts for some reason.
As long as you see a line like
Exec app ‘C:\ProgramData\checkmk\agent\modules\python-3.venv\Scripts\python.exe C:\ProgramData\checkmk\agent\plugins\robotmk-runner.py’,
robotmk will never run properly. The CMK Python does not have the required modules.
You wrote that you created the rule to disable the CMK Python. => What’s now in the agent log?
You should see now the OS Python executing robotmk. This is the next step you need to take. (It’s obvious that without a successful start of robotmk no HTML/XML can be generated)
Of course, it is possible to also have a Python in the user profile.
But if the Checkmk agent should run robotmk, the one and only place where the modules should be is in the OS python “site-packages”.
Unfortunately, opening an Admin cmd.exe and installing the modules will report that they are already installed - even if you installed them first in your user profile by accident. The user python is within of the module search path.
For testing, you could rename your user installation of Python to something like python_ so that there isn’t any module to load from this place anymore.
Another approach is to open an admin cmd and execute
psexec -i -s cmd.exe
This opens a cmd with SYSTEM context, that means: exactly the user the CMK agent is running with.
Everything you can start here, is able to be started by the CMK agent, too.
Hope that helps!
regards,
Simon