Date: Thu, 31 Oct 2019 14:19:50 +0100 (CET) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> To: freebsd-questions@freebsd.org Subject: Re: Increasing shutdown timeout Message-ID: <alpine.BSF.2.21.99999.352.1910311359270.40313@enterprise.ximalas.info> In-Reply-To: <3cf157fa-6941-b662-9ffd-d9e2370f8846@netfence.it> References: <3cf157fa-6941-b662-9ffd-d9e2370f8846@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 31 Oct 2019 12:47+0100, Andrea Venturoli wrote: > I'm having some problems on different servers with shutdown timeout. > > For the curious, it ranges from bhyve VMs failing to stop (and keeping running > as zombie, preventing real shutdown after init died), to NUT shutdown script > not having the chance to run (so the UPS power won't get killed and the > servers won't come up again unless all batteries are fully drained before the > power comes back). > > First: why not? > Are there good reasons NOT to increase this timeout? Possible side effects? > Any experience with an high value? In my experience, the shutdown script(s) display more patience with a higher value. > Second: how? > I see there's "rcshutdown_timeout" that can be set in /etc/rc.conf, but also > "kern.init_shutdown_timeout" sysctl. > I read the latter is obsolete and not used since years. Seeing it there raises > the doubt. Is it still valid? > Should I increase both? My version control system says I had to increase rcshutdown_timeout from 30 seconds to 60 seconds on 2011-02-28 for one of my systems, and again to 90 seconds on 2011-05-09. 90 seconds has been the default value since 2012-02-17. Try setting rcshutdown_timeout to 120 seconds, or higher, i.e.: rcshutdown_timeout="120" -- Trond.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.99999.352.1910311359270.40313>