Page 1 of 1

New Install Issue

Posted: 04 Sep 2018 20:03
by Frayre
After installing on Hyperv and configuring the appliance i noticed very slo performance and an email from Root@domain.com to clam with a subject of Cron <clam@EFA> [ -x /usr/bin/clamav-unofficial-sigs.sh ] && /bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null every 10 seconds. the machine has literally been up for 1 hour and received 87 email's from itself.
The ID is the same for all and if you open one up it seems to be repeating the same one over and over again...

any thoughts?

Re: New Install Issue

Posted: 05 Sep 2018 00:56
by shawniverson
That is a sign of trouble.
What are you seeing in /var/log/maillog?

Re: New Install Issue

Posted: 05 Sep 2018 13:21
by Frayre
Virus Scanning: No Virus Scanners Worked, so message batch was abandoned and retried!
Virus Scanning: Found 1 viruses
Spam Checks: Starting
Deleted 1 messages from Processing-database
MailWatch: Logging message 0381D10006D.A2954 to SQL
New Batch: Scanning 1 messages, 1156 bytes
Virus and Content Scanning: Starting
Clamd::ERROR:: COULD NOT CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON :: .
Virus Scanning: Clamd found 1 infections
Virus Scanning: No Virus Scanners Worked, so message batch was abandoned and retried!


The above message seems to repeat every 10 seconds or so. this is a fresh install all i did was import the VM, configure and update. that's when all this started. i haven't even started running mail through it. At first i thought Clamd::ERROR:: COULD NOT CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON :: . meant the vm couldn't reach something out on the web. but i don't see anything in my WatchGuard traffic monitor trying to reach out from that IP.

Thanks for all your help it's Greatly appreciated!

Re: New Install Issue

Posted: 05 Sep 2018 15:43
by Frayre
Think i got it figured out. while researching the issue i found another post viewtopic.php?t=3128 I had previously seen that but for some reason didn't think it applied. however after reviewing that post again i realized it was the same issue. so i followed the solution in the post and am now hopeful that will clear things up.