Sven Nierlein

I forgot to press the release button :-) It is here now

Indeed, i can reproduce that. Haven't noticed that so far, because we disable the object cache by setting: `object_cache_file=/dev/null` Which would be a workaround for you too. The object.cache is...

Took a bit, but should be fixed with #483

Disabling `enable_flap_detection` does not reset all existing flapping flags. It simply prevents new flapping flags from being set. But i agree, it should not prevent notifications from being sent out.

I don't think this is done aleady, but yes, that might be the way to go.

Thinking about it, simply resetting the flag might not be a good idea. The global `enable_flap_detection` flag can be (temporarily) changed by an external command. So this would result in...

Besides the quick fix from #452 we could think about slowly letting grow out the state history in case the host/service flapping flag is set, even if flapping detection is...

Besides restarting the worker, it would be pretty interesting to know why the worker fail. Is it reproducable? If so, maybe attaching strace to one of the workers might reveil...

just my 2 cents... * using the spoolfolder for decades now and never had any issue. If you experience segfaults with public APIs, please always open an issue. * send_gearman...

sounds like a "normal" object configration error to me. Have you tried: `naemonctl check`