GNU bug report logs - #28776
guix system reconfigure does not update path to nginx configuration

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 28776 in the body.
You can then email your comments to 28776 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: Oleg Pykhalov <go.wigust <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: guix system reconfigure does not update path to nginx configuration
Date: Tue, 10 Oct 2017 12:37:24 +0300

Hello Guix,

After changing config.scm, herd restarts NGINX with previous (on boot)
configuration (checked with ps).  So to apply a new NGINX configuration
to a system, reboot is required.

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

From: Clément Lassieur <clement <at> lassieur.org>
To: Oleg Pykhalov <go.wigust <at> gmail.com>
Cc: 28776 <at> debbugs.gnu.org
Subject: Re: bug#28776: guix system reconfigure does not update path to nginx
 configuration
Date: Tue, 10 Oct 2017 12:47:28 +0200

Hi Oleg,

Oleg Pykhalov <go.wigust <at> gmail.com> writes:

> After changing config.scm, herd restarts NGINX with previous (on boot)
> configuration (checked with ps).  So to apply a new NGINX configuration
> to a system, reboot is required.

Quoting Ludovic from:
https://lists.gnu.org/archive/html/guix-patches/2017-05/msg00669.html

--8<---------------cut here---------------start------------->8---
Currently ‘guix system reconfigure’ (specifically
‘upgrade-shepherd-services’) reloads and starts all services that are
currently stopped, on the grounds that it would not be safe/desirable to
simply stop any running service.
--8<---------------cut here---------------end--------------->8---

So if you want NGINX to start with its new configuration, you need to
stop it before doing the 'guix system reconfigure'.

Clément

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

From: Oleg Pykhalov <go.wigust <at> gmail.com>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 28776 <at> debbugs.gnu.org
Subject: Re: bug#28776: guix system reconfigure does not update path to nginx
 configuration
Date: Tue, 10 Oct 2017 13:58:46 +0300

Hello Clement,

Clément Lassieur <clement <at> lassieur.org> writes:

> Oleg Pykhalov <go.wigust <at> gmail.com> writes:
>
>> After changing config.scm, herd restarts NGINX with previous (on boot)
>> configuration (checked with ps).  So to apply a new NGINX configuration
>> to a system, reboot is required.
>
> Quoting Ludovic from:
> https://lists.gnu.org/archive/html/guix-patches/2017-05/msg00669.html
>
> Currently ‘guix system reconfigure’ (specifically
> ‘upgrade-shepherd-services’) reloads and starts all services that are
> currently stopped, on the grounds that it would not be safe/desirable to
> simply stop any running service.
>
> So if you want NGINX to start with its new configuration, you need to
> stop it before doing the 'guix system reconfigure'.

Thank you for giving a direction!  I actually tried to make 'sudo herd
restart nginx' after reconfigure,  but apparently it's wrong.

I'm not sure if we need to close this bug.  It wasn't obvious to
me that it related to subject “Allow services to implement a 'reload'
action”, because I tried to reload it manually :-)

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

From: ludo <at> gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust <at> gmail.com>
Cc: 28776 <at> debbugs.gnu.org,
 Clément Lassieur <clement <at> lassieur.org>
Subject: Re: bug#28776: guix system reconfigure does not update path to nginx
 configuration
Date: Wed, 11 Oct 2017 15:25:30 +0200

Hi Oleg,

Oleg Pykhalov <go.wigust <at> gmail.com> skribis:

> Clément Lassieur <clement <at> lassieur.org> writes:

[...]

>> Quoting Ludovic from:
>> https://lists.gnu.org/archive/html/guix-patches/2017-05/msg00669.html
>>
>> Currently ‘guix system reconfigure’ (specifically
>> ‘upgrade-shepherd-services’) reloads and starts all services that are
>> currently stopped, on the grounds that it would not be safe/desirable to
>> simply stop any running service.
>>
>> So if you want NGINX to start with its new configuration, you need to
>> stop it before doing the 'guix system reconfigure'.
>
> Thank you for giving a direction!  I actually tried to make 'sudo herd
> restart nginx' after reconfigure,  but apparently it's wrong.
>
> I'm not sure if we need to close this bug.  It wasn't obvious to
> me that it related to subject “Allow services to implement a 'reload'
> action”, because I tried to reload it manually :-)

The behavior of ‘reconfigure’ is not ideal, which is why Clément started
working on improving it.

However, what you report here is intended, so I’ll just close as
“not-a-bug”.

Thank you,
Ludo’.

Previous Next

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