<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:40:11 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/5a30326857122cb7f6c245f2a3faf485d5abd4b8.png?u=847429"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 5, 2023 at 4:15 AM Lennart Poettering <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mi, 04.01.23 13:21, Scott Ellentuch (<a href="mailto:tuctboh@gmail.com" target="_blank">tuctboh@gmail.com</a>) wrote:<br>
<br>
> Hi,<br>
><br>
> I'm trying to do something with inconsistent results and wondered where I'm<br>
> going wrong. I recently installed GLUSTERFS onto a set of 4 Raspberry PI's,<br>
> but am having some boot sequencing issues.<br>
><br>
> It started trying to run rsyslogd. Apparently, it was getting started<br>
> before the gluster mount was done. After a bit of looking, I added into<br>
> [Unit] -<br>
><br>
> After=glusterd.service<br>
><br>
> Restarted the machine and all good.<br>
<br>
Hmm, you actually *want* rsyslog to run after glusterd?<br>
<br></blockquote><div>No, I really don't, but because the rsyslog.conf's are on the glusterfs volume, my hands are a bit tied. I could move them back to the root filesystem, but defeats why I did that all in the first place.</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">
The thing is that most system services log, and I presume glusterd<br>
too, and usually you want that to enter your log framework of choice,<br>
but that means rsyslog probably should run first, not after glusterd,<br>
but that means it cannot log onto gluster fs. because that would be a<br>
cyclic dep.<br>
<br></blockquote><div>In my case besides the rsyslog.conf being on the gluster fs, its also logging to the gluster fs. Double whammy.</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">
> 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). 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. (And I did run<br>
> `systemctl daemon-reload` after the change.<br>
><br>
> How can I track down why this isn't happening in the order I expect?<br>
<br>
This all smeels like a mess of cyclic deps. See the system logs<br>
(journalctl).<br>
<br></blockquote><div>Yea, I actually am fuzzy on that right now, I'll be back to it by Tuesday next week.</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">
/etc/ must be available during early boot, before you run complex<br>
services (such as glusterd) off it. Thus it cannot be backed by such<br>
complex services.<br>
<br></blockquote><div><br></div><div>I don't have ALL of /etc. I just have directories or files, but essentially the same issue.</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">
If you want /etc/ to be backed by such complex services, these<br>
services must run from the initrd, and stick around. But I doubt<br>
glusterfs is ready for that.<br>
<br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Berlin<br>
</blockquote></div></div>