[Varnish] #1850: logrotate stops varnishncsa/varnishlog permanently under systemd.

Varnish varnish-bugs at varnish-cache.org
Mon Feb 1 15:33:05 CET 2016

#1850: logrotate stops varnishncsa/varnishlog permanently under systemd.
 Reporter:  lkarsten     |      Owner:
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  varnishncsa  |    Version:  4.1.1
 Severity:  normal       |   Keywords:
 In 4.1.1, varnishncsa and varnishncsa running from systemd will exit when
 receiving SIGHUP from (for example) logrotate.

 The official packaging for 4.1.1 runs varnishncsa and varnishlog in this

 Expected: varnishncsa and varnishlog daemons not to stop unintentionally
 every night.

 In #1794 there is a discussion about SIGHUP handling, and that the tools
 exit successfully in SIGHUP if they are running in foreground mode. This
 means that -D must be used for daemons.

 Possible workarounds:
 * Moving back to -D, which means we need a varnish:varnishlog owned
 directory in /run to write to.
 * Extending the daemons with chuid/chgid support. Write pidfile before
 dropping privs.

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1850>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list