[Varnish] #1289: varnishncsa segfault in libvarnishapi

Varnish varnish-bugs at varnish-cache.org
Fri Apr 5 15:48:24 CEST 2013

#1289: varnishncsa segfault in libvarnishapi
 Reporter:  tmagnien                                  |       Owner:
     Type:  defect                                    |      Status:  new
 Priority:  normal                                    |   Milestone:
Component:  varnishncsa                               |     Version:  3.0.3
 Severity:  normal                                    |  Resolution:
 Keywords:  varnishncsa segfault libvarnishapi vsl.c  |

Comment (by martin):

 Hi Thierry,

 I have had a look at that bug report, and this sounds to me very much like
 the log being overrun by varnishd. What will happen then is that
 varnishncsa while reading the log will see new log data being interpreted
 as previous pointers, easily creating a situation where the next log entry
 being pointed to is outside the log. There isn't today any clearly defined
 way for log readers to detect that they are lagging behind, so undefined
 behavior is to be expected if that happens.

 Could this be an explanation for what is happening? Where is the
 varnishncsa logging to? If that place can potentially stall, increasing
 the amount of logging space through the -l argument to varnishd might be a
 workaround that will help you.

 Martin Blix Grydeland

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1289#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list