Error while Removing services

Hi Team,

i am facing similar issues multiple times while i was removing services and the error is…

Internal error

Internal error: Your request timed out after 110 seconds. This issue may be related to a local configuration problem or a request which works with a too large number of objects. But if you think this issue is a bug, please send a crash report.

I have noticed this issue while removing ex: 5 services also i.e less number.

may i know why this issue has been arising multiple times while performing actions.

Hi, can you please provide the specs of your checkmk Server? (RAM,CPU,SSD/HDD, VM/Hardware)
Thanks in advance.

2 Likes

Hi Norm,

specs of our check_mk Server…

RAM - 4GB
CPU - 2
SSD/HDD - 2 x 70 GB
VM/Hardware - VM

Hi,
do you experience any performance Issues while using CheckMK?
Have you checked CPU usage and storage io while the error occurs?
See top / htop / iotop / iostat to check if the timeout is caused by a high system load or a busy storage or if there is something else.

2 Likes

Hello together I have similar problems,
but sometimes it’s just not possible

Also the shift of Host brought only so1 day what

Config with me

2 Server Debian 10 CMK 1.6 CMC/CEE
8 Core CPU
24 GB RAM each Server

for me the only help is still on the console cmk -R and then a cmk -O

then discard changes in WATO

Then the changes are accepted and WATO is clean again.

For me it doesn’t matter if I have a thousand or only 2 Changes

get also with -vv no errors displayed and the load of the CPU is current

top - 20:29:31 up 35 min, 1 user, load average: 6.40, 12.05, 14.97

also with less load I have the same problem

take a look hier also:

it thems to be a generell Problem

and yes, before there is another discussion about cmk -R or -O

But exactly in this order it works for me, that does not mean that it works where else it goes…

one point left after all … take a look into:

~tmp/check_mk/wato/activation/

if there no Changes pending this folder should be empty

1 Like