Wonder if they are looking into it or if they are on vacation this time of year :)
Oddly enough I set av_avast = false just to disable it in the ini for now to see if it would stop. I restarted surgemail and it still is pegged at 100% off and on.
Steve,
we also confirm your observations. On a server with multiple cpu's, one cpu will be used by avast 100% for about 8 seconds and then is quiet. Avast process uses only 8% of memory and has very small I/O. Surgemail loafs along at 8-20%.
I notice that ~3 times a day we will get an "Important message from Surgemail" with the subject "Avast auto restart seems to have worked". There are alert emails from postmaster saying that avast has acted to stop an email with virus code in them, so avast appears to be working.
I only see 1 "vpipe failure" email alert per day. Every vpipe message is followed by a "avast successful restart" email, but not all avast restarts are preceded by a vpipe failure.
av_avast version 1.4, file date Nov 7 2011, Linux 21 x86_64, 6.9c-1
/usr/lib/libavastengine.so -> libavastengine-4.so.7.0.1
there have been 2 coredump/core.av_avast files in the last 3 days.
Larry
Cincinnati
===========================
--- Original message ---
Subject: Re: [SurgeMail List] av_avast high CPU
From: Steven <HIDDEN@wavedirect.org>
To: <surgemailHIDDEN@etwinsite.com>
Date: Monday, 04/13/2015 12:19 PM
Also on a side note I do get the occasional vpipe failure even though I've followed the advanced instructions for linux and completed them without any issues. The tests run fine too. I just get the notification that the vpipe fails on a regular basis.
From: "Steven Kenney" <HIDDEN@avedirect.org>
To: surgemail-list@netwinsite.com
Sent: Monday, April 13, 2015 8:41:16 AM
Subject: [SurgeMail List] av_avast high CPU
Since we updated to 6.9c-1 cpu usage has been through the roof. The culprit is the virus scanner. Also after the update it didn't quite work until we restarted a couple times. We noticed it adds a new line at the end of the process of restarting - " tcp_fix_ipv4 1". Probably unrelated.
Anyone else having issues with avast?
This is happening on both the mirror and primary servers.
