On 12/25/06, Peter Peltonen [EMAIL PROTECTED] wrote:
My problems started at the morning of 20.12. Zero timeouts before
that. I'll reboot the server tomorrow evening so we'll see if anything
changes.
I've now rebooted the server. I also upgraded to the newest
spamassassin, courier-imap, and
On 12/24/06, Eric Shubes [EMAIL PROTECTED] wrote:
Is bayes_auto_expire on? That caused timeouts for me, though not mysql.
Nope. I've got that turned off a few weeks earlier (thanks to the
discussion on this list).
Not exactly. It still has many static rules that can catch a lot of things.
I also noticed timeouts in imap4 and imap4-ssl logs. They're like this:
2006-12-22 20:19:27.537362500 INFO: TIMEOUT, [EMAIL PROTECTED],
ip=[xxx.xxx.xxx.xxx], headers=0, body=0, rcvd=75, sent=112441,
time=1802
There is a lot more these than timeouts in spamd logs.
My problems started at the
Greetings, Peter.
On 23 ??? 2006 ?., 21:12:53 you wrote:
When looking at information that sar has collected CPU has been idle
at least 80 % all the time. Top showed mysql and spamd eating from
0-20 % of CPU at times, never much more.
After restarting spamd I have not been able to
On 12/24/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Did you check with vmstat or top the state of iowait? Maybe your
processors are idle because of heavy disk load they are waiting to
finish?
iostat tells me:
avg-cpu:
%user %nice%sys %iowait %idle
6.77 0.00 1.23 8.28
Peter Peltonen wrote:
On 12/24/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Did you check with vmstat or top the state of iowait? Maybe your
processors are idle because of heavy disk load they are waiting to
finish?
iostat tells me:
avg-cpu:
%user %nice%sys %iowait %idle
6.77
On 12/23/06, Peter Peltonen [EMAIL PROTECTED] wrote:
When looking at information that sar has collected CPU has been idle
at least 80 % all the time. Top showed mysql and spamd eating from
0-20 % of CPU at times, never much more.
After restarting spamd I have not been able to reproduce this.
Hi,
On 12/19/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
From time to time some of SA servers tend to 'stuck'. This shows up in
logs like this:
# qmlog -s @4000458765251acf0b74.s spamd | grep -E 'error|warn'
2006-12-19 00:53:00.508318500 [10802] warn: spamd: timeout: (300 second timeout
Greetings, Peter.
On 22 ??? 2006 ?., 18:59:10 you wrote:
We have quite the default spamassassin setup (no extra or custom
rules) and are using spam filtering only for a few domains. And no
cluster setup, this is a single server.
I.e. mysql, spamassassin, apache and qMailToaster - all are
Greetings, Peter.
On 22 ??? 2006 ?., 18:59:10 you wrote:
If someone has an idea how to debug mysql to find out what is really
causing the hangups, please let me know.
Forgot to say - try to disable bayest engine of SA and check if it
helps. In my case the issue is gone just as I disable
Greetings, Eric.
On 19 ??? 2006 ?., 20:05:37 you wrote:
Alexey Loukianov wrote:
Hello all,
I'm forced to run a bunch of SA-specialized servers to be able to
handle processing of all the incoming mail to the corporate servers.
All the SA hosts utilize the same HA mysql for bayest
Alexey Loukianov wrote:
Hello all,
I'm forced to run a bunch of SA-specialized servers to be able to
handle processing of all the incoming mail to the corporate servers.
All the SA hosts utilize the same HA mysql for bayest storage DB, and
a simple king of load-balancing for SA is achieved
Hello all,
I'm forced to run a bunch of SA-specialized servers to be able to
handle processing of all the incoming mail to the corporate servers.
All the SA hosts utilize the same HA mysql for bayest storage DB, and
a simple king of load-balancing for SA is achieved by built in spamc
13 matches
Mail list logo
