all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36731@debbugs.gnu.org
Subject: bug#36731: shepherd lost track of nginx
Date: Sat, 20 Jul 2019 15:51:46 +0200	[thread overview]
Message-ID: <87d0i495l9.fsf@gnu.org> (raw)
In-Reply-To: <78D8D737-8D4D-485D-8388-AD014C669FB9@vllmrt.net> (Robert Vollmert's message of "Sat, 20 Jul 2019 09:42:34 +0200")

Hi,

Robert Vollmert <rob@vllmrt.net> skribis:

>>> $ sudo herd restart nginx
>>> Service nginx is not running.
>>> herd: exception caught while executing 'start' on service 'nginx':
>>> Throw to key `srfi-34' with args `("#<condition &invoke-error [program: \"/gnu/store/mlg0xfbiq03s812rm3v7mrlhyngas4xp-nginx-1.17.1/sbin/nginx\" arguments: (\"-c\" \"/gnu/store/r6gl9n7pwf4npiri05qxr40vdihdm2yy-nginx.conf\" \"-p\" \"/var/run/nginx\") exit-status: 1 term-signal: #f stop-signal: #f] 147e000>")’.
>> 
>> Do you use an “opaque” nginx config file, or do you use <nginx-...>
>> records?
>
> The latter I think:
>
>      (service nginx-service-type
>               (nginx-configuration
>                (extra-content “…”)))

That’s actually the non-opaque variant, so shepherd should read the PID
file and it shouldn’t get it wrong.  Not sure what happened.

If you can reproduce it, it would be great to gather the output of “herd
status nginx” at the time shepherd is confused.

Thanks,
Ludo’.

  reply	other threads:[~2019-07-20 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 16:49 bug#36731: shepherd lost track of nginx Robert Vollmert
2019-07-19 22:49 ` Ludovic Courtès
2019-07-20  7:42   ` Robert Vollmert
2019-07-20 13:51     ` Ludovic Courtès [this message]
2019-07-20 23:07   ` Mark H Weaver
2019-07-22 10:31     ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0i495l9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36731@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.