Discussion:
Assert error in ban_lurker_getfirst()
Hugues Alary
2018-07-17 23:35:23 UTC
Permalink
Hi there,

Today the varnish child panicked:

varnish> panic.show
200
Panic at: Tue, 17 Jul 2018 23:24:28 GMT
Assert error in ban_lurker_getfirst(), cache/cache_ban_lurker.c line 177:
Condition((oc->flags & OC_F_BUSY) == 0) not true.
version = varnish-6.0.0 revision a068361dff0d25a0d85cf82a6e5fdaf315e06a7d,
vrt api = 7.0
ident = Linux,4.14.22+,x86_64,-junix,-smalloc,-sdefault,-hcritbit,epoll
now = 582423.461242 (mono), 1531869856.455080 (real)
Backtrace:
0x561f9e331957: varnishd(+0x4a957) [0x561f9e331957]
0x561f9e396730: varnishd(VAS_Fail+0x40) [0x561f9e396730]
0x561f9e3154e9: varnishd(ban_lurker+0xba9) [0x561f9e3154e9]
0x561f9e350747: varnishd(+0x69747) [0x561f9e350747]
0x7fb783eda494: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)
[0x7fb783eda494]
0x7fb783c1cacf: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)
[0x7fb783c1cacf]
errno = 110 (Connection timed out)
thread = (ban-lurker)
thr.req = (nil) {
},
thr.busyobj = (nil) {
},

Any idea about what could have happened?

Cheers,
-Hugues
Dridi Boukelmoune
2018-09-25 09:15:23 UTC
Permalink
Found this unread thread in my inbox, I will reply here for completeness.
Post by Hugues Alary
Any idea about what could have happened?
Reported on github and fixed in 6.0.1 and 6.1.0, should be fixed as
part of the next 4.1 release:

https://github.com/varnishcache/varnish-cache/issues/2681

Thanks for reporting!

Loading...