Hi, I have a cluster of 4 Raspberry Pis that are responsible for close to 20 different activities (Mrtg, Smokeping, OpenVPN [server and client], Netflow , etc). When one fails (which they do) if it wasn't the leader they'll elect a new leader, and that one decides how to redistribute the work. I want that one to make any config changes needed at the time and signal that machine to reload/restart/etc.
As an aside, putting an "After" of gfs.mount seems to have done the trick. Tuc On Fri, Jan 6, 2023, 12:26 PM Lennart Poettering <mzerq...@0pointer.de> wrote: > On Do, 05.01.23 21:39, Scott Ellentuch (tuct...@gmail.com) wrote: > > > > > Restarted the machine and all good. So the next thing I tried was for > > > > keepalived . It started up and failed with not being able to see its > > > config > > > > file (Moved to gluster). > > > > > > It checks for /etc/keepalived/keepalived.conf file. If you moved this > > > file somewhere else, you presumably need to adjust path to this file in > > > unit definition as well. > > > > > File is in the same location, just /etc/keepalived is a link to > > /gfs/etc/keepalived . > > This sounds like a bad idea. use gluster for storing data, not for > storing configuration. You are using a cluster storage where you > should just use configuration management. Don't confuse the two > concepts. One is totally not like the other, and you cannot replace > one with the other. > > This will create tons of cyclic deps. > > This all sounds like a terrible idea, you are actively working on > making things hard for you. > > Lennart > > -- > Lennart Poettering, Berlin >
