Hi Jochen,

thanks for the reply.

On Sat, Dec 21, 2019 at 07:06:24PM +0100, Jochen Neumeister wrote:
> Hi,
>
> you're not allone with this Problem.
> Other nginx user have the same Problem:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626
>
> Unfortunately I have no solution for the problem at the moment

I'm not on position to think these two issues are similar.
Here, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626#c20
the originator has clear replied he has the issue on 12.1 amd64
and on 11.1 everything looks fine.

In this case we have FreeBSD 11.3 on ppc64, nginx has been built
with gcc9, not from ports.

So, my recommendation is still the same as before: build nginx from
ports tree with debug log enabled. Once compiled, it's possible to
use the following directive on the main level to enable debug logging:

error_log /var/log/nginx/error.log debug;

--
Sergey


> Am 20.12.19 um 18:31 schrieb Sergey A. Osokin:
> > Hi Luciano,
> >
> > hope you're doing well.
> >
> > As far as I understood you're running nginx on FreeBSD 11.3 ppc64.
> > It looks like it's nginx from mainline 1.17 branch.
> >
> > I would recommend to build nginx from FreeBSD ports collection,
> > please see www/nginx-devel for details.
> >
> > In this case nginx builds with the following option:
> >
> > [ ] DEBUGLOG Enable debug log (--with-debug)
> >
> > it's possible to enable debug log in nginx.conf configuration
> > file.
> >
> > Thanks.
> >
> > --
> > Sergey Osokin
> >
> > On Fri, Dec 20, 2019 at 06:21:42PM +0100, Luciano Mannucci wrote:
> >> On Fri, 20 Dec 2019 16:23:26 +0100
> >> Luciano Mannucci <luciano@vespaperitivo.it> wrote:
> >>
> >>> I have an istallation of nginx in a FreeBSD PPC64 server (running
> >>> 11.3 RELEASE) which seems to ignore kill -HUP: it doesn't reload
> >>> configuration and doesn't log the fact that kill has reached it, even
> >>> if I set the debug level in error_log to "debug".
> >> Further investigation: it does re-read the config.
> >> It just doesn't log that it did it.
> >>
> >> This may be a problem because *sometime* it doesn't reload the ssl
> >> certificates not noticing that they have changed.
> >>
> >> Do I need to put something special in the conf file to achieve that?
> >>
> >> Thanks again,
> >>
> >> Luciano.
> >> --
> >> /"\ /Via A. Salaino, 7 - 20144 Milano (Italy)
> >> \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250
> >> X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG
> >> / \ AND POSTINGS / WWW: http://www.lesassaie.IT/
> >> _______________________________________________
> >> nginx mailing list
> >> nginx@nginx.org
> >> http://mailman.nginx.org/mailman/listinfo/nginx
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx