[Check_mk (english)] distributed monitoring setup -- slave node went out of sync?

Paul Dott pauldott at gmail.com
Fri Feb 15 18:53:27 CET 2019

This is the expected behavior when adding a new slave site to distributed
setup. I'm assuming the other slave sites were already connected and in
sync, which is why they were unaffected.

On Fri, Feb 15, 2019 at 9:35 AM Christian Vo <christian.vo at gmail.com> wrote:

> Hi everyone,
> After setting up new node to my distributed monitoring setup, I ran into
> this weird issue today:
> when I goto WATO,  I notice no changes required,  but the slave node shows
> "restart required".
> why is this happening?
> one bad side-effect associated to this  -- my master dashboard went from
> 300+ monitored hosts (expected) down to 1xx,  due to all hosts being
> monitored on the slave node not being seen from the master...  restart from
> WATO resolved the issue...
> the other distributed nodes in this setup were unaffected, this only
> happened on the new node.
> any ideas where to start troubleshooting?
> the new node is a physical server, and OS uptime seems fine...
> _______________________________________________
> checkmk-en mailing list
> checkmk-en at lists.mathias-kettner.de
> Manage your subscription or unsubscribe
> https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mathias-kettner.de/pipermail/checkmk-en/attachments/20190215/decc4f80/attachment.html>

More information about the checkmk-en mailing list