[Check_mk (english)] Setting op liveproxyd

[Paul Bongers]

Hi list,

I'm setting up a new remote site and stumbled upon something I can't
explain.

I've configured the connection with Livestatus Proxy-Daemon on port 6557.
On the remote site I enabled liveproxyd and disabled livestatus tcp.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: off
...

However, when I look on my WATO master, it says the remote site is down.
As soon as I enable livestatus tcp on port 6557 it starts working. Note
that I left liveproxyd enabled as well.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: on
LIVESTATUS_TCP_PORT: 6557
...

I already have this setup on another remote connection, but until now I
haven't wondered about it because of several network related issues at
the time that I set up that connection.

Is liveproxyd supposed to run on the WATO master instead of on the WATO
slave? Or am missing something?

Note that I have liveproxyd enabled on the WATO master already. All
sites are running Check_MK 1.2.6p12.cre.

Regards,

Paul

[Andreas Döhler]

Hi Paul,

Liveproxy only needs to run on the master site. All slave sites have normal
livestatus tcp enabled.
The liveproxy only handles timeouts and connection problems from master to
slave. The slave doesn't know anything about the liveproxy.

Best regards
Andreas

Post by Paul Bongers
Hi list,
I'm setting up a new remote site and stumbled upon something I can't
explain.
I've configured the connection with Livestatus Proxy-Daemon on port 6557.
On the remote site I enabled liveproxyd and disabled livestatus tcp.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: off
...
However, when I look on my WATO master, it says the remote site is down.
As soon as I enable livestatus tcp on port 6557 it starts working. Note
that I left liveproxyd enabled as well.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: on
LIVESTATUS_TCP_PORT: 6557
...
I already have this setup on another remote connection, but until now I
haven't wondered about it because of several network related issues at
the time that I set up that connection.
Is liveproxyd supposed to run on the WATO master instead of on the WATO
slave? Or am missing something?
Note that I have liveproxyd enabled on the WATO master already. All
sites are running Check_MK 1.2.6p12.cre.
Regards,
Paul
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

[Paul Bongers]

Hi Andreas,

Thanks for your answer. That explains a lot.

Regards,

Paul

Post by Andreas Döhler
Hi Paul,
Liveproxy only needs to run on the master site. All slave sites have
normal livestatus tcp enabled.
The liveproxy only handles timeouts and connection problems from
master to slave. The slave doesn't know anything about the liveproxy.
Best regards
Andreas
Hi list,
I'm setting up a new remote site and stumbled upon something I can't
explain.
I've configured the connection with Livestatus Proxy-Daemon on port 6557.
On the remote site I enabled liveproxyd and disabled livestatus tcp.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: off
...
However, when I look on my WATO master, it says the remote site is down.
As soon as I enable livestatus tcp on port 6557 it starts working. Note
that I left liveproxyd enabled as well.
$ omd config show
...
LIVEPROXYD: on
LIVESTATUS_TCP: on
LIVESTATUS_TCP_PORT: 6557
...
I already have this setup on another remote connection, but until now I
haven't wondered about it because of several network related issues at
the time that I set up that connection.
Is liveproxyd supposed to run on the WATO master instead of on the WATO
slave? Or am missing something?
Note that I have liveproxyd enabled on the WATO master already. All
sites are running Check_MK 1.2.6p12.cre.
Regards,
Paul
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en