varnishlog exists when sending SIGHUP

Bug #1597911 reported by Ruben Laban
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
varnish (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The currently shipped systemd unit file causes varnishlog to exit when SIGHUP is sent to it.

SIGHUP has two meanings for varnishlog:
 1) when running in daemon mode: reopen logfile
 2) when not running in daemon mode: exit

Since the current systemd unit file doesn't run varnishlog in daemon mode, a reload will result in a stop, instead of a reopen of the logfile.

This systemd unit file does work properly (for me, at least):

[Unit]
Description=Varnish HTTP accelerator log daemon
After=varnish.service

[Service]
RuntimeDirectory=varnishlog
Type=forking
User=varnishlog
Group=varnish
ExecStart=/usr/bin/varnishlog -D -a -w /var/log/varnish/varnish.log -P /run/varnishlog/varnishlog.pid
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/varnishlog/varnishlog.pid

[Install]
WantedBy=multi-user.target

Revision history for this message
Lasse Karstensen (lasse-6) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in varnish (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.