[Check_mk (english)] Distributed WATO - Replication Status not completing. Slave configs out of sync

Hi.

We had this problem with one specific slave with a large configuration.

We fixed it with the solution mentioned here:
http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/

Basically, we modify the /omd/sites/your_slave_site /etc/apache/proxy-port.conf and change the line that
contains the directive ProxyPass from:

···
ProxyPass http://127.0.0.1:5000/**your_slave_site** retry=0 disablereuse=On

to:

ProxyPass http://127.0.0.1:5000/**your_slave_site**
 retry=0 disablereuse=On **acquire=10000 timeout=600 Keepalive=On ttl=120 connectiontimeout=10**

Once modified, we restart everything and it works.

Hope this can help.

</details>

A great idea as well. Thank you.

I’ll report back how it goes.

···

On Mon, Mar 21, 2016 at 10:03 AM, Beaulieu, René [2] Beaulieu.Rene2@hydro.qc.ca wrote:

Hi.

We had this problem with one specific slave with a large configuration.

We fixed it with the solution mentioned here:
http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/

Basically, we modify the /omd/sites/your_slave_site /etc/apache/proxy-port.conf and change the line that
contains the directive ProxyPass from:

ProxyPass [http://127.0.0.1:5000/](http://127.0.0.1:5000/)**your_slave_site** retry=0 disablereuse=On

to:

ProxyPass http://127.0.0.1:5000/your_slave_site
retry=0 disablereuse=On acquire=10000 timeout=600 Keepalive=On ttl=120 connectiontimeout=10

Once modified, we restart everything and it works.

Hope this can help.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

I was able to duplicate the symptom on my master server. One of the
slaves takes about 40 seconds
to complete. On the master I changed /etc/httpd/conf/httpd.conf
from:

Timeout 45

to:

Timeout 30

and restarted httpd. Triggered an 'Apply Configuration' and the

slower site never showed up as done
on the master…it actually did finish, but the webpage didn’t show
it.

Then I changed it to:

Timeout 60

and restarted httpd. It's working again.
···

On 03/21/2016 11:09 AM, Joe Hedrick
wrote:

A great idea as well.� Thank you. �

I’ll report back how it goes.

      On Mon, Mar 21, 2016 at 10:03 AM,

Beaulieu, Ren� [2] <>
wrote:

Hi.

                We had this

problem with one specific slave with a large
configuration.

                We fixed it with

the solution mentioned here:
http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/

                Basically, we

modify the /omd/sites/your_slave_site /etc/apache/proxy-port.conf
and change the line that contains the
directive�ProxyPass from:

ProxyPass [http://127.0.0.1:5000/](http://127.0.0.1:5000/)**your_slave_site** retry=0 disablereuse=On

to:

                  ProxyPass

http://127.0.0.1:5000/your_slave_site
retry=0 disablereuse=On ** acquire=10000
timeout=600 Keepalive=On ttl=120
connectiontimeout=10**

                Once modified,

we restart everything and it works.

                Hope this can

help.

        _______________________________________________

        checkmk-en mailing list

        checkmk-en@lists.mathias-kettner.de

        [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
_______________________________________________
checkmk-en mailing list

Beaulieu.Rene2@hydro.qc.cacheckmk-en@lists.mathias-kettner.dehttp://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Bumping my timeout from 60 to 120 looks to have allowed enough time for a successful sync. That seems like quite a long time though. I think some further investigation as to what is taking so long in syncs is in order.

Thank you all for your help.

···

On Mon, Mar 21, 2016 at 10:20 AM, Jam Mulch spammagnet10@gmail.com wrote:

I was able to duplicate the symptom on my master server. One of the

slaves takes about 40 seconds

to complete. On the master I changed /etc/httpd/conf/httpd.conf

from:

Timeout 45



to:



Timeout 30



and restarted httpd. Triggered an 'Apply Configuration' and the

slower site never showed up as done

on the master...it actually did finish, but the webpage didn't show

it.

Then I changed it to:



Timeout 60



and restarted httpd. It's working again.





  On 03/21/2016 11:09 AM, Joe Hedrick

wrote:

A great idea as well. Thank you.

I’ll report back how it goes.

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
      On Mon, Mar 21, 2016 at 10:03 AM,

Beaulieu, René [2] Beaulieu.Rene2@hydro.qc.ca
wrote:

Hi.

                We had this

problem with one specific slave with a large
configuration.

                We fixed it with

the solution mentioned here:
http://hermannsspace.de/wp/reverse-proxy-timeouts-with-check_mk/

                Basically, we

modify the /omd/sites/your_slave_site /etc/apache/proxy-port.conf
and change the line that contains the
directive ProxyPass from:

ProxyPass [http://127.0.0.1:5000/](http://127.0.0.1:5000/)**your_slave_site** retry=0 disablereuse=On

to:

                  ProxyPass

http://127.0.0.1:5000/your_slave_site
retry=0 disablereuse=On ** acquire=10000
timeout=600 Keepalive=On ttl=120
connectiontimeout=10**

                Once modified,

we restart everything and it works.

                Hope this can

help.

        _______________________________________________

        checkmk-en mailing list

        checkmk-en@lists.mathias-kettner.de

        [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)