On 03/02/2011 11:16 AM, Sergio M wrote:
Eric Shubert escribió:
On 03/02/2011 10:22 AM, Sergio M wrote:
Eric Shubert escribió:
You should see:
03-02 10:09:37 tcpserver: status: 0/25
right after you start qmail. If it doesn't drop to 0 when you start
it, then something's wrong. Please check the status message which
corresponds to the start of qmail. If it's not 0/25, please post
several lines before and after from your log.
I don't know about using htop to look for qmail processes. Perhaps
you've missed something. I would try:
# ps -ef | grep qmail
to see what processes are running that are qmail related, in place of
your step 4 above.
I'm sorry, its starts at 0/25 and then goes up straight to 25/25.
What's more annoying is that it just stays frozen for several minutes.
(ie from 10:22 to 10:26 in the excerpt that i posted earlier)
---------------------------------------------------------------------------------
How long does it take to go from 0 to 25? Please post log.
<snip>
Wow. Just 9 seconds. And from a variety of sources.
Also, why do you have this set so low? Please post (again) your HW specs.
[*sergio*] I have a Quad-Core AMD Opteron(tm) Processor 1354 cpu MHz :
1100.000 with 1Gb RAM.
That's more than adequate CPU, and ample RAM.
You should be able to open things up a bit. Also, number of domains
and users (# pop, # imap) would help. Using dovecot or courier? Also,
how many spamd children do you have configured? I know these aren't
directly related to your perceived problem, but these things could be
influencing your dilemma.
[*sergio*] We have around 40/50 domains with less than 2000
users(total), mostly pop, though some use Squirrelmail.
Dont know about courier or dovecot.
Doesn't really matter unless you have IMAP accounts with large amounts
of email.
cat /var/qmail/supervise/spamd/run
#!/bin/sh
exec /usr/bin/spamd -x -m 8 -u vpopmail -s stderr 2>&1
That's a good start.
What are your load number looking like? Pretty low I expect.
I'd open that puppy up. You can handle way more than 25 connections.
I'd go back to the default value of 100 for starters, and double the
number of spamd children. Then keep an eye on things. You don't want to
get so many spamd instances running that you start swapping ram.
Find a good comfortable number for spamd children (this is what will eat
your ram and cpu), then adjust your total smtp sessions to fit. You
should have many more (2-4x) smtp sessions available as spamd children.
With that many domains and users, there is probably a good deal of mail
queued up in other servers, which is why you're getting pounded so hard.
You might need to turn off spamassassin temporarily to get past the
wave, but I'd only do that as a last resort. What you have here is a
good opportunity to do some serious tuning. :)
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
