Re: server not accessible - 3.6-beta3-1

"Simon Matter" <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
> Thank you Ivan,
>
> I just checked it and modified to 
>
>         imap            cmd="imapd -U 60" listen="imap" prefork=10
> maxchild=500 proto=tcp4
>         imaps           cmd="imapd -s -U 60" listen="imaps" prefork=10
> maxchild=500 proto=tcp4
>
> We will see, soon.
>
> The old (default) was:
>
>         imap            cmd="imapd -U 30" listen="imap" prefork=0
> maxchild=100
>         imaps           cmd="imapd -s -U 30" listen="imaps" prefork=0
> maxchild=100

What I'm wondering is where did your cyrus.conf file come from?

This file seems to be good for a private test server but for real world
tasks, it simply won't work as you have seen.

Using the original conf files are a better choice IMHO, like the prefork
example:

https://github.com/cyrusimap/cyrus-imapd/blob/master/doc/examples/cyrus_conf/prefork.conf

Regards,
Simon

>
> When I checked it before, I had 120 imapd process running and 125
> connections (netstat -tapn | grep imap).
>
> Now I have 121 processes and 97 connections.
>
> I will report here.
>
> Thanks!
> István
>
>
>
> 2022. 11. 15, kedd keltezéssel 12.53-kor Ivan Kuznetsov ezt írta:
>> Hello
>>
>> It can be a lack of available IMAP handlers. One TB makes more than
>> one
>> IMAP connection depending of a number of tabs opened. Some client
>> connections can hit a limit of running imapd processes. Consult with
>> cyrus.conf
>>
>> Regards, Ivan
>>
>>



------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Tc5a2b80110a27505-M3aeb5128b4bc34136d5ef3e9
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.