[Varnish] #1354: Segfault in libvgz.so

Varnish varnish-bugs at varnish-cache.org
Tue Oct 22 11:15:12 CEST 2013

#1354: Segfault in libvgz.so
 Reporter:  ixos    |       Owner:
     Type:  defect  |      Status:  new
 Priority:  high    |   Milestone:
Component:  build   |     Version:  3.0.4
 Severity:  major   |  Resolution:
 Keywords:          |

Comment (by ixos):

 Last panic at: Tue, 22 Oct 2013 06:38:05 GMT
 Assert error in vmod_ch_sighandler(), vmod_crashhandler.c line 13:
   Condition(You asked for it) not true.
 thread = (cache-worker)
 ident = Linux,3.10.9-xxxx-grs-
   0x439e6d: LCK_Init+1157
   0x43a142: LCK_Init+142c
   0x364fcc29230: _end+364fc592498
   0x364fda4c344: _end+364fd3b55ac
   0x364fda4ea11: _end+364fd3b7c79
   0x42db5d: VGZ_Gunzip+12c
   0x42f014: VGZ_Destroy+e0a
   0x42b709: FetchError+2c9
   0x42bef2: FetchStorage+4d8
   0x42cc60: FetchBody+436
 sp = 0x31237c3e008 {
   fd = 135, id = 135, xid = 1542650315,
   client = 60176,
   handling = deliver,
   err_code = 200, err_reason = (null),
   restarts = 0, esi_level = 0
   flags =  do_stream do_close is_gzip
   bodystatus = 3

 One more thing worth mention:
 I was suggested that it may be fault of 3rd part module. It isn't. I've
 tested it without any module and this panic occurs. Here are the panic in
 the same step STP_STREAMBODY/STP_STREAMDELIVER. It cannot be a coincident.
 Replying to [comment:3 martin]:
 > Could you try to install the libvmod-sigsegv on the server please? To do
 this you first need to compile the vmod for the varnish you're running,
 and then reference the vmod in your vcl ('import sigsegv'). This should
 cause a panic to happen when a seg fault is generated.
 > Regards,
 > Martin Blix Grydeland

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

More information about the varnish-bugs mailing list