From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from dude02.hi.pengutronix.de ([2001:67c:670:100:1d::28]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXg1W-0001fK-7J for ptxdist@pengutronix.de; Wed, 28 Oct 2020 08:37:34 +0100 Received: from mol by dude02.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1kXg1V-0005y6-UV for ptxdist@pengutronix.de; Wed, 28 Oct 2020 08:37:33 +0100 Date: Wed, 28 Oct 2020 08:37:33 +0100 From: Michael Olbrich Message-ID: <20201028073733.GF3084@pengutronix.de> References: <20201020060458.GA68883@lenoch> <20201021072754.GA96000@lenoch> <20201028072811.GE3084@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201028072811.GE3084@pengutronix.de> Subject: Re: [ptxdist] systemctl daemon-reload fails List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de On Wed, Oct 28, 2020 at 08:28:11AM +0100, Michael Olbrich wrote: > On Wed, Oct 21, 2020 at 09:27:54AM +0200, Ladislav Michl wrote: > > On Tue, Oct 20, 2020 at 08:57:27AM -0400, Jon Ringle wrote: > > > On Tue, Oct 20, 2020 at 2:06 AM Ladislav Michl wrote: > > > > > > > > On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote: > > > > > I recently updated to ptxdist-2020.10.0 for running on our device that > > > > > has 64MB or physical ram. > > > > > With systemd-246.6 that is installed,I'm finding that systemd > > > > > daemon-reload now fails: > > > > > > > > > > $ sudo systemctl daemon-reload > > > > > Failed to reload daemon: Refusing to reload, not enough space > > > > > available on /run/systemd. Currently, 10.6M are free, but a safety > > > > > buffer of 16.0M is enforced. Out of curiosity: What is filling up /run for you? I've always had plenty of space in /run. Michael > > > > > Has anyone else encountered this issue? > > > > > What is the recommended way to handle this? I'm hesitant to increase > > > > > the size of /run in fstab because of the limited RAM I have available. > > > > > > > > I lowered RELOAD_DISK_SPACE_MIN with hope for the best. In my scenario, > > > > daemon-reload is almost never called - only in case technician is doing > > > > some tests on device and there is always watchdog to fix failed software. > > > > > > Yeah, I noticed that systemd hardcoded the value of > > > RELOAD_DISK_SPACE_MIN to 16MB. > > > What did you patch your value to be? > > > > 1MB, previously there was no such check and it was added to fix > > https://github.com/systemd/systemd/issues/5016 > > and those 16MB seems to be just a number big enough... > > For most embedded systemd 16M is probably overkill. But on a server with > thousands of units, it is probably reasonable. A real fix should probably > be something that scales with the number of units. -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de