[Varnish] #1407: Varnishd loses the ability to write to shared memory if you try to start it twice
Varnish
varnish-bugs at varnish-cache.org
Tue Jan 14 16:55:23 CET 2014
#1407: Varnishd loses the ability to write to shared memory if you try to start it
twice
-----------------------------+----------------------
Reporter: brandonwamboldt | Type: defect
Status: new | Priority: normal
Milestone: | Component: varnishd
Version: 3.0.3 | Severity: normal
Keywords: |
-----------------------------+----------------------
If you start Varnish, and then try to start it again using the varnishd
command directly, it will take over the shared memory file from the
running varnishd process, then exit as it fails to bind ports. This leaves
the original process unable to write to shared memory.
It does throw a warning, "WARNING: Taking over SHMFILE marked as owned by
running process (pid=29585)", but I feel like this could be handled
better.
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1407>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list