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.
Norm
(Norman Kühnberger)
December 26, 2019, 11:59am
2
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
JJX
(JJX)
December 26, 2019, 7:12pm
4
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
BH2005
(Bernd Holzhauer)
December 27, 2019, 4:42am
5
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:
Hallo zusammen,
seit etwa vorgestern kann ich bei meinem check_mk 1.5.0p22 keine Änderungen mehr aktivieren. Ich kann nicht erklären, was sich geändert hätte. Wenn ich „cmk –R –vv“ aufrufe, werden die einzelnen Schritte inkl. aller Host checks angezeigt. Dabei gibt es keinen Fehler. Allerdings bleibt der Vorgang dann zuletzt beim Schritt „Restarting monitoring core…“ stehen und tut nichts mehr bis zum manuellen Abbruch nach mehreren Stunden.
Als Zusatzfrage würde mich noch interessieren, wie i…
Hi @andreas-doehler ,
you was rigth with the load of the cpu
i`d have create a new site on a second server and transfered around 1k host to the new distributed site.
Now it`s working again, not so fast as expected but it works !!!
5K Hosts on Site1 with ~30K Services
1K Hosts on Site2 with ~10K Services
like this POST:
still happend … by differend action`s
Hi,
we are using the 1.6.0p6 Enterprise Version.
If we want to Bulk Edit around 700 hosts, the bulk edit stops after 110s.
Is it really necessary to increase the timeout on slave sites and not just on the master site in distributed monitoring?
In our version i can find the htmllib.py just under /opt/omd/sites/SITENAME/lib/python2.7 but not a value with a timeout.
Is there any improvement for this timeout problem in Version 1.6?
@Mathias @LaMi
Heeeeelp
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