ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018081ClearOSclamavpublic2017-12-03 14:552018-02-12 09:31
ReporterNickH 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.4.0 
Target Version7.4.0 UpdatesFixed in Version 
Summary0018081: clearsdn-antimalware since 29/11/2017 potentially stop clamav from starting
DescriptionSince clearsdn-antimalware-6.1-20171128.1025.noarch, the start time for clamd has doubled. In my case it has gone from 10s to about 19s on a Core i3-4130 machine. On a slower n3150 machine on the forum (https://www.clearos.com/clearfoundation/social/community/clamd-start-up-times-out# [^]) start up times went from40s to over 90s. Unfortunately systemd has a 90s timeout after which it will fail an app rather than keep trying to start it.

Can the rules be investigated? Alternatively, can a timeout override be put into the startup file, /usr/lib/systemd/system/clamd.service? Details are in the accepted answer in the forum post.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-12-03 14:55NickHNew Issue
2017-12-05 08:24user2Statusnew => confirmed
2017-12-05 08:24user2Categoryapp-antivirus - Gateway Antivirus => clamav
2017-12-05 08:35user2Note Added: 0006811
2017-12-05 08:36user2Target Version => 7.4.0 Updates
2017-12-05 12:02user2Statusconfirmed => resolved
2017-12-05 12:02user2Resolutionopen => fixed
2017-12-05 12:02user2Assigned To => user2
2018-02-12 09:31user2Statusresolved => closed

Notes
(0006811)
user2   
2017-12-05 08:35   
The blurl.ndb signature database increased from about 10,000 to 40,000 signatures. Removing that particular signature file will improve the start time for ClamAV, however, that's not recommended. As a workaround, we can add the TimeoutStartSec parameter to the systemd configlet, but that change might get reverted in ClearOS 8.

Note: we're adding a tool to help protect users from adding resource-intensive apps (see https://www.clearos.com/resources/documentation/clearos/content:en_us:6_b_system_requirements#size_requirements [^]) to low-memory systems -- tracker 0017821. We might have to expand the scope to include compute power too -- ClamAV needs quite a bit of horsepower!