Print Page | Close Window

SpamFilterSvc uses 100% CPU

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
Printed Date: 18 December 2018 at 10:07pm

Topic: SpamFilterSvc uses 100% CPU
Posted By: tvanham
Subject: SpamFilterSvc uses 100% CPU
Date Posted: 06 October 2010 at 4:08am

Since october 1st (around 3.15pm GMT+1) the SpamFilter Service is showing strange behavior. The software has been updated to v4.2.4.834 several weeks before that so I'm guessing this is not the issue. The problem occurs on both our Windows Server 2003 and Windows Server 2008 systems.

After the service is started it takes several minutes (up to 30) before the service takes up the whole available CPU (go vCPU's ..) and doesn't let go of it. The incoming e-mail is processed without any delay but I am not quite sure why the service suddenly uses 100% CPU, this significantly slows down everything else (including logging in). There are no other services installed on the servers, they are both dedicated to spam filtering. (2003 for production, 2008 for testing).

It just seemed out both started to use 100% CPU at the same time, does anyone else recognize this behavior? If not, what would be the best way to track down this error? Does the SpamFilter has logging options besides the message logging?

Some help would be appreciated!

Posted By: LogSat
Date Posted: 06 October 2010 at 10:24pm

High CPU usage are very, vary rare, but unfortunately we have seen them in the past years - no software is ever bug free.

Is it possible for you to setup performance monitor running in the background, monitoring SpamFilter's process for CPU usage, with a sampling interval as short as you can safely (for performance and disk space) configure? Having a large number of samples may allow us to pinpoint with more accuracy the specific time at which the CPU increases, and hopefully cross-referincing SpamFilter's activity logfile will show if there's a specific email/IP/sender that could be causing this to happen.
It may take to reproduce more than one incident to pinpoint the issue, but we're of course here to help.
If you're able to proceed, you can email us at support at with any logs you may have so we can look into this.

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Print Page | Close Window