...
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Problem
Activating Changes, specifically, a CMC reload, takes a long time.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
OMD[mysite]:~$ find ~/var/check_mk/web -follow -type f | wc -l OMD[mysite]:~$find~$ find ~/local -follow -type f | wc -l |
...
Please run this command on the master central and remote sites to see if the local files are the same:
...
If the above suggestions do not point you to the solution, you can use the profiling mechanism to profile Activate changes.
| Tip |
|---|
BTW: Every checkmk Checkmk command can be profiled. The whole syntax of the profile command is described here: Enable Checkmk profilingprofiling#Profilingviacli. |
Let's run the following command on the master central and remote sites to create a profile file of cmk -O. cmk -O is doing a configuration reload, which is part of a typical activation process.
...
If you want to debug the profile files alone, please follow the manual Enable Checkmk profilingprofiling#GUIProfiling otherwise, please open a support case and include these three files.
...