<div dir="ltr"><div dir="ltr"><br><br><br><br><div id="gmail-mt-signature">
        <table border="0" cellpadding="8" cellspacing="0" style="user-select: none;">
            <tbody><tr>
                <td>
                    <a id="gmail-signatureLink-logo" href="https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&" class="gmail-mt-no-pointer-events" style="text-decoration:none">
                        <img src="https://s3.amazonaws.com/mailtrack-signature/sender-notified-72.gif" alt="Mailtrack" class="gmail-mt-no-pointer-events" width="32" height="32">
                    </a>
                </td>
                <td>
                    <span style="color:rgb(119,119,119)">Sender notified by</span> <br>
                    <a id="gmail-signatureLink-text" href="https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&" class="gmail-mt-install gmail-mt-no-pointer-events" style="color:rgb(67,116,247)">Mailtrack</a>
                    
    </td><td><span style="color:transparent;font-size:0px">01/05/23, 09:34:36 PM</span></td>

                
                <td>
                    
                </td>
            </tr>
        </tbody></table>
    </div></div><br><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/67b713ed239600b01a105a134cdfe1732d4b50e2.png?u=847429"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 5, 2023 at 1:42 AM Andrei Borzenkov <<a href="mailto:arvidjaar@gmail.com">arvidjaar@gmail.com</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> Restarted the machine and all good. So the next thing I tried was for<br>
> keepalived . It started up and failed with not being able to see its config<br>
> file (Moved to gluster).<br>
<br>
It checks for /etc/keepalived/keepalived.conf file. If you moved this <br>
file somewhere else, you presumably need to adjust path to this file in <br>
unit definition as well.<br>
<br></blockquote><div><br></div><div>File is in the same location, just /etc/keepalived is a link to /gfs/etc/keepalived .</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> I changed -<br>
> <br>
> [Unit]<br>
> Description=Keepalive Daemon (LVS and VRRP)<br>
> After=network-online.target<br>
> Wants=network-online.target<br>
> # Only start if there is a configuration file<br>
> ConditionFileNotEmpty=/etc/keepalived/keepalived.conf<br>
> <br>
> to<br>
> <br>
> [Unit]<br>
> Description=Keepalive Daemon (LVS and VRRP)<br>
> After=network-online.target glusterd.service<br>
> Wants=network-online.target glusterd.service<br>
> # Only start if there is a configuration file<br>
> ConditionFileNotEmpty=/etc/keepalived/keepalived.conf<br>
> <br>
> But it still isn't letting glusterd run before it. <br>
<br>
What exactly does it mean? What is "it" that "isn't letting" and what is <br>
"it" in "before it" and how you determine that the problem is due to the <br>
wrong order?<br>
<br></blockquote><div><br></div><div>keepalived appears to run before gluster has completed its mounts since I'm getting a message about the ConditionFileNotEmpty being empty.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
>(And I did run<br>
> `systemctl daemon-reload` after the change.<br>
><br>
<br>
daemon-reload applies to units started after it. When you edited unit <br>
definition your system was already booted so presumably this unit was <br>
already activated.<br>
<br></blockquote><div><br></div><div>Just covering all bases.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> How can I track down why this isn't happening in the order I expect?<br>
> <br>
<br>
What makes you think the problem is in ordering of units? Have you <br>
checked journal? systemd logs when it begins and completes activation of <br>
each unit.<br></blockquote><div><br></div><div>I am not near the systems for the next few days due to a funeral, I don't remember now.</div><div><br></div><div>Thanks</div></div></div>