action #46880
closed[sle][security] clamav module update
Added by mloviska about 5 years ago. Updated about 5 years ago.
0%
Description
As it is described in below bug report, we should run sigtool tests on the database file before starting clamd and freshclam.
https://bugzilla.suse.com/show_bug.cgi?id=1121845#c1
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/clamav.pm
Updated by okurz about 5 years ago
- Subject changed from [sle][functional][u] clamav module update to [sle][security] clamav module update
- Assignee set to sunyan
Test module maintainer is still "Wei Jiang wjiang@suse.com", should be updated as well.
@sunyan can you please help to find a new test module maintainer and also assign the ticket to the right person for updating the clamav module according to the mentioned bug?
Updated by okurz about 5 years ago
- Category changed from Enhancement to existing tests to Bugs in existing tests
- Priority changed from Low to High
- Target version changed from Milestone 26 to Milestone 23
Setting to "High" as linked to currently failing tests, e.g. https://openqa.suse.de/tests/2517691#step/clamav/7 as one example from the latest SLE15SP1 build
Updated by whdu about 5 years ago
- Status changed from In Progress to Resolved
Updated by okurz about 5 years ago
- Has duplicate action #48902: [sle][functional][u] openQA test fails in clamav - systemctl start clamd.service failed added
Updated by okurz about 5 years ago
- Status changed from Resolved to Feedback
hi, could you please check the latest, retriggered job in the scenario mentioned in #46880#note-4 -> https://openqa.suse.de/tests/2525047#step/clamav/12 . Could be this is a follow-up issue or still the same.
Updated by whdu about 5 years ago
okurz wrote:
hi, could you please check the latest, retriggered job in the scenario mentioned in #46880#note-4 -> https://openqa.suse.de/tests/2525047#step/clamav/12 . Could be this is a follow-up issue or still the same.
From journald log:
Mar 07 07:13:33 susetest freshclam[11038]: Your ClamAV installation is OUTDATED!
Mar 07 07:13:33 susetest freshclam[11038]: Local version: 0.100.2 Recommended version: 0.101.1
Mar 07 07:13:33 susetest freshclam[11038]: DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
...
Mar 07 07:13:33 susetest clamd[11039]: Bytecode: Security mode set to "TrustSigned".
Mar 07 07:15:04 susetest systemd[1]: clamd.service: Start operation timed out. Terminating.
Mar 07 07:15:04 susetest systemd[1]: Failed to start Clamav antivirus Deamon.
Mar 07 07:15:04 susetest systemd[1]: clamd.service: Unit entered failed state.
I don't think it is the clamav version issue which prevented it's starting. So I can not find anything valuable from journald log for the reason of timeout. I suppose it is worker performance or product issue.
Updated by okurz about 5 years ago
Ok. I am not exactly sure what you mean with "worker performance" in this context as the test looks like doing everything correctly but the service does not start up properly (in time). Will you further look into this and report as product issue, implement a workaround and/or fix the test?
Updated by whdu about 5 years ago
It was failed on Build 188.1 again. I am going to take an investigation.
Updated by whdu about 5 years ago
I can not reproduce this issue on my own environment. It is not a product bug. Still need more investigations.
Updated by whdu about 5 years ago
- Related to action #49133: [functional][u][sle][security][sle15sp1] test fails in clamav - clamd starting timeout added
Updated by whdu about 5 years ago
- Status changed from Feedback to Resolved
I enlarged systemctl timeout for clamd.service only by creating a runtime override. Now it works well.
See https://openqa.suse.de/tests/2548985#step/clamav/18
(Turn out it took around 140 seconds to start clamd, quite a long duration.)