<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>On Mon, 2025-10-06 at 16:30 -0400, Khalid Baheyeldin wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div style="font-size:small" class="gmail_default"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div style="font-size:small" class="gmail_default">Anton,</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">The dmesg command does not keep data across reboots.</div><div style="font-size:small" class="gmail_default">It only shows the data from when the last boot was done. </div></div></div></div></div></div></blockquote><div><br></div><div>True, but sometimes its still a source of information. I've recently had a similar experience with a cloud provider. <br>Anyway you seams to have found half the time in the commend below and the rest is probably what Chris suggested. <br>See my other comment below. </div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div style="font-size:small" class="gmail_default"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">The server has two sets of RAID SSDs, but they should be checked on boot, not shutting down.</div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><div style="font-size:small" class="gmail_default">Ron,</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Here is what systemd-analyze blame reports.</div><div style="font-size:small" class="gmail_default">Not sure if that is across boots, or just the current boot though.</div><br><div style="font-size:small" class="gmail_default"><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">2min 145ms systemd-networkd-wait-online.service</span><br> 30.164s apt-daily-upgrade.service<br> 3.226s motd-news.service<br> 1.738s fstrim.service<br> 1.635s munin-node.service<br> 757ms fwupd-refresh.service<br> 731ms mysql.service</span></div></div></div></div></div></div></blockquote><div><br></div><div>A! <span style="font-family: monospace;">systemd-networkd-wait-online.service had mess with me before. <br>How many network interfaces do you have on the machine? Either plugged in or not? <br></span></div><div>And what do you use to manage them? systemd-networkd, NetworkManager, ifupdown or other?<br><br>I use systemd-networkd.<br><br>Since my clients servers sometimes boot without network I've solved that problem with just systemctl disable systemd-networkd-wait-online.service<br><br></div><div>However some services would not start properly if there is no network interface available. To resolve this I install networkd-dispatcher and have scripts to restart/reload services that do not bring hooks in their packages to resolve networking going up/down. </div><div><br></div><div>Another option is just to create /etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf file and override the Start directive to listen only to your main interface like so: </div><div>[Service]</div><div>ExecStart=</div><div>ExecStart=/lib/systemd/systemd-networkd-wait-online --interface enp6s0</div><div><br></div><div><br></div><div>Notice the first ExecStart is not an error, but is used to clear the current command. Otherwise it would execute both</div><div><br></div><div>Hope helps. <br>If you are coming tonight to the meting we could discuss more :) </div><div>Cheers</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div style="font-size:small" class="gmail_default"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">The ap-daily-upgrade is not something that runs on boot, and </div><div style="font-size:small" class="gmail_default">would not block anything. </div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">But the first entry of "wait online" is kind of suspicious.</div><div style="font-size:small" class="gmail_default">It may mean that 2 minutes of the current boot is wasted </div><div style="font-size:small" class="gmail_default">until the network is up (however that is assessed).</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">The rest is too low to be relevant. </div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">John Sellens</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Great point. I have anecdotally noticed this over the years, but </div><div style="font-size:small" class="gmail_default">never got to measuring them, because once the server is live, </div><div style="font-size:small" class="gmail_default">the reboots are rare (sometimes we go 500 days without a reboot).</div><div style="font-size:small" class="gmail_default"><br></div>This server is not yet live, so I got curious ...</div></div></div></div><br></div><div>_______________________________________________<br></div><div>kwlug-disc mailing list<br></div><div>To unsubscribe, send an email to <a href="mailto:kwlug-disc-leave@kwlug.org">kwlug-disc-leave@kwlug.org</a><br></div><div>with the subject "unsubscribe", or email<br></div><div><a href="mailto:kwlug-disc-owner@kwlug.org">kwlug-disc-owner@kwlug.org</a> to contact a human being.<br></div></blockquote><div><br></div><div><span></span></div></body></html>