Hi,
is there some way to adjust GUI timeout of 110 seconds somewhere?
In some cases, such as renaming of hosts, or discovery of a host that is slow to respond to SNMP, the GUI times out too soon while the slave node is still processing stuff.
I tried changing "Total query timeout" in distributed monitoring settings, but this didn't help (it was set to 120 second, anyway).
···
--
- Dr. Antti Mäkelä | Senior Architect | CCIE #20962 -
- Vintor Oy, Itsehallintokuja 6, 02600 Espoo | www.vintor.fi -
In htmllib.py you can see
self._request_timeout = 110 # Seconds
But is this a hardcoded value?
···
--
- Dr. Antti Mäkelä | Senior Architect | CCIE #20962 -
- Vintor Oy, Itsehallintokuja 6, 02600 Espoo | www.vintor.fi -
-----Original Message-----
From: Mäkelä, Antti
Sent: maanantai 25. kesäkuuta 2018 15.02
To: checkmk-en@lists.mathias-kettner.de
Subject: Distributed monitoring - GUI timeout
Hi,
is there some way to adjust GUI timeout of 110 seconds somewhere?
In some cases, such as renaming of hosts, or discovery of a host that is slow to respond to SNMP, the GUI times out too soon while the slave node is still processing stuff.
I tried changing "Total query timeout" in distributed monitoring settings, but this didn't help (it was set to 120 second, anyway).
--
- Dr. Antti Mäkelä | Senior Architect | CCIE #20962 -
- Vintor Oy, Itsehallintokuja 6, 02600 Espoo | www.vintor.fi -
Right.
Based on that werk, I should edit the proxy-port.conf on the *slave* site to e.g. 240 seconds. Then change the value on the *master* (in htmllib.py) to e.g. 230 seconds.
Not the most elegant method (would really hope that this would be configurable), but I guess it works.
···
--
- Dr. Antti Mäkelä | Senior Architect | CCIE #20962 -
- Vintor Oy, Itsehallintokuja 6, 02600 Espoo | www.vintor.fi -
-----Original Message-----
From: Jam Mulch <spammagnet10@gmail.com>
Sent: maanantai 25. kesäkuuta 2018 15.39
To: Mäkelä, Antti <Antti.Makela@vintor.fi>
Subject: Re: [Check_mk (english)] Distributed monitoring - GUI timeout
I vaguely remember an email...maybe one of the'werks' that hardcoded a timeout into the web gui, but I don't know where.
take a look at:
https://mathias-kettner.de/check_mk_werks.php?werk_id=3856&HTML=yes
On 6/25/2018 8:30 AM, Mäkelä, Antti wrote:
Hi,
OMD has automatically created a file with timeout of 120 seconds...However, adjusting these values at least on the master site alone did not help.
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 