Dual Server Setup with Kuma for Uptime Monitoring?
reddit / selfhosted

----------------------------------------------------------------------
MangoMolester · 2023-11-05 10:53

Hey all,

Currently using Kuma to monitor my external services and it's been
solid. I'm looking to also keep tabs on services on my main server
within the same setup.

Is it possible to run Kuma on two servers at the same time for
redundancy? Basically, if my main server goes down (think network
issues or a power cut), I want a backup server to pick up the slack
automatically, using the same dashboard.

Anyone done something similar or have tips on setting this up?

----------------------------------------------------------------------
rafipiccolo · 2023-11-05 12:06

it may be anoying to configure, but 2 separate instances with 2
distinct databases will work. You would need to configure all services
twice (once for each uptime kuma instance).

unless the maintainer have carefully worked on it, having 2 separate
instances with the same database may result in double inserts in
database for ping events. which leads to unexpected results. and it
may work for a time, but not necessarily for the next upgrade.

people seems interested in your vision but i dont find it solved :
https://github.com/louislam/uptime-kuma/issues/3393

the easy solution is to have one real instance with all your services
to watch, and the second watching the first. The first instance should
also monitor the second.

----------------------------------------------------------------------
MangoMolester · 2023-11-05 12:10

Thank you for your reply!

​

>people seems interested in your vision but i dont find it solved :
[https://github.com/louislam/uptime-
kuma/issues/3393](https://github.com/louislam/uptime-kuma/issues/3393)

Yea, that is exactly what I was thinking. Thank you for linking it.

​

>the easy solution is to have one real instance with all your services
to watch, and the second watching the first. The first instance should
also monitor the second.

The problem with this is when my first instance goes down, I will get
notified, but all the monitors that it was running have no data for
the down period.

----------------------------------------------------------------------
00006969 · 2023-11-06 20:54

* Use corosync/pacemaker to switch a virtual IP between the 2 nodes
* Assuming its mariadb/mysql, go with a 2 node galera cluster or
glusterfs over /var/lib/mysql maybe? (for the later, include to
corosync/pacemaker to switch the service)
* In the best of world you'd have a witness node serving as a
tiebreaker