I have server with 16k accounts with approximately 35k messages
processed per day. I have had a problem with the server under high load
which becomes unusable - no logins. I think I narrowed the problem down
to the lmtpunix area when a remote user sends an email with 100+
recipients. It goes like:
1. Mail arrives
2. I start seeing lmtpunix DBERROR db4: 30 lockers ... increasing
to around 150+ lockers
3. Then the kernel starts warning of memory usage
4. I start seeing lmtpunix - abnormally terminated
5. The kernel reports 0 swap space
5. Then master signaled to death by 9
6. Then the kernel starts killing off cyrus and other processes.
The server then has to be reset.....
This only happens when a spike of email arrives, primarily when a single
email has 100+ recipients. It appears that the lmtpunix is killing the
server. I initially though I
should place limits on the smtp connections but this now appears to be a
Cyrus deliver problem, i.e. I think I need to limit how much mail
postfix should send to the lmtpunix socket, yes/no?
Questions:
1. the lmtp currently uses the socket setup, should I use the TCP
configuration?
2. under postfix (main.cf), what *_destination_*_limits should I use?
Vernon
The host server is a dual XEON 3.0 with 1.5 meg of ram.
Cyradm Version information:
localhost> ver
name : Cyrus IMAPD
version : v2.2.12-Gentoo 2005/02/14 16:43:51
vendor : Project Cyrus
support-url: http://asg.web.cmu.edu/cyrus
os : Linux
os-version : 2.6.14-gentoo-r4
environment: Built w/Cyrus SASL 2.1.20
Running w/Cyrus SASL 2.1.20
Built w/Sleepycat Software: Berkeley DB 4.2.52: (December
3, 2003)
Running w/Sleepycat Software: Berkeley DB 4.2.52:
(December 3, 2003)
Built w/OpenSSL 0.9.7e 25 Oct 2004
Running w/OpenSSL 0.9.7e 25 Oct 2004
CMU Sieve 2.2
TCP Wrappers
mmap = shared
lock = fcntl
nonblock = fcntl
auth = unix
idle = poll
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
