Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

Am 24.05.17 um 06:00 schrieb Michael Hieb: [...] MAILSERVER:~ # strace -p 2120 Process 2120 attached fcntl(13, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0} Process hangs, nothing happening... then about 45 seconds later (in this case - time to wait varies each time I try this)

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

= 0 > >> open("/dev/urandom", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_CLOEXEC) = 3 > >> fstat(3, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9), ...}) = 0 > >> poll([{fd=3, events=POLLIN}], 1, 10)= 1 ([{fd=3, revents=POLLIN}]) > >> read(3, >

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

I set maxforkrate=100 to make to raise it well above a default. 100 a second is quite a lot and logs show I am no where near that many connections. I am not sure if I can define the maxforkrate parameter so that it is unlimited (for testing) so I just set it at a number well above what I see

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

ten="mail.domain2.com:lmtp" maxchild=-1 maxforkrate=100 lmtp.domain3.com cmd="lmtpd -a" listen="mail.domain3.com:lmtp" maxchild=-1 maxforkrate=100 lmtp.domain4.com cmd="lmtpd -a" listen="mail.domain4.com:lmtp" maxchild=-1 maxf

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

644, st_size=127, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fdeb770b000 read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0\0\0\0"..., 4096) = 127 lseek(3, -71, SEEK_CUR) = 56 read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

Michael Hieb wrote on 5/19/2017 4:48 AM: Apologies for long post, most of it is configuration details. ... # UNIX sockets start with a slash and are put into /var/lib/imap/socket SERVICES { # add or remove based on preferences #imap cmd="imapd" listen="imap" maxchild=-1 maxforkrate=100 imap

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

3, -71, SEEK_CUR) = 56 read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0\0\0\0"..., 4096) = 71 close(3)= 0 munmap(0x7fdeb770b000, 4096)= 0 socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3 connect(3, {sa_family=AF_LOCAL

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

open("/dev/urandom", O_RDONLY|O_CLOEXEC) = 3 > read(3, > "U\2\251M\21fm\345\334\215Q1(\253\1M!\270\226\212s\263}\351\16\271", > 28) = 28 > close(3)= 0 > futex(0x7fdeb5bf30a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0 > open("/

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

My immediate guess is it blocks at reading /dev/random. strace should show you exactly where it blocks. What version of SASL are you using? Newer versions have switched to /dev/urandom AFAIK Michael On Friday, May 19, 2017 05:48:36 PM Michael Hieb wrote: > Apologies for long post, most of it is

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

Have you tried stracing one of the imap processes that is slow to see where the delay is? On May 19, 2017 6:48:36 AM ADT, Michael Hieb wrote: >Apologies for long post, most of it is configuration details. > >I have recently changed from a single threaded cyrus server

Re: Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

A few corrections of typos.. On 05/19/2017 05:48 PM, Michael Hieb wrote: Apologies for long post, most of it is configuration details. I have recently changed from a single threaded cyrus server in which multiple domains were overloaded on one listener as multiple virtual domains to a

Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

Apologies for long post, most of it is configuration details. I have recently changed from a single threaded cyrus server in which multiple domains were overloaded on one listener as multiple virtual domains to a multiple threaded cyrus server in which multiple domains are listened for on