Jacob Yocom-Piatt wrote:
> ---- Original message ----
>> Date: Thu, 30 Nov 2006 15:34:04 -0500
>> From: Seth Hanford <[EMAIL PROTECTED]>
>> Subject: Dovecot 1.0rc2p3 "Too many open files"
>> To: misc@openbsd.org
>>
...
>> How do I fix this? It seems like Dovecot is running away with LOTS of
>> open files, and the dovecot lists talk about file descriptor leaks for
>> later versions, as well as kqueue problems noted in the OpenBSD ports
>> tree CVS log. I've seen fstat reporting something like 36+ connections
>> for one of my mail accounts when it was just sitting idle. I could
>> increase ulimit like many MySQL users have in the past, but this seems
>> more like a runaway program to me.
>>
>
> i'm having the same problems as the OP, where dovecot opens too many files
> and/or won't allow downloading of email via POP or IMAP. this is
> dovecot-1.0rc2p3 on 4.0-release, but it appears that dovecot-1.0beta8 from
> 3.9-release didn't get deleted cleanly (shows up as partial-dovecot-1.0beta8)
> when i upgraded. a pkg_delete {partial-dovecot-1.0beta8,dovecot-1.0beta8}
> gives
> me no output and does not remove the pkg from the pkg_info listing. any
> suggestions on how to fully remove the 1.0beta8 pkg?
>
> my 1st attempt at fixing this is adding a login class that ups the usual
> ulimits, just like for mysqld:
>
> _dovecot:\
> :datasize=1024M:\
> :maxproc=4096:\
> :openfiles-cur=2048:\
> :openfiles-max=8192:\
> :stacksize-cur=16M:\
> :tc=default:
>
> this fixes, at least temporarily, the trouble with number of open files.
I'd also like a better solution than I have at the moment. Because
dovecot was trashing the associated mail processes (amavisd, postfix)
because it was using up too many open files, I opted to manually build
an upgrade package to the -current version of dovecot (1.0rc15).
Obviously, this is an unsupported solution and I don't really like being
here. Is the ulimit method preferred? I don't understand that system
very well, and was under the assumption that it would simply hide the
symptoms of broken software in this case -- dovecot might simply expand
to fill the more lenient login.conf constraints, but take longer to get
there.
- Seth
> other solutions that come to mind, but are not very appealing:
>
> - upgrade mailserver to current or stable to get new dovecot package
> - compile dovecot from souce (not clear to me how to get all the nice
> configure
> options that the package uses; any insight here would be nice)
>
> advice as to the best solution is welcome. i'd like to keep this machine as
> close to 4.0-release as possible for maintainability purposes.
>
> cheers,
> jake
>
>> Thanks,
>> Seth
>>
>
