[Varnish] #1352: Assert error in VEP_Init(), cache_esi_parse.c line 1001:#012 Condition((sp->wrk->vep) != 0) not true.
Varnish
varnish-bugs at varnish-cache.org
Wed Oct 2 11:33:23 CEST 2013
#1352: Assert error in VEP_Init(), cache_esi_parse.c line 1001:#012
Condition((sp->wrk->vep) != 0) not true.
--------------------+----------------------
Reporter: Smar | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: build | Version: unknown
Severity: normal | Resolution:
Keywords: |
--------------------+----------------------
Description changed by phk:
Old description:
> Hi,
>
> I got following assert error on a live server.
>
> Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) not responding to
> CLI, killing it.
> Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) died signal=6
> Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) Panic message:
> Assert error in VEP_Init(), cache_esi_parse.c line 1001:#012
> Condition((sp->wrk->vep) != 0) not true.#012thread = (cache-
> worker)#012ident =
> Linux,2.6.39-bpo.2-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll#012Backtrace:#012
> 0x439565: pan_backtrace+19#012 0x43983a: pan_ic+1ad#012 0x426f05:
> VEP_Init+bd#012 0x423c41: vfp_esi_begin+381#012 0x42b044:
> VFP_Begin+e2#012 0x42c6d6: FetchBody+45d#012 0x41bdd8:
> cnt_fetchbody+b90#012 0x41ebe1: CNT_Session+793#012 0x4276b6:
> ved_include+237#012 0x4284bf: ESI_Deliver+968#012sp = 0x7f9a3feee008
> {#012 fd = 37, id = 37, xid = 286162510,#012 client = 46.161.41.24
> 63058,#012 step = STP_FETCHBODY,#012 handling = deliver,#012 err_code
> = 200, err_reason = (null),#012 restarts = 0, esi_level = 1#012 flags =
> do_esi do_close is_gunzip#012 bodystatus = 5#012 ws = 0x7f9a3feee080 {
> #012 id = "sess",#012 {s,f,r,e} =
> {0x7f9a3feeec78,+2560,(nil),+65536},#012 },#012 http[req] = {#012 ws
> = 0x7f9a3feee080[sess]#012 "GET",#012
> "/index_part.php?get=community_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC&post=&HTTP_HOST
> =kara-
> koivukyla.nettipizza.eu&REQUEST_URI=%2Findex.php%3Fcommunity_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DbonusPros%26sortType%3DASC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC&QUERY_STRING=community_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DbonusPros%26sortType%3DASC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC",#012
> "HTTP/1.1",#012 "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MSIE
> 5.5; Windows 95) Opera 7.03 [de]",#012 "Accept: */*",#012
> "Cache-Control: max-age=259200",#012 "Connection: keep-alive",#012
> "Host: p
>
> Since it’s from syslog, it seems to be cut, but is this enough
> information to know what happened?
>
> That user agent is some kind of bot, most likely malicious, if it
> matters.
New description:
Hi,
I got following assert error on a live server.
{{{
Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) not responding to
CLI, killing it.
Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) died signal=6
Oct 2 02:01:58 varnish varnishd[3147]: Child (22377) Panic message:
Assert error in VEP_Init(), cache_esi_parse.c line 1001:
Condition((sp->wrk->vep) != 0) not true.
thread = (cache-worker)
ident = Linux,2.6.39-bpo.2-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll
Backtrace:
0x439565: pan_backtrace+19
0x43983a: pan_ic+1ad
0x426f05: VEP_Init+bd
0x423c41: vfp_esi_begin+381
0x42b044: VFP_Begin+e2
0x42c6d6: FetchBody+45d
0x41bdd8: cnt_fetchbody+b90
0x41ebe1: CNT_Session+793
0x4276b6: ved_include+237
0x4284bf: ESI_Deliver+968
sp = 0x7f9a3feee008 {
fd = 37, id = 37, xid = 286162510,
client = 46.161.41.24 63058,
step = STP_FETCHBODY,
handling = deliver,
err_code = 200, err_reason = (null),
restarts = 0, esi_level = 1
flags = do_esi do_close is_gunzip
bodystatus = 5
ws = 0x7f9a3feee080 {
id = "sess",
{s,f,r,e} = {0x7f9a3feeec78,+2560,(nil),+65536},
},
http[req] = {
ws = 0x7f9a3feee080[sess]
"GET",
"/index_part.php?get=community_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC&post=&HTTP_HOST
=kara-
koivukyla.nettipizza.eu&REQUEST_URI=%2Findex.php%3Fcommunity_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DbonusPros%26sortType%3DASC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC&QUERY_STRING=community_id%3D31%26city_id%3D74%26region_id%3D13124%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DbonusPros%26sortType%3DASC%26sort%3DarvostelutAvg%26sortType%3DASC%26sort%3DkumppaniToiminimiValue%26sortType%3DDESC",
"HTTP/1.1",
"User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows
95) Opera 7.03 [de]",
"Accept: */*",
"Cache-Control: max-age=259200",
"Connection: keep-alive",
"Host: p
}}}
Since it’s from syslog, it seems to be cut, but is this enough information
to know what happened?
That user agent is some kind of bot, most likely malicious, if it matters.
--
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1352#comment:1>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list