GNU bug report logs - #36517
'guix deploy' does not restart services

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36517 in the body.
You can then email your comments to 36517 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: bug-guix <at> gnu.org
Subject: 'guix deploy' does not restart services
Date: Fri, 05 Jul 2019 19:23:40 -0400

[Message part 1 (text/plain, inline)]

This issue is described in more detail at [1]. Essentially, 'guix
deploy' is will happily load and start new services, as well as unload
obsolete services, but does nothing to restart valid services that are
already running.

I can assign myself to this issue. Just filing for tracking purposes :]

Regards,
Jakob

[1]: https://lists.gnu.org/archive/html/guix-patches/2019-06/msg00567.html

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Thu, 11 Jul 2019 17:32:31 +0200

Hi,

zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:

> This issue is described in more detail at [1]. Essentially, 'guix
> deploy' is will happily load and start new services, as well as unload
> obsolete services, but does nothing to restart valid services that are
> already running.

That’s not a bug: ‘guix system reconfigure’ does not restart already
running services, simply because it cannot tell whether now is a good
time to restart them.  It’s a decision that’s left to the system
administrator.

However, note that ‘guix system reconfigure’ loads “replacements” for
each Shepherd service, such that next time you run ‘herd restart FOO’,
you spawn that new version of FOO.

Does that make sense?

Thanks,
Ludo’.

Message #11 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Thu, 11 Jul 2019 13:05:00 -0400

[Message part 1 (text/plain, inline)]

Hi, Ludovic!

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi,
>
> zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:
>
>> This issue is described in more detail at [1]. Essentially, 'guix
>> deploy' is will happily load and start new services, as well as unload
>> obsolete services, but does nothing to restart valid services that are
>> already running.
>
> That’s not a bug: ‘guix system reconfigure’ does not restart already
> running services, simply because it cannot tell whether now is a good
> time to restart them.  It’s a decision that’s left to the system
> administrator.
>
> However, note that ‘guix system reconfigure’ loads “replacements” for
> each Shepherd service, such that next time you run ‘herd restart FOO’,
> you spawn that new version of FOO.
>
> Does that make sense?

Yes, that does make sense. I suppose the way I worded the initial report
wasn't great; I opened this to track support for 'restart-strategy' as
described in #33508 in 'guix deploy'. This takes care of the question of
when a good time to restart the service would be.

Regards,
Jakob

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Fri, 12 Jul 2019 22:43:22 +0200

Howdy!

zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> Hi,
>>
>> zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:
>>
>>> This issue is described in more detail at [1]. Essentially, 'guix
>>> deploy' is will happily load and start new services, as well as unload
>>> obsolete services, but does nothing to restart valid services that are
>>> already running.
>>
>> That’s not a bug: ‘guix system reconfigure’ does not restart already
>> running services, simply because it cannot tell whether now is a good
>> time to restart them.  It’s a decision that’s left to the system
>> administrator.
>>
>> However, note that ‘guix system reconfigure’ loads “replacements” for
>> each Shepherd service, such that next time you run ‘herd restart FOO’,
>> you spawn that new version of FOO.
>>
>> Does that make sense?
>
> Yes, that does make sense. I suppose the way I worded the initial report
> wasn't great; I opened this to track support for 'restart-strategy' as
> described in #33508 in 'guix deploy'. This takes care of the question of
> when a good time to restart the service would be.

Oh, I see.  To me that’s completely orthogonal to ‘guix deploy’ though,
in that ‘guix system reconfigure’ and ‘guix deploy’ should use the same
code for that.

Thanks,
Ludo’.

Message #17 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Sat, 13 Jul 2019 13:14:40 -0400

[Message part 1 (text/plain, inline)]

Heyo,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Oh, I see. To me that’s completely orthogonal to ‘guix deploy’ though,
> in that ‘guix system reconfigure’ and ‘guix deploy’ should use the
> same code for that.
>
> Thanks,
> Ludo’.

Yeah, I believe it would be safe to close this once the code for 'guix
deploy' and 'guix system reconfigure' is unified. I opened this under
the impression that the two would remain separate and individual changes
would need to occur for both.

Regards,
Jakob

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Sat, 24 Aug 2019 15:22:01 +0200

Hi Jakob,

zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> Oh, I see. To me that’s completely orthogonal to ‘guix deploy’ though,
>> in that ‘guix system reconfigure’ and ‘guix deploy’ should use the
>> same code for that.
>>
>> Thanks,
>> Ludo’.
>
> Yeah, I believe it would be safe to close this once the code for 'guix
> deploy' and 'guix system reconfigure' is unified. I opened this under
> the impression that the two would remain separate and individual changes
> would need to occur for both.

Unless I’m mistaken, this bug can be closed now, right?

Thanks,
Ludo’.

Message #23 received at 36517 <at> debbugs.gnu.org (full text, mbox):

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 36517 <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Sat, 24 Aug 2019 13:44:00 -0400

[Message part 1 (text/plain, inline)]

Hi Ludovic,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Unless I’m mistaken, this bug can be closed now, right?

Yep! This can be closed now, since we're running the unified code and we
have another ticket for tracking this in 'guix system reconfigure'.

Regards,
Jakob

[signature.asc (application/pgp-signature, inline)]

Message #28 received at 36517-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
Cc: 36517-done <at> debbugs.gnu.org
Subject: Re: bug#36517: 'guix deploy' does not restart services
Date: Mon, 26 Aug 2019 10:19:40 +0200

zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> Unless I’m mistaken, this bug can be closed now, right?
>
> Yep! This can be closed now, since we're running the unified code and we
> have another ticket for tracking this in 'guix system reconfigure'.

Alrighty, done!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.