clamav-users October 2011 archive
Main Archive Page > Month Archives  > clamav-users archives
clamav-users: Re: [clamav-users] clamd exits with libclamav erro

Re: [clamav-users] clamd exits with libclamav error

From: Chuck Swiger <cswiger_at_nospam>
Date: Tue Oct 18 2011 - 18:01:47 GMT
To: ClamAV users ML <>

On Oct 18, 2011, at 10:43 AM, Alex wrote:
> I've since learned there was a cooling problem with the processor and
> started receiving events like these on the host:
> kernel: [73788.355981] [Hardware Error]: Machine check events logged
> kernel: [73914.635576] CPU4: Package temperature above threshold, cpu
> clock throttled (total events = 5538406)
> kernel: [73914.635581] CPU0: Package temperature above threshold, cpu
> clock throttled (total events = 5538398)

Since your CPU had thermal protection, it's supposed to take effect before the hardware is permanently damaged, but the thermal stress might have affected it, or other components like memory or the PSU.

> I've since corrected the cooling issue, but am still receiving
> messages such as these on the kvm guest:
> [169245.360511] clamscan[27448] general protection ip:7f125f2e6ffb
> sp:7fff117566f0 error:0 in[7f125f229000+9ce000]
> [29016.445470] clamd[1110] general protection ip:30df2c3981
> sp:7fffa08f4fe0 error:0 in
> .11[30df200000+9ce000]

What OS? Looks to be Unix-style library names, but a Windows-style error messages? I'd expect a Unix platform to be logging a SIGSEGV or SIGBUS....

> I realize this may be a problem with the system and not specifically
> clamd or clamscan, but since that is how it is currently presenting
> itself, I thought someone may have some ideas of what is happening
> here?
> Is there any way to determine if the processor is permanently damaged
> due to overheating?
> Could this be related to library or system corruption caused by the
> processor overheating? I've reinstalled all the clam applications, and
> there haven't been any further messages in the logs except for this
> one clamscan line.

Your hardware manufacturer should have hardware diagnostics available which will identify anything obviously wrong. But running prime95 in test mode or memtest86 for 24 hours is a decent sanity check.

-- -Chuck _______________________________________________ Help us build a comprehensive ClamAV guide: visit