Repairman wrote:
Hello all!
I have no idea how to research this problem, so any suggestion you offer will
be appreciated!
I'm running Dspam 3.8.0 in daemon mode on CentOS 4.5 along with Postfix 2.2.10
& MySQL 4.1.20.
I don't normally go "bleeding-edge" on my projects. I'll wait for a version to
be out awhile and see what happens before I install it first on a test platform then I
put it on my production server. The system was running Dspam 3.6.8 until I upgraded to
3.8.0 at the end of August.
While I was running 3.6.8 I never noticed this problem, but with 3.8.0 my Dspam
process has started taking up large amounts of memory. And it's started taking
up this memory at a faster rate.
I don't have hard data points to go by yet, but in general my servers average
load has not changed over the past 2 months.
I would see that Dspam was taking around 2 gig's of memory and I would stop the
process and restart it to get the memory cleared up. This would be around every
2 weeks.
But for the last 2 weeks the need to restart Dspam is more frequent. It's only
been 3 days and Dspam is already at 1.5 gig's today.
I've seen prior posts where a different database was used and it would cause
Dspam to use large amounts of memory, but I'm using MySQL and I've run checks
on my database just to be sure and there are no problems with it.
Any suggestions where to go from here?
Thanks!
I've had trouble running dspam in daemon mode too (different problems
than what you describe though.)
To that end I don't run dspam in daemon mode. Instead I make use of
pipe (documented in one or more of the dspam postfix setup wiki's).
Yes, It is a work-around, not a fix, is less efficient, etc.. Just
thought you might consider it as an option.
-Troy
