From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id GHNCCkMLxmLhfgEAbAwnHQ (envelope-from ) for ; Thu, 07 Jul 2022 00:22:59 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id SLdlCUMLxmIAIAEAG6o9tA (envelope-from ) for ; Thu, 07 Jul 2022 00:22:59 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7FA9E3FAE2 for ; Thu, 7 Jul 2022 00:22:58 +0200 (CEST) Received: from localhost ([::1]:41626 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o9DQ9-000894-5C for larch@yhetil.org; Wed, 06 Jul 2022 18:22:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:60744) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o9D5u-0000SR-VO for bug-guix@gnu.org; Wed, 06 Jul 2022 18:02:07 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:33193) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o9D5u-0000co-Mf for bug-guix@gnu.org; Wed, 06 Jul 2022 18:02:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o9D5u-0008R5-IP for bug-guix@gnu.org; Wed, 06 Jul 2022 18:02:02 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#55898: jami service failing following 'guix deploy' update Resent-From: Maxim Cournoyer Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Wed, 06 Jul 2022 22:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55898 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: Maxime Devos Cc: GNU Debbugs , 55898@debbugs.gnu.org Received: via spool by 55898-submit@debbugs.gnu.org id=B55898.165714491732411 (code B ref 55898); Wed, 06 Jul 2022 22:02:02 +0000 Received: (at 55898) by debbugs.gnu.org; 6 Jul 2022 22:01:57 +0000 Received: from localhost ([127.0.0.1]:55321 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9D5p-0008Qf-B3 for submit@debbugs.gnu.org; Wed, 06 Jul 2022 18:01:57 -0400 Received: from mail-qt1-f169.google.com ([209.85.160.169]:37472) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9D5l-0008QK-K3; Wed, 06 Jul 2022 18:01:55 -0400 Received: by mail-qt1-f169.google.com with SMTP id i11so20269297qtr.4; Wed, 06 Jul 2022 15:01:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=0rvaPlqFPOPduEkxVAoLVsmjaVt4VYO7nub8kv3x5GE=; b=f7+C/Z0AHyGmn129G69jf3BBI8FbX5uvB4BPZ+2XjUSjIxdvmVGA1gV/sikD1RZuSq VzprYtBlqpZ+NF189sIJashXB5L/A8+XQIsS45AY70KouUDVywTS5JzlhFnWVabfn6gY h2rZoAfMl3vVxULG6zenEuPdMweLZ3yjrYVKdvGoOMuPQUdtMxibyNzJltJjzdIvSm8t hhdSYxkXNgk5lvqQ777XEH51mkcpaORr0RgHu7+h11gWf28vF9e4f/+jgZQhjEDHh1xp 2is+EMS06l1mbysyDU4La+5U/T8UF+prxI3tsVYbh06s/7h/C33wHoW1YX8JoYmk3YN+ fHYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=0rvaPlqFPOPduEkxVAoLVsmjaVt4VYO7nub8kv3x5GE=; b=C/yAvPFRWZrkwb/9V3xqPAbUNGckNziNzrtmMGFkH4H7DCSgYWt/Lkf36Rclc+TcFw vxrymx7u4TRKo5P2pSbVLUIEcU9uRP6NZwBZmu7znXIz2ZYRHy7N2I0t8W4WmgEhbRZN ESM9Ky6YYWBZJATOt9B85mlBt/tRdKSCNQePZ5mnt0DzEjwQd22us6BjUkSxmAscV4Cc llhe+KgBXO96OTDrBjCBOTkPWWZdYFkhzBT7fZSMBVL/dCiePZznEcVCg/PaAXorXUbO A51DcSe0VUdSaVR0tgul+esnobyWLj287jlUe6lb3RF9AnwT7sp/zF91b164mDv5/xmu wa6Q== X-Gm-Message-State: AJIora/r4v4oFqsqCOEiQkzLMKSU+PmRg0By8EKcwzjWpf/XOT2H5ION Fs6lsJfdL5k8fxs6rpuu8D5pdfqi0itwP2hr X-Google-Smtp-Source: AGRyM1u624e+H3hdtn/Na12o5Ku2mEliZ6OQ2Bx/ybWyXoE2W7XOvETcImt8ggNBOcdJGHa1I2inQQ== X-Received: by 2002:a05:622a:5cf:b0:31d:4c04:b642 with SMTP id d15-20020a05622a05cf00b0031d4c04b642mr15481037qtb.310.1657144907635; Wed, 06 Jul 2022 15:01:47 -0700 (PDT) Received: from hurd (dsl-10-134-148.b2b2c.ca. [72.10.134.148]) by smtp.gmail.com with ESMTPSA id bp10-20020a05622a1b8a00b0031d4044c464sm10003350qtb.46.2022.07.06.15.01.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Jul 2022 15:01:47 -0700 (PDT) From: Maxim Cournoyer References: <87a6ajg2zv.fsf@gmail.com> <5521716772922285f7c6bc381c82613026eebbd9.camel@telenet.be> <87bkuvdoe4.fsf@gmail.com> <87r13ex7nw.fsf_-_@gmail.com> <87mtdl2a7u.fsf_-_@gmail.com> Date: Wed, 06 Jul 2022 18:01:45 -0400 In-Reply-To: <87mtdl2a7u.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Wed, 06 Jul 2022 17:38:13 -0400") Message-ID: <87ilo9294m.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: "bug-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1657146178; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post: dkim-signature; bh=0rvaPlqFPOPduEkxVAoLVsmjaVt4VYO7nub8kv3x5GE=; b=h9y5kN8f/qPKb9xf/Oeh13hlF+2xw7Kh11zWvd8CmO08RxvqlfxeQBnqsWgBBwtDzqVYeY B0cBxfRbJncjkkbfFQu7u0g7aSnjNS1+Tw57qJvpnSkGdL83NXAqrMompr56QVivUHHsnP EQbaygzf9sKmkpROpDmS4GqeP2mHEAzOc28NutbKBdJTqsNMxAA60ML9Cz3XHF9aoPX3uW ZkiSSq7UuZ8NTH+nJrzQc4ElGpx3diJmw8tHuwVHKv9MBAB1LI5nzkCPjmwQDohuhUt+m6 krYyNfalDQRHgECvWdHa97ZUtzEZ7JOiShTrw2AEakyjFYuYxRc0O0XndMtRRw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1657146178; a=rsa-sha256; cv=none; b=YEVmFjAFMZA4SP9VAQPm2zN/Ewr77YPkuPyzklghGJMpWlZQ3MPhLqE3Lg3/dS+18Lah4/ FAdCiV39WzMHOyhBgSBmC9+9DS60WcMr+cOWCI517XNbxXqCfBNkfL2Jz7Zj98CeofzqyO QgY0hf6zCeaufa/snlKSwRCIihnLR0XjdCDNnZAeqpgu50hcp+HkH1aIZvidL+ArzS1A/1 pQZmhLysw0iNShoRPn8wgYIOy826/2M0ckQQOyq3C5rzjJ4IYBwNE7PDa6oKh2ROXHDWMG TnICy3ka3WT7CEmemiRbHb1hltxnCpFx4R52TuaTfzfwOgNG1mEe9oiaiYd3bQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b="f7+C/Z0A"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 5.25 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b="f7+C/Z0A"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 7FA9E3FAE2 X-Spam-Score: 5.25 X-Migadu-Scanner: scn0.migadu.com X-TUID: 38yiV7rAvNUG Hi again, [...] > Perhaps services should allow specifying the minimum required Shepherd > version, which Shepherd could ensure is met before attempting to restart > a service, printing something like: > > 'Could not restart service X due to unmet Shepherd version requirement; > the service will continue unchanged until the next reboot' > > or something similar. > > I've re-titled the bug, as this isn't specific to our jami service. I've asked in #systemd about what a similar situation would happen in systemd-land, and here's what I've learned: 1. service units aren't reloaded automatically after new versions of them are installed -- this effectively prevent the breakage seen here (the jami service was reloaded and restarting manually it caused it to fail). 2. a savvy user can still opt to force the new service to be reloaded via 'systemctl daemon-reload'. In case the service update depends on new systemd features, systemd would need to be restarted itself, via 'systemctl daemon-reexec'. The later command is interesting, but its documented as a debugging tool [0]: daemon-reexec Reexecute the systemd manager. This will serialize the manager state, reexecute the process and deserialize the state again. This command is of little use except for debugging and package upgrades. Sometimes, it might be helpful as a heavy-weight daemon-reload. While the daemon is being reexecuted, all sockets systemd listening on behalf of user configuration will stay accessible. [0] https://www.freedesktop.org/software/systemd/man/systemctl.html# systemd folks told me it is not typically run in systemd package upgrade hooks, but perhaps some distribution do this (I don't know). So the situation is not very different in systemd vs shepherd, except that we more aggressively load the new service definitions, potentially leading to breakage. Thoughts? Maxim