Hi:
I'm testing cyrus 2.0.15 (apllying it a mail stress tool) and imapd
process hungs...
It hangs always when the server has between 145 and 155 imapd
processes...
When I say "hungs" I mean that, for instance, if I make a connection to
port 143, the imapd process doesn't responds properly...
[root@cyrus2 bin]# telnet localhost 143
Trying 127.0.0.1...
Connected to cyrus2.
Escape character is '^]'
In this situation the server has a lot of memory available, has no
uptime and it seems that is doing "nothing"...
If the stress is not very hihgh... the cyrus works perfectly...
I have configured the imapd process in order to server until 500 childs
with the maxchild directive..
cyrus.conf looks like this:
# standard standalone server implementation
START {
# do not delete these entries!
mboxlist cmd="ctl_mboxlist -r"
deliver cmd="ctl_deliver -r"
# this is only necessary if using idled for IMAP IDLE
# idled cmd="idled"
}
# UNIX sockets start with a slash and are put into /var/imap/sockets
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=20 maxchild=500
# imaps cmd="imapd -s" listen="imaps" prefork=1
pop3 cmd="pop3d" listen="pop3" prefork=10 maxchild=50
# pop3s cmd="pop3d -s" listen="pop3s" prefork=1
sieve cmd="timsieved" listen="sieve" prefork=0
# at least one LMTP is required for delivery
# lmtp cmd="lmtpd" listen="lmtp" prefork=0
lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=5
}
EVENTS {
# this is required
checkpoint cmd="ctl_mboxlist -c" period=30
# this is only necessary if using duplicate delivery suppression
delprune cmd="ctl_deliver -E 3" period=1440
}
Any iadea ?
Regards...
Enric
