From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Vollmert Subject: bug#36389: odd Date: Wed, 26 Jun 2019 20:21:33 +0200 Message-ID: <828259BC-1B2F-4741-975F-7E9E842AB750@vllmrt.net> References: <249AC56B-BE05-4162-B65D-618490163CB0@vllmrt.net> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42514) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgCYY-0006NU-Ep for bug-guix@gnu.org; Wed, 26 Jun 2019 14:22:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hgCYW-0003CX-98 for bug-guix@gnu.org; Wed, 26 Jun 2019 14:22:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:51720) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hgCYU-0003BC-6A for bug-guix@gnu.org; Wed, 26 Jun 2019 14:22:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hgCYU-0005E2-0s for bug-guix@gnu.org; Wed, 26 Jun 2019 14:22:02 -0400 In-Reply-To: <249AC56B-BE05-4162-B65D-618490163CB0@vllmrt.net> Sender: "Debbugs-submit" Resent-Message-ID: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 36389@debbugs.gnu.org I agree that it sounds odd, and some of my original diagnostic must be skewed. After several configuration changes and system reconfigurations and nginx restarts, I do appear to have a sensible state currently, and I can=E2=80=99t reliably reproduce the problems I had before. I=E2=80=99m also pretty sure I didn=E2=80=99t imagine it all, though. Here=E2=80=99s something else I ran into while getting there: At some point, nginx was running, even after calling # herd stop nginx and herd did list it as stopped. That nginx instance that got away from shepherd might have been involved in the earlier trouble. (Is it ok for shepherd to lose track of a child like that?) Another thing was that I got a failed nginx configuration test that didn=E2=80=99t make sense. Notably, it complained that (a) the user directive `user nginx nginx;` is ineffective when when not running as root and (b) it didn=E2=80=99t have permission to access the letsencrypt keys. Both of these indicate that the configuration test was not run as root. I don=E2=80=99t see any reason in the code why that would happen=E2=80=A6 I=E2=80=99ll keep an eye on it and see if something similar occurs again.