|Main Archive Page > Month Archives > clamav-users archives|
A few days ago we were discussing a problem I was having with clamd
reporting a corrupt database.
>>>> Restarting won't help if the database is corrupted, or is there is some problem parsing the database.
>>> Correct, if you mess up a sig DB on a system, you've messed up the
>>> ClamAV on the system.
>>> And most of the time it doesn't log a thing, it just dies.
>>> Lots of fun. :-)
>> In my case, restarting does fix the problem.
>> Is there anything I should watch for, or do when it happens again? How
>> can I manually check the integrity of all the databases when it fails?
> Run clamscan /dev/null (or any file), and it will print an error if any database is wrong.
> Official databases have digital signatures, and clamscan (and freshclam) checks it.
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)
I've since corrected the cooling issue, but am still receiving
messages such as these on the kvm guest:
[169245.360511] clamscan general protection ip:7f125f2e6ffb
sp:7fff117566f0 error:0 in libclamav.so.6.1.11[7f125f229000+9ce000]
[29016.445470] clamd general protection ip:30df2c3981
sp:7fffa08f4fe0 error:0 in libclamav.so.6.1
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
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.
I'm hoping there are some smart people here that can tell me with
certainty that it is indeed the processor and I should replace it as
quickly as possible.