[Pkg-nginx-maintainers] Bug#863602: nginx: Restart should check conf files before stopping service

Olaf van der Spek olafvdspek at gmail.com
Mon May 29 07:40:33 UTC 2017


Subject: nginx: Restart should check conf files before stopping service
Package: nginx
Version: 1.10.3-1
Severity: normal

Dear Maintainer,

1. A conf file was edited, a bug was inserted but it wasn't loaded.
2. A (letsencrypt) script invoked a service restart (maybe it
shouldn't), but the service didn't come backup due to the bug in the
conf file.

I think the conf files should be checked in restart before the old
service is stopped.
Perhaps even better, but I'm not sure if systemd and nginx supports
this, would be for the new instance to be fully started before the old
one is stopped.

Gr,

Olaf

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nginx depends on:
ii  nginx-full  1.10.3-1

nginx recommends no packages.

nginx suggests no packages.

-- no debconf information



More information about the Pkg-nginx-maintainers mailing list