bug#49205: closed ([services]: nginx doesn't restart after guix system reconfigure)

[GNU bug Tracking System]

Your message dated Fri, 30 Jun 2023 19:38:18 -0700
with message-id 
<CAFHYt57R+vNHMuBMELruh9FzfT+r12jZ1BqUfQUt6sJqqGn8Pg@mail.gmail.com>
and subject line Closing Bug#49205: Usually caused by misconfigurations of Nginx
has caused the debbugs.gnu.org bug report #49205,
regarding [services]: nginx doesn't restart after guix system reconfigure
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
49205: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49205
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [services]: nginx doesn't restart after guix system reconfigure Date: Thu, 24 Jun 2021 07:35:35 -0400

Hello Guix!

I am using certbot-service-type which also brings in nginx service. Upon `guix system reconfigure`, I get the following:

guix system: warning: exception caught while executing 'start' on service 'nginx': Throw to key `%exception' with args `("#<&invoke-error program: \"/gnu/store/g6nhdp7i1sr51anq86hd6adrsm5ha857-nginx-1.21.0/sbin/nginx\" arguments: (\"-c\" \"/gnu/store/2igpjf27rm92np6jn6hfrxzx5m55a468-nginx.conf\" \"-p\" \"/var/run/nginx\") exit-status: 1 term-signal: #f stop-signal: #f>")'.

Regards,
RG.

OpenPGP_signature
Description: OpenPGP digital signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Closing Bug#49205: Usually caused by misconfigurations of Nginx
>
>
>
>
> Date: 
>
> Fri, 30 Jun 2023 19:38:18 -0700
>
>
>
>
> Hi,
>
> I have also seen this error several times. In my experience, it is
> almost always caused by a misconfiguration of Nginx.
>
> On my equipment, there is an exception to that rule when Nginx serves
> outside connections as a reverse proxy to the local network, i.e.
> something like: [1]
>
> (body (list
>   "proxy_pass http://lechner-desktop.us-core.com:3011;";
>   "proxy_set_header Host $host;"
>   "proxy_set_header X-Real-IP $remote_addr;"
>   "proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;"))
>
> but that's somewhat exotic. It triggers a "host not found" in the logs.
>
> My particular failure may have to do with the service ordering in
> Shepherd, although I have not been able to fix it. For example, the
> default prerequisites for Nginx do not even include 'networking. [2]
> Either way, Nginx is configured to respawn, so my bug is probably
> elsewhere.
>
> Closing this issue.
>
> Kind regards
> Felix
>
> [1] 
> https://codeberg.org/lechner/system-config/src/commit/fca07b73068b043d57930266a2102af05b0b0aa9/host/wallace-server/operating-system.scm#L892-L895
> [2] 
> https://codeberg.org/lechner/guix/src/commit/f25529b08e356f89ca7cecc44295085531a8faba/gnu/services/web.scm#L567
>
>
> --- End Message ---