bug#28776: guix system reconfigure does not update path to nginx configuration

bug#28776: guix system reconfigure does not update path to nginx configuration

[Oleg Pykhalov]

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.

bug#28776: guix system reconfigure does not update path to nginx configuration

[Clément Lassieur]

Hi Oleg,

Oleg Pykhalov <go.wigust@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

bug#28776: guix system reconfigure does not update path to nginx configuration

[Oleg Pykhalov]

Hello Clement,

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

> Oleg Pykhalov <go.wigust@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 :-)

bug#28776: guix system reconfigure does not update path to nginx configuration

[Ludovic Courtès]

Hi Oleg,

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

> Clément Lassieur <clement@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’.