GNU logs - #36388, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#36388: nginx startup logging error, at odds with documentation
Resent-From: Robert Vollmert <rob@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 26 Jun 2019 05:19:02 +0000
Resent-Message-ID: <handler.36388.B.15615263331107 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 36388 <at> debbugs.gnu.org
From: Robert Vollmert <rob@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <A8BEB5E8-9002-4BE4-8CA3-99AA90819851@HIDDEN>
Date: Wed, 26 Jun 2019 07:18:38 +0200
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

The documentation states:

   At startup, =E2=80=98nginx=E2=80=99 has not yet read its =
configuration file, so it
uses a default file to log error messages.  If it fails to load its
configuration file, that is where error messages are logged.  After the
configuration file is loaded, the default error log file changes as per
configuration.  In our case, startup error messages can be found in
=E2=80=98/var/run/nginx/logs/error.log=E2=80=99, and after configuration =
in
=E2=80=98/var/log/nginx/error.log=E2=80=99.  The second location can be =
changed with the
LOG-DIRECTORY configuration option.

But I see:

creating nginx log directory '/var/log/nginx'
creating nginx run directory '/var/run/nginx'
creating nginx temp directories =
'/var/run/nginx/{client_body,proxy,fastcgi,uwsgi,scgi}_temp'
nginx: [alert] could not open error log file: open() =
"/gnu/store/byd116qs89b0am4zwjf4vjai7qlskvaw-nginx-1.17.0/logs/error.log" =
failed (2: No such file or directory)

It seems the documentation assumes nginx=E2=80=99s prefix directory is =
/var/run/nginx
instead of in the store. Some likely ways to improve this would be to =
pass
`-p /var/run/nginx` or `-g =E2=80=9Cerror_log =
/var/log/nginx/error.log=E2=80=9D` as command
line flags when starting nginx:

$ /gnu/store/byd116qs89b0am4zwjf4vjai7qlskvaw-nginx-1.17.0/sbin/nginx -h
nginx version: nginx/1.17.0
Usage: nginx [-?hvVtTq] [-s signal] [-c filename] [-p prefix] [-g =
directives]

Options:
  -?,-h         : this help
  -v            : show version and exit
  -V            : show version and configure options then exit
  -t            : test configuration and exit
  -T            : test configuration, dump it and exit
  -q            : suppress non-error messages during configuration =
testing
  -s signal     : send signal to a master process: stop, quit, reopen, =
reload
  -p prefix     : set prefix path (default: =
/gnu/store/byd116qs89b0am4zwjf4vjai7qlskvaw-nginx-1.17.0/)
  -c filename   : set configuration file (default: conf/nginx.conf)
  -g directives : set global directives out of configuration file

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Robert Vollmert <rob@HIDDEN>
Subject: bug#36388: Acknowledgement (nginx startup logging error, at odds
 with documentation)
Message-ID: <handler.36388.B.15615263331107.ack <at> debbugs.gnu.org>
References: <A8BEB5E8-9002-4BE4-8CA3-99AA90819851@HIDDEN>
X-Gnu-PR-Message: ack 36388
X-Gnu-PR-Package: guix
Reply-To: 36388 <at> debbugs.gnu.org
Date: Wed, 26 Jun 2019 05:19:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 36388 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
36388: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D36388
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#36388: activation?
References: <A8BEB5E8-9002-4BE4-8CA3-99AA90819851@HIDDEN>
In-Reply-To: <A8BEB5E8-9002-4BE4-8CA3-99AA90819851@HIDDEN>
Resent-From: Robert Vollmert <rob@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 26 Jun 2019 18:24:02 +0000
Resent-Message-ID: <handler.36388.B36388.156157341320279 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 36388 <at> debbugs.gnu.org
From: Robert Vollmert <rob@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <AF2533FB-3879-44EC-97E9-1CEA16660456@HIDDEN>
Date: Wed, 26 Jun 2019 20:23:23 +0200
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Could it be that the errors happen in the activation script,
but not when actually starting nginx? I see in the code that
we appear to pass a =E2=80=9C-p=E2=80=9D flag already when starting =
nginx;
maybe we should simply do the same when testing the config
during activation?=

Message sent to bug-guix@HIDDEN:

Subject: bug#36388: activation?
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Thu, 27 Jun 2019 15:22:02 +0000
Resent-Message-ID: <handler.36388.B36388.156164892232207 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Robert Vollmert <rob@HIDDEN>
Cc: 36388 <at> debbugs.gnu.org
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <A8BEB5E8-9002-4BE4-8CA3-99AA90819851@HIDDEN>
 <AF2533FB-3879-44EC-97E9-1CEA16660456@HIDDEN>
Date: Thu, 27 Jun 2019 17:21:47 +0200
In-Reply-To: <AF2533FB-3879-44EC-97E9-1CEA16660456@HIDDEN> (Robert
 Vollmert's message of "Wed, 26 Jun 2019 20:23:23 +0200")
Message-ID: <87r27fxddg.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi,

Robert Vollmert <rob@HIDDEN> skribis:

> Could it be that the errors happen in the activation script,
> but not when actually starting nginx? I see in the code that
> we appear to pass a =E2=80=9C-p=E2=80=9D flag already when starting nginx;
> maybe we should simply do the same when testing the config
> during activation?

Probably, that must be where the error comes from.

Ludo=E2=80=99.

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.