Hi,
Just to confirm that we did see a 2-3x time decrease (from ~10 minutes to ~3 minutes) on the Activate changes since incorporating Werk 3806.
Cheers,
Jonathan
-----Message d'origine-----
···
De : Trahan, Jonathan
Envoyé : 26 septembre 2016 10:13
À : 'Fabian Klemusch'; checkmk-en@lists.mathias-kettner.de
Objet : RE: [Check_mk (english)] HTTP 502 timeout while trying to Activate Changes
Hi,
FYI, on our end, we will try this week to incorporate Werk 3806 (http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=5180128047c96bd9b884bb3df9113ed3262981e2) into our 1.2.8p0 installation to see if there is any performance gain.
Cheers,
Jonathan
-----Message d'origine-----
De : Fabian Klemusch [mailto:fabian.klemusch@de.tuv.com]
Envoyé : 26 septembre 2016 08:06
À : Trahan, Jonathan; checkmk-en@lists.mathias-kettner.de
Objet : RE: [Check_mk (english)] HTTP 502 timeout while trying to Activate Changes
Courriel provenant de l’externe
ATTENTION, avant d’accéder à une pièce jointe ou à un lien de ce courriel, assurez-vous que celui-ci provient d’un tiers de confiance.
Hello Jonathan,
our check_MK environment looks similiar to yours.
- same check_MK Version (1.2.8p4) - but the problem exists longer
- we have used the same settings that are provided on http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/
- we are having 10 Slaves to 1 Master
Last year, we had so much trouble with this problem, that we had contact to the support team by check_MK.
- they announced, that this problem should be fixed in version 1.2.8
- but we still get sometimes this 502 timeout
The only troubleshoot I know so far is: restart omd service on the problem machine...
Anyone else have better experiences?
Best regards,
Fabian
-----Original Message-----
From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de] On Behalf Of Trahan, Jonathan
Sent: Donnerstag, 4. August 2016 19:28
To: checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] HTTP 502 timeout while trying to Activate Changes
Hi,
Did anybody ever encountered a timeout while trying to Activate Changes in a distributed environment?
We apply in part the fix explained on this website:
http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/
We only apply the "timeout=600" part so our ProxyPass line looks like:
ProxyPass http://127.0.0.1:5000/your_slave_site retry=0 disablereuse=On timeout=600
... and it did resolve the problem, but I am curious as to why this fix as not been integrated in Check_MK's code since then?
Even with the fix, it can take sometimes up to 4-5 minutes to successfully activate changes. We have 2 slaves site which contains about ~ 1100 servers with 60000 services each. We are on Check_MK 1.2.8 .
Cheers,
Jonathan
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en