Search found 5 matches
- 31 Jul 2019 17:27
- Forum: 4.x Bugs
- Topic: Fresh install, failing with virus scanning
- Replies: 8
- Views: 9981
Re: Fresh install, failing with virus scanning
So, I decided to use a newer system. Core I5, 8gigs, SATA SSD. No errors to report. So, am I safe to assume that the Atom CPU just isnt powerful enough to process the clamav stuff? There is some timeout for the daemon to start, and I tried to adjust it for the Atom CPU. And it just would not work. R...
- 26 Jun 2019 14:36
- Forum: 4.x Bugs
- Topic: Fresh install, failing with virus scanning
- Replies: 8
- Views: 9981
Re: Fresh install, failing with virus scanning
4gigs
However, I'm wondering if my Atom(TM) CPU D510 could be part of the problem. Let me try another install using a spare core i5 box with 8gig.
However, I'm wondering if my Atom(TM) CPU D510 could be part of the problem. Let me try another install using a spare core i5 box with 8gig.
- 20 Jun 2019 15:06
- Forum: 4.x Bugs
- Topic: Fresh install, failing with virus scanning
- Replies: 8
- Views: 9981
Re: Fresh install, failing with virus scanning
I tried the solutions listed here: https://forum.efa-project.org/viewtopic.php?t=3128 enable_yararules was set to yes Didn't work for me, even after a reboot. Still getting this error: Clamd::ERROR:: COULD NOT CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON :: . Jun 20 11:00:09 XXXXXX MailScanner[6252...
- 19 Jun 2019 23:22
- Forum: 4.x Bugs
- Topic: Fresh install, failing with virus scanning
- Replies: 8
- Views: 9981
Re: Fresh install, failing with virus scanning
It's not the install that failed, and I should have been more clear about that. I added: TimeoutSec=900 to the bottom of: /usr/lib/systemd/system/clamd@.service And that seemed to get clamd up and running. Running systemctl status clamd@scan.service shows it running: ● clamd@scan.service - Generic c...
- 19 Jun 2019 18:43
- Forum: 4.x Bugs
- Topic: Fresh install, failing with virus scanning
- Replies: 8
- Views: 9981
Fresh install, failing with virus scanning
Fresh install. (Actually, the second time since the first failed with the same error). As soon as new email arrives and gets past the greylisting period, it gets stuck in queue. I see the following errors in maillog Jun 19 12:17:31 XXXXXXX MailScanner[1080]: Cannot find Socket (/var/run/clamd.socket...