From MAILER-DAEMON Mon May 01 18:17:05 2023 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1ptbpR-000240-OX for mharc-tech-volunteer-meeting@fsf.org; Mon, 01 May 2023 18:17:05 -0400 Received: from mail.fsf.org ([2001:470:142::13]) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ptbpQ-00023o-Cl for tech-volunteer-meeting@fsf.org; Mon, 01 May 2023 18:17:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org; s=mail-fsf-org; h=In-Reply-To:From:References:To:Subject:MIME-Version:Date; bh=gMl0PGe1nRAhp7uGDyUgmYsmVdRYGOcI1MIzhZhUWsg=; b=LTMfDwU1QLdi4ed7QRKUmJjsO ql5pbhVHrz3NT+avg6QGOU0kkkWAMe2nowUzz0+Ny/W8gJ/rHeYMLVCsscLoZDq4r9zYh5B15fNCZ arpwVeSvCKGSUO7SC/+taLlnd2sGaXHZm9xdhIX9A7L+UyhLgT9/8POlvEQEsa+eNhddvLK9K50gk jtj7B6beNQF+oQ4H/v24Q9SmWRkRHznLMTinHFXn6YOacX1xA/xfuqec2Wd0vN4zD5ipxmMi+tiDe rdwAIpIzn5SlT3AB6E58hBznrCmXQa3DOgzI2wBsll6WT9YHtra4c5U3VWS5uzP43SfkaCsB+Q96h FXf0jjAeQ==; Message-ID: <4b678e39-5406-399b-8c56-f32da1661fa3@fsf.org> Date: Mon, 1 May 2023 18:17:02 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Icedove/102.10.0 Subject: Re: Rebooting with systemd wedged Content-Language: en-US To: tech-volunteer-meeting@fsf.org References: <20230430191724N@bob.proulx.com> From: Andrew Engelbrecht In-Reply-To: <20230430191724N@bob.proulx.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2023 22:17:04 -0000 On 4/30/23 21:42, Bob Proulx wrote: > #!/bin/sh > echo 1 >/proc/sys/kernel/sysrq > echo s >/proc/sysrq-trigger > echo b >/proc/sysrq-trigger If the server is doing anything other than hosting static data, it might make sense to try killing important processes, or sending them commands to exit gracefully, so they can write out any data to disk before they die. I'm thinking mostly about processes like SQL servers. > And of course shutdown and reboot both call systemctl now. Could not > reboot it normally it since systemd is in charge of the reboot and > systemd is not responding. Isn't systemd just such a wonderful > system? ... unless systemd gobbles up the kill command too... As much as I like systemd, I hope not. : P -- Join the FSF and help us defend software freedom: https://my.fsf.org/ US government employee? Use CFC charity code 63210 to support us through the Combined Federal Campaign. https://cfcgiving.opm.gov/ From MAILER-DAEMON Wed May 03 01:20:00 2023 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1pu4uF-0005RF-PW for mharc-tech-volunteer-meeting@fsf.org; Wed, 03 May 2023 01:20:00 -0400 Received: from mail.fsf.org ([2001:470:142::13]) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pu4uD-0005QI-6I for tech-volunteer-meeting@fsf.org; Wed, 03 May 2023 01:19:57 -0400 Received: from havoc.proulx.com ([198.99.81.74]) by mail.fsf.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1pu4uB-00Dt5S-KR for tech-volunteer-meeting@fsf.org; Wed, 03 May 2023 01:19:56 -0400 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 40630699 for ; Tue, 2 May 2023 23:19:50 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1683091190; bh=13Yc6Y++gOnPC6eg82SZhh21j/bPyhwp4zekpgJD6rQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=KteXUbZVuBNVALo+WIvUTBVYIONwZv/WTEeq+0Hy99kspkZ/J/VUpCqxUDatHj3IQ FgCITQUlx81N6QXMPPzoFEf+9HZEM7AtRBIWZ9RKAS5Abeyb8jjUSOU3WhWrZlwSE7 2dH7iO3sY2S9QHv0ZggHYHdpqtZhPxAwwWwuP/3pFJYWfvwHr5x1FHHjq0yTz+qd+A +wVlZRrZi+zbZPbqOlH9VYzjPxY6tFX0XwOLdCT6O0qnWwaiuhEaoDu70rl2I2XZzJ uO9yCYmMo4qzcr1LXvMWKeo4yGTexu/2dxEjTyWu6t+kkAcc8ixWsrS8Slz2aIrYnQ DKBUpGTQljQ0Q== Received: from madness.proulx.com (madness.proulx.com [192.168.230.122]) by joseki.proulx.com (Postfix) with ESMTP id 2081496881 for ; Tue, 2 May 2023 23:19:50 -0600 (MDT) Received: by madness.proulx.com (Postfix, from userid 1000) id 08F3511D49; Tue, 2 May 2023 23:19:50 -0600 (MDT) Date: Tue, 2 May 2023 23:19:49 -0600 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Re: Rebooting with systemd wedged Message-ID: <20230502230838N@bob.proulx.com> References: <20230430191724N@bob.proulx.com> <4b678e39-5406-399b-8c56-f32da1661fa3@fsf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4b678e39-5406-399b-8c56-f32da1661fa3@fsf.org> Received-SPF: pass client-ip=198.99.81.74; envelope-from=rwp@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2023 05:19:57 -0000 Andrew Engelbrecht wrote: > Bob Proulx wrote: > > echo 1 >/proc/sys/kernel/sysrq > > echo s >/proc/sysrq-trigger > > echo b >/proc/sysrq-trigger > > If the server is doing anything other than hosting static data, it might > make sense to try killing important processes, or sending them commands > to exit gracefully, so they can write out any data to disk before they > die. I'm thinking mostly about processes like SQL servers. If the system were running a database then by all means try to shutdown the database first. But it _should_ survive a power outage in most cases anyway. But why chance it if there is the possibility to avoid it? In this case that wasn't a problem though. No database server on this system. In this case just needed to trigger a reboot so that things could get back on track again. > > And of course shutdown and reboot both call systemctl now. Could not > > reboot it normally it since systemd is in charge of the reboot and > > systemd is not responding. Isn't systemd just such a wonderful > > system? > > ... unless systemd gobbles up the kill command too... As much as I like > systemd, I hope not. : P If you are asking about "systemctl stop mariadb.service" then that would not have worked. Since all systemctl commands were failing. But one could dig through the systemd service units and see what it does to stop the process and then do the same thing. I gave a quick browse through /lib/systemd/system/mariadb.service and it was not immediately apparent to me though. Bob