From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: GNU Debbugs <control@debbugs.gnu.org>, 55898@debbugs.gnu.org
Subject: bug#55898: jami service failing following 'guix deploy' update
Date: Wed, 06 Jul 2022 17:38:13 -0400 [thread overview]
Message-ID: <87mtdl2a7u.fsf_-_@gmail.com> (raw)
In-Reply-To: <87r13ex7nw.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Fri, 24 Jun 2022 14:01:23 -0400")
retitle 55898 Services depending on new Shepherd features may fail until
a reboot
thanks
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
> I'm suspecting that given the service makes use of Shepherd 0.9
> features, perhaps it fails loading and the error is reported erroneously
> that way... a reboot would tell but I'm not in a position to do that at
> this moment (remote machine).
I confirm that following a reboot, the service runs normally.
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.
Thanks!
Maxim
next prev parent reply other threads:[~2022-07-06 22:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 5:53 bug#55898: jami service failing following 'guix deploy' update Maxim Cournoyer
2022-06-11 14:51 ` Maxime Devos
2022-06-14 19:40 ` Maxim Cournoyer
2022-06-24 17:52 ` Maxim Cournoyer
2022-06-24 18:01 ` bug#55898: jami service failing following reconfigure Maxim Cournoyer
2022-07-06 21:38 ` Maxim Cournoyer [this message]
2022-07-06 22:01 ` bug#55898: jami service failing following 'guix deploy' update Maxim Cournoyer
2022-07-20 21:19 ` bug#55898: Services depending on new Shepherd features may fail until reboot Ludovic Courtès
2022-07-21 4:10 ` Maxim Cournoyer
2022-08-29 13:43 ` Ludovic Courtès
2022-08-29 21:06 ` Maxim Cournoyer
2022-08-30 7:33 ` Ludovic Courtès
2022-08-30 9:35 ` Maxime Devos
2022-08-30 13:50 ` Ludovic Courtès
2022-09-01 13:18 ` Maxim Cournoyer
2022-09-01 13:28 ` Maxime Devos
2022-09-01 13:51 ` Ludovic Courtès
2022-09-01 19:16 ` Maxim Cournoyer
2022-09-02 9:10 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtdl2a7u.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=55898@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).