Assert error in vfp_esi_bytes_gg()

[Benjamin Jorand]

We have been able to solve this issue : vcl lacked a library include for
some C code. Check that vcl can be loaded without warning
(varnishadm vcl.load)

Le 21 février 2012 18:08, Benjamin Jorand <benjamin.jorand at gmail.com> a
écrit :

> Hello,
>
> Same issue here with varnish 3.0.2.
>
> Syslog output :
>
> Feb 21 15:28:15 xo varnishd[11230]: Child (16362) died signal=6
> Feb 21 15:28:15 xo varnishd[11230]: Child (16362) Panic message: Assert
> error in vfp_esi_bytes_gg(), cache_esi_fetch.c line 273:   Condition(i >=
> VGZ_OK) not true. thread = (cache-worker) ident =
> Linux,2.6.35.13,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace:
> 0x42e678: /usr/sbin/varnishd() [0x42e678]   0x41d315: /usr/sbin/varnishd()
> [0x41d315]   0x41d45b: /usr/sbin/varnishd() [0x41d45b]   0x4237ab:
> /usr/sbin/varnishd(FetchBody+0x98b) [0x4237ab]   0x417ff0:
> /usr/sbin/varnishd() [0x417ff0]   0x418f95:
> /usr/sbin/varnishd(CNT_Session+0x5d5) [0x418f95]   0x430e28:
> /usr/sbin/varnishd() [0x430e28]   0x42fff9: /usr/sbin/varnishd() [0x42fff9]
>   0x7f245a5928ba: /lib/libpthread.so.0(+0x68ba) [0x7f245a5928ba]
> 0x7f245a2fa02d: /lib/libc.so.6(clone+0x6d) [0x7f245a2fa02d] sp =
> 0x7f1c75f2e008 {   fd = 72, id = 72, xid = 1178213161,   client = xxxxx
> 51138,   step = STP_FETCHBODY,   handling = deliver,   err_code = 206,
> err_reason = (null),   restarts = 0, esi_level = 0   flags =  do_esi do
> Feb 21 15:28:15 xo varnishd[11230]: Child cleanup complete
> Feb 21 15:28:15 xo varnishd[11230]: child (29746) Started
> Feb 21 15:28:15 xo varnishd[11230]: Child (29746) said Child starts
>
> Thanks,
>
> Le 17 février 2012 14:50, Pablo Román <pablo at thenextweb.com> a écrit :
>
>> Hi there,
>>
>> I'm having the same issue described above regarding Vanish dying with the
>> error: Panic message: Assert error in vfp_esi_bytes_gg(),
>> cache_esi_fetch.c line 273:#012  Condition(i >= VGZ_OK) not true.
>>
>> In my case, it happens only when a certain url pattern is met. This
>> pattern should normally resolve with a 404, but instead the server responds
>> with an Error 324 (net::ERR_EMPTY_RESPONSE) and then Varnish dies,
>> throwing the aforementioned error. I'm using Varnish 3.0.2 with ESI. Has
>> someone experienced this before or have any tips on how to debug it?
>>
>> Thanks,
>>
>> --
>> ---
>>
>> Pablo Román
>> http://thenextweb.com
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
>
> --
> Benjamin Jorand (benjamin.jorand at gmail.com)
> +33.681460331
>



-- 
Benjamin Jorand (benjamin.jorand at gmail.com)
+33.681460331
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120221/3e46e77d/attachment-0001.html>