Proper way to delay boot up

Started by dumaresq, August 06, 2024, 04:49:20 PM

Previous topic - Next topic
Hi,

I have HA turned on.  if for some reason my whole network is down, on boot up, I want my secondary firewall to wait about 5 minutes (For my ISP to give me my IPs) and then boot.   After that I want the primary to come up about 1 minute later.   This is due to the complexities of having only a single wan IP and using CARP.  Anyway, the way I've done this is I have modified /usr/local/etc/rc.loader.d/20-misc so it contains autoboot_delay="400" on the primary and autoboot_delay="300" on the secondary.  Sadly every update causes this file to be overritten.  I Assume there must be a setting somewhere I can change to have this perist but I cannot figure it out.   What am I missing?

Thanks!

Not what any of us would want (because of $), but what about a programmed PDU to turn the power back on after the time elapses?

Is there a delay in the BIOS that you can set? Maybe how long the BIOS function keys are displayed? I've done this in the past when I needed something to wait 2 minutes before loading the OS, but I don't think too many of my current servers even support this anymore.

I don't think there is a setting in the OPN config file for this, which is why it keeps getting written over during an update. And from my point of view, this isn't really a strange request, I try to do this with my VMs so that they don't all try to boot at the same time and drag the disk array down to a crawl.

August 06, 2024, 06:30:39 PM #2 Last Edit: August 06, 2024, 06:41:21 PM by Baender
Isn't it like most .d folders, that an additional file like 70-custom-delay with the same content would overwrite 20-misc? Like most of those files work in the Linux world? That way, the 20-misc can be overwritten from any update, but your setting would remain. I don't think, that the whole folder is overwritten/deleted at an update?

Edit: first found value prevails. You need your custom file to be lower than 20.

Quote from: Baender on August 06, 2024, 06:30:39 PM
Isn't it like most .d folders, that an additional file like 70-custom-delay with the same content would overwrite 20-misc? Like most of those files work in the Linux world? That way, the 20-misc can be overwritten from any update, but your setting would remain. I don't think, that the whole folder is overwritten/deleted at an update?

Edit: first found value prevails. You need your custom file to be lower than 20.
This worked great!  thanks so much!   I still think ti shoudl be a var in the GUI but at least this works!

You can add it to the GUI (tunables). But if the first one wins that doesn't help much. Though I was under the impression the last one would as it gets set last.


Cheers,
Franco

I read a bit more, to that topic and unfortunately the answer is: it depends. It depends on the implementation, if the first or last value prevails. So I would try it out. However, I understand dumaresq, that "first value wins" worked for him?

I'm in doubt but I definitely don't have the time to test this at the moment.


Cheers,
Franco