Always full of Ram because Qmail service.

[Kloxo-DR]

In my top monitor it shows qmail-rspawn under command. Does that mean that it hangs in identifying DKIM signatures under cluster env and goes in loop?

[chrisf]

No.  If the script finds no domainkey for a domain it sends it unsigned. Several of us use qmail in a cluster environment without problems.

Good chance you have a corrupted queue, and since qmail-remote's job is to send it, it is hanging.   Goto KloxoMR panel and look at mail queue, report it here.  Watch for a message or messages not leaving the queue.

As we can see, the problem IS NOT with signing, since you had him rename a file, which is never a solution.  Reinstall your toaster packages.

Did this problem always exist on this server or is it recent?

SSH:
yum reinstall *-toaster

SSH:
vim /var/qmail/control/softlimit
If 64 bit file should be

Code: [Select]

/usr/bin/softlimit -m 72000000

If 32 bit change above number to 1800000.

Run fixdomainkeys in case a domain key is corrupted, but unlikely
SSH:
sh /script/fixdomainkeys

Do as Mustafa also said and reduce Max smtp to 25 - 50 in KloxoMR panel under mail settings.

Do this on the server with problems, and all at once, no need try each solution, they are all part of one solution.

[hoangkoha]

Did this problem always exist on this server or is it recent?

It always appears and stress my machine

Do as Mustafa also said and reduce Max smtp to 25 - 50 in KloxoMR panel under mail settings.

I reduce it from 100 to 70. I will reduce it to 50.
I'm removing and installing *toaster. I hope everything allright

Ah, how to reset domain counter  ? I create a customer, then i add a domain for this customer, after i delete domain but the domain counter not reset

[MRatWork]

Domain counter still have bug since Kloxo release (6.0.x) and Kloxo-MR carry this bug.

[hoangkoha]

Thank you a lot, Kloxo-DR, MRatWork and chrisf. Problem solved. No ram killer anymore  I just reinstall *toaster and reduce value of Max SMTP in "Mail Server Setting" to 50. Hope this topic useful to everyone
Have a nice day

[Kloxo-DR]

Hi,

The first thing I told you was to reinstall the toaster, which - as it appears now - that you DID NOT. Then we see things in a different direction on trouble shooting and the actual problem remains in there.

Thank you a lot, Kloxo-DR, MRatWork and chrisf. Problem solved. No ram killer anymore  I just reinstall *toaster and reduce value of Max SMTP in "Mail Server Setting" to 50. Hope this topic useful to everyone
Have a nice day

There were changes in the compilation of Qmailtoaster. Most likely that was the problem.

If you want to have this topic useful to everyone, then do change the Max SMTP from your currect 50 to 200, instead of default 100 in Kloxo-MR.

Try to increase Max SMTP instances to 200 instances now, restart qmail by the following and tell us if this solution increases RAM of qmail-remote:

qmailctl stop
qmailctl start
service xinetd restart

So let us see where the problem was and understand if the problem occured due to more SMTP instances.

[hoangkoha]

The first thing I told you was to reinstall the toaster, which - as it appears now - that you DID NOT.

The first, I reduced value of Max SMPT but it still took a lot of ram.
Then, i really reinstalled qmail-toaster, it was the same broblem.
After, i removed clearly qmail-toaster and installed qmail-toaser, everything seem to be allright.
Final, i scare of ram killer, so i reduce value of SMTP again 

Now, my server lost WAN IP that i can remote it. I will increase Max SMTP instances to 200 instances as soon as i reconnect my server.
I'm sorry for making another direction 

[hoangkoha]

i increased MAX SMTP INSTANCES to 200 follow your required. I need a day enough to confirm about increases RAM.
But i think spamdyke have broblem after i reinstalled *toaster.

No mail account, it just a clearly qmail.

[MRatWork]

Don't confuse about 'spamd' in 'top'. It's spamassassin and not spamdyke. Spamassassin (also clamav) tend to use more resource (cpu and ram).

[Kloxo-DR]

To reduce resource usage, change Spamassassin to Bogofilter.

Bogofilter _MUST_ consume less RAM or CPU tht Spamassassin.

Most likely the problem was not in reinstall or max instances but old binaries that did not correctly get uninstalled. I had something like that as well.

Thats the reason why I advised you the second time "not to reinstall" but remove and install.

Remove and install is not the same as reinstall.

After you change it to Bogofilter, everything should be cooled down and no dramatic usage of CPU of RAM!

[hoangkoha]

I never use Spamassassin, the default setting is Bogofilter. I think it was changed after reinstalling qmail. I switch to Spamassassin, then i switch back to Bogofilter and the "Spamd process" 's killed.
No dramatic usage of RAM if set  MAX SMTP INSTANCES to 200 after a day

[MRatWork]

remove spamassassin and clamav with 'yum remove spamasssassin-toaster* clamav-toaster* simscan-toaster*' after change spamasssin to bogofilter in panel.

[Kloxo-DR]

Hi,

No dramatic usage of RAM if set  MAX SMTP INSTANCES to 200 after a day

Yes, I knew it. You can even set 1000 instances and things will not change. Better not unless you require and fulfil the prerequisites...

I suspected that the problem was somewhere with old Qmailtoaster rpms and spamdyke with old Kloxo-MR versions until mid. Feb. 2014., until Mustafa recompilied the Qmailtoaster.

I had a similar problem. The problem remained with yum reinstall *toaster but disappeared after yum remove *toaster and yum install *toaster. In this case, I could not confirm this as I did not have any explosive RAM effect due to above yum proceedure.

Conclusion from the above problem is that MAX SMTP INSTANCES, softlimit or crashed queues HAS NO impact qmail-remote.

The problem was in old binaries, config files or PATHS, etc. that got recompiled and reconfigured after the remove/install method. Here yum reinstall does, or did not, not help.

[MRatWork]

If you run 'yum install *-toaster', it's including install spamassassin and clamav. In installing process, spamassassin and clamav not including to installed.

[hoangkoha]

I had a similar problem. The problem remained with yum reinstall *toaster but disappeared after yum remove *toaster and yum install *toaster. In this case, I could not confirm this as I did not have any explosive RAM effect due to above yum proceedure.

So lucky about the same broblem with you thank you, Kloxo-DR.

If you run 'yum install *-toaster', it's including install spamassassin and clamav. In installing process, spamassassin and clamav not including to installed.

Oh, i got it. It 's the reason that i don't have clamav before I removed it.
My cluster seem to be nice. Thank you, MRatWork