From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Raghav Gururajan <rg@raghavgururajan.name>, 49205@debbugs.gnu.org
Subject: bug#49205: [services]: nginx doesn't restart after guix system reconfigure
Date: Fri, 09 Dec 2022 10:14:38 +0100 [thread overview]
Message-ID: <87y1rh9bwh.fsf@gnu.org> (raw)
In-Reply-To: <87v963ru82.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 24 Jun 2021 20:30:21 +0200")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Raghav Gururajan via Bug reports for GNU Guix 写道:
>> 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>")'.
>
> The shortest answer is to run this command manually and see what it
> prints out. So
>
> $ sudo /gnu/store/g6n…/sbin/nginx -c /gnu/store/… -p /var/run/nginx
>
> in a terminal.
These days, with the Shepherd 0.9.3, the stdout/stderr or nginx is
captured in /var/log/messages when it starts. That should make it
easier to debug startup failures.
If you don’t have more info on this bug Raghav (it’s been some time…), I
suggest we close it.
> I saw you mention nginx and certbot in #guix. It's unfortunately
> common to end up in a catch-22 with Guix's nginx and certbot services
> when using HTTP authentication, where nginx needs to be running to
> receive your first certificate but refuses to start because of missing
> certificates…
I wonder how we could address that.
Ludo’.
next prev parent reply other threads:[~2022-12-09 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 11:35 bug#49205: [services]: nginx doesn't restart after guix system reconfigure Raghav Gururajan via Bug reports for GNU Guix
2021-06-24 18:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-12-09 9:14 ` Ludovic Courtès [this message]
2023-07-01 2:38 ` bug#49205: Closing Bug#49205: Usually caused by misconfigurations of Nginx Felix Lechner via Bug reports for GNU Guix
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=87y1rh9bwh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=49205@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=rg@raghavgururajan.name \
/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).