[clamav-users] ClamAV 0.100.1 - clamd signal 11, leaves unix domain socket behind?

[Karl Pielorz]

--On 20 September 2018 15:44 +0000 "Micah Snyder (micasnyd)" 
<micasnyd at cisco.com> wrote:

> Clamd has a FixStaleSocket option that is default on.
> FixStaleSocket will unlink the lingering stale socket and bind again if
> it failed to bind when restarting clamd.

Hi, yeah - I saw that option.

> I all ears if anyone knows of a better way to remove the stale socket on
> death instead of on startup. As Ged Haywood suggested, your best option
> may be to have an ad-hoc watchdog script monitor clamd and kill the
> socket if clamd become unresponsive for too long.

Being simplistic, a sigsegv handler? :) [simplistic as it just fixes my 
case ]

> That said, if you figure out which file was killing clamd, I'd love to
> have a sample so I can try to fix the bug.  It would be very helpful.

I'd love to be able to do that - but the usual 'needle in a haystack', and 
that fact it's very intermittent isn't helping us much (nor the fact it 
gets delivered if it fails during the scan) - if I find it, you'll be the 
2nd person to know :) - I am still looking. I guess turning on coredumps 
might provide some info captured to disk - I'll post anything I find.

Thanks,

-Kp