Closed huguesalary closed 6 years ago
this ban-luker induced panic is missing the vmod info. Could you please add the list of vmods you are using?
Of course, here's the top of my vcl file:
vcl 4.1;
import std;
import directors;
No other vmods are being used.
ok, that's harmless. Any chance you could use a build from current source or a weekly package?
never mind. Actually this looks pretty simple. Interesting to see this reported only now....
Glad I could help ;)
FTR, I'd say this was introduced with the fix for #1449 99851a10c7314dd6a4eb6a0de60161732b1b7b55 when we moved the ban insert before clearing the busy flag
Back ported to 4.1 as 7906a41782a39.
@nigoroll Should the test also include stolen objects? In other words, should we also have || oc->flags & OC_F_STOLEN
in there?
@hermunn , there is no OC_F_STOLEN
?
Sorry, please ignore me from now on. :)
A few weeks ago, varnish panicked:
I believe this panic happens on a rare basis.
Some more info:
Not sure that matters, but, Varnish is running inside a docker container.