[Varnish] #1824: Varnish.service should be using type=notify

Varnish varnish-bugs at varnish-cache.org
Fri Nov 27 09:40:25 CET 2015

#1824: Varnish.service should be using type=notify
 Reporter:  zmyrgel  |       Type:  defect
   Status:  new      |   Priority:  normal
Milestone:           |  Component:  varnishd
  Version:  4.0.3    |   Severity:  normal
 Keywords:  systemd  |
 I'm running several Varnishd / varnishncsa instances on our RHEL 7
 There seems to be incorrect assumptions in the varnish.service systemd
 file about starting of varnishd.
 The service file uses Type=forking.
 As far as I've understood, this makes Varnishd fork and that will signal
 that the Varnishd is ready and running.
 Problem appears to be with VSM files. The VSM files are not necessarily
 ready when Varnishd reports itself ready. This makes following Varnishncsa
 processes fail with messsages:
  Can't open VSM file (Abandoned VSM file (Varnish not running?)

 What I've gathered the from looking at systemd is that Varnishd process
 should use systemd's
 sd_notify(3)] to signal when the VSM is ready.

 I'm making assumption here that running multiple varnish instances on same
 computer makes the creation of VSM files slower which causes the issue to
 pop up.

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

More information about the varnish-bugs mailing list