Disabling AV Scanning to free up resources

Submitted by rjrsinc on Tue, 04/24/2012 - 06:19 Pro Licensee

We are waiting on a new server to deploy, and in the meantime need to free up as much processing and resources as possible. So I would like to temporarily disable ClamAV but still keep spamassassin running. I used the disable button but got a warning that it was still configured for use, but disabled. I was concerned it may disrupt my email flow, slow I enabled it again. Can you provide the correct process to temporarily have Postfix bypass the ClamAV? We are using Pro 3.91

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Tue, 04/24/2012 - 08:38

Howdy -- you would first want to disable the Virus scanning feature for each of your existing Virtual Servers. You can do that by running this command from the command line:

virtualmin disable-feature --all-domains --virus

Once you do that, it would be safe to disable the Virus Scanning feature in System Settings -> Features and Plugins.

Submitted by rjrsinc on Tue, 04/24/2012 - 09:10 Pro Licensee

I'm only doing this to get more processing power since lookup-domain is killing our system. It launches about 200 instances when we get a flood of email and my load just shot up to 115 with 0% idle. It's shutting down apaches and other services. We are going to try to offload the spamassasin and ClamAV to a different VM while waiting for a new server, but this issue has been occurring for many weeks now. We're trying anything to save the server since lookup-domain is going crazy on us.

I assume I can enable ClamAV at a future time is we need and thought this was the safest to do to help currently. Any additional input would be greatly appreciated. I know some of the other open issues we have are dealing with this same "issue."

Submitted by andreychek on Tue, 04/24/2012 - 09:37

Well, the issue in your case is that we can't seem to reproduce that exact problem you're seeing on other systems.

Even when dealing with email blasts being sent to tens of thousands of users, we're not seeing the sort of lookup-domain behavior that you're seeing.

We are seeing SpamAssassin with a high load, and the Postfix queue works overtime during that, but lookup-domain hasn't generally been the issue.

So we haven't yet come up with a way to resolve that for you.

However, you can indeed re-enable ClamAV in the future, simply by changing that command from "disable-feature" to "enable-feature".