Mailscanner max'd out CPU/memory and not processing mail

Tom Rogers mailscanner at generalgau.com
Fri Mar 7 02:49:29 GMT 2008


"Check for hardware faults. Does /proc/meminfo still agree with you on the
amount of RAM in the box, for example?"

Yes.

root at fatman:/home/tom# cat /proc/meminfo
MemTotal:       516048 kB
MemFree:        426620 kB
Buffers:         18412 kB
Cached:          37576 kB
SwapCached:       9316 kB
Active:          35732 kB
Inactive:        37024 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       516048 kB
LowFree:        426620 kB
SwapTotal:     1572856 kB
SwapFree:      1504472 kB
Dirty:             148 kB
Writeback:           0 kB
AnonPages:       12728 kB
Mapped:           7576 kB
Slab:            10104 kB
SReclaimable:     3372 kB
SUnreclaim:       6732 kB
PageTables:       1160 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   1830880 kB
Committed_AS:   293188 kB
VmallocTotal:   507896 kB
VmallocUsed:      3776 kB
VmallocChunk:   504004 kB

"What virus scanners are you using?"

F-Prot.  I have ClamAV installed, but don't use it.

'Run "MailScanner --lint" '

root at fatman:/home/tom# MailScanner --lint
Read 759 hostnames from the phishing whitelist
Config: calling custom init function SQLBlacklist
Config: calling custom init function MailWatchLogging
Config: calling custom init function SQLWhitelist
MailScanner setting GID to  (119)
MailScanner setting UID to  (111)

Checking for SpamAssassin errors (if you use it)...
lock.pl sees Config  LockType =  flock
lock.pl sees have_module =  0
Using locktype = flock
MailScanner.conf says "Virus Scanners = f-prot"
Found these virus scanners installed: f-prot, clamavmodule


root at fatman:/home/tom# cat /etc/passwd | grep 119
postfix:x:111:119::/var/spool/postfix:/bin/false

'as well as "MailScanner --debug" to check things out.'

root at fatman:/home/tom# MailScanner --debug
In Debugging mode, not forking...



On Thu, 06 Mar 2008 22:11:20 +0000, Julian Field wrote
> Check for hardware faults. Does /proc/meminfo still agree with you 
> on the amount of RAM in the box, for example?
> 
> Sounds like you've already got 'Use SpamAssassin = no'. What virus 
> scanners are you using? If you are using clamavmodule, I would 
> switch to clamd if you can on your distro.
> 
> Run "MailScanner --lint" as well as "MailScanner --debug" to check 
> things out.
> 
> Tom Rogers wrote:
> > I've been using Mailscanner for a few years now with no problems.  Two weeks
> > ago, I started to have a problem.
> >
> > When I run Mailscanner, it maxes out my CPU and the amount of memory it uses
> > keeps climbing and climbing, until it eats all available memory and basically
> > freezes the system up.  Mail is not processed from the Postfix hold queue.
> >
> > The system is basically used only by myself, for LAN file storage and email. 
> > It's a P2 333mhz, with 512mb of RAM, which has been just fine for my needs.
> >
> > Using Postfix for mail delivery; the OS is Ubuntu 6.04.
> >
> > I've disabled Spamassassin, but still have the same problem.
> >
> > Running Mailscanner in debug, I get the following:
> >
> > root at fatman:/home/tom# /etc/init.d/mailscanner start
> > In Debugging mode, not forking...
> >
> >
> > >From the /var/log/mail.info (nothing in the mail.err or mail.warn):
> >
> > Mar  6 16:10:48 fatman MailScanner[7063]: MailScanner E-Mail Virus Scanner
> > version 4.57.6 starting... 
> > Mar  6 16:10:49 fatman MailScanner[7063]: Read 759 hostnames from the phishing
> > whitelist 
> > Mar  6 16:10:49 fatman MailScanner[7063]: Config: calling custom init function
> > SQLBlacklist 
> > Mar  6 16:10:49 fatman MailScanner[7063]: Starting up SQL Blacklist 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Read 0 blacklist entries 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Config: calling custom init function
> > MailWatchLogging 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Started SQL Logging child 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Config: calling custom init function
> > SQLWhitelist 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Starting up SQL Whitelist 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Read 18 whitelist entries 
> > Mar  6 16:10:50 fatman MailScanner[7063]: Using locktype = flock 
> >
> > After about 20 minutes, the CPU is still at around 98-99% and using 450+MB of
> > RAM (on my installation, Mailscanner uses 60-70MB of RAM per instance).
> >
> > I've tried removing/purging/reinstalling Mailscanner, but keep coming up with
> > the same results.
> >
> 
> Jules
> 
> -- 
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
> 
> MailScanner customisation, or any advanced system administration 
> help? Contact me at Jules at Jules.FM
> 
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> PGP public key: http://www.jules.fm/julesfm.asc
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
> 
> Before posting, read http://wiki.mailscanner.info/posting
> 
> Support MailScanner development - buy the book off the website!



More information about the MailScanner mailing list