I'm using postfix 2.7.1 with amavis 2.7.0 as a proxy. After some clients 
reported errors sending email, I've noticed postfix is sometimes unable 
to relay email to amavis due to 'queue file write error'. I'm kinda 
clueless, why... Unfortunately I can't see no logs at that time in the 
maillog. Due to this being an active server ( ~100 msgs/minute) I don't 
dare starting amavis in debug mode.

Oct 28 15:30:26 smtp-1 postfix/smtpd[3215]: warning: timeout talking to 
proxy 127.0.0.1:10024
Oct 28 15:30:26 smtp-1 postfix/smtpd[3215]: proxy-reject: 
END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<a...@b.c> 
to=<d...@e.f> proto=SMTP helo=<hhh>


I belive the hardware itself is adequate - ibm hs22 blade, dual quad 
core xeon with ht, 24GB ram, it's running Centos 5.5 x64. First I 
thought there aren't enough running processes of amavis, so now I'm 
running 100 instances (was set to 50 before), but guess that didn't fix 
the problem.

$ uptime
  19:32:30 up 9 days, 20:33,  2 users,  load average: 1.09, 1.07, 1.10
$ free
              total       used       free     shared    buffers     cached
Mem:      24660216   14494356   10165860          0    1805228    6367644
-/+ buffers/cache:    6321484   18338732
Swap:      4192956          0    4192956

Any ideas how to start analyzing the problem?

-- 
LP, Rok

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 Please visit http://www.ijs.si/software/amavisd/ regularly
 For administrativa requests please send email to rainer at openantivirus dot 
org

Reply via email to