Well, I've upgraded to SA 3.0.1 several of my servers, and since the bugfixes seemed so promising, I decided to give it a try on the server which had the memory issues (I've sent a couple of mails to the list a month ago, or so). Good news is spamd doesn't chew up the memory as fast as with 3.0.0. Bad news, it still does it. Playing with the numbre of max-conn-per-child and the number of children, I've managed to make it quasi-stable, but it still is a hell of a memory chewer. What really pisses me off is the fact that in the rest of my servers, when SA starts, only the parent process weights 22 MB, the children weight approx. 5 MB each. But in this particular server, all of the spamd processes start up as 22 MB processes... I've downloaded and recompiled perl (running on 5.8.5 now, compiled from source), and the bad behaviour keeps going and going. I've enabled the debug option on spamd, but looking at the maillog, it seems to be working fine. Every time a mail arrives, spamass-milter passes it to spamd, it opens it, claims the mutexes on auto whitelist and bayes, and then releases them, when it finishes scanning. Running sa-learn force-expire didn't help at all, spamd just keeps growing and growing, but with a setting of max-conn-per-child of 10o and ten children, it does it slower, and allows the server to live longer (so far, it didn't crash, but most of daily spam will arrive in approx. five hours from now). If anyone could point me on what to look at, or the output of what process will be handy to attach here in order to debug this, please, send me a mail, because this little big memory issue is really driving me nuts.
Thanks in advance, Luis -- ------------------------------------------------- GNU-GPL: "May The Source Be With You... -------------------------------------------------
