Large deliver.db file
igor at ipass.net
Tue Nov 4 12:13:08 EST 2003
On Tue, 4 Nov 2003, Denis Liard wrote:
> We had the same problem, and I found in the log file that the
> ctl_deliver no not work : db problem...
> It seem that the db file was incorrect.
> So I decide to rename it and restart cyrus. The risk was only to delive=
> duplicate mail so ....
> A new file was created, and ctl_deliver work fine (log file).
> Now, the size is large because of traffic but stable. I have reduce the
> expiring delay to 2 days.
Do you use DB 4.1.25? If so, you can fix this problem by starting cyrus
from configdirectory. There is a problem with the setup of the sleepycat
enviroment, but I have not been able to track the problem down. Note tha=
this is DB 4.1.25 issue only.
> Igor Brezac a =E9crit:
> >On Tue, 4 Nov 2003, Leena Heino wrote:
> >>Is it normal that tls_sessions.db, deliver.db and db-directories seem=
> >>get quite large. At the moment tls_sessions.db is about 50kB, deliver=
> >>is about 174MB and db and db.backup directories are about 1.3G each.
> >>System information:
> >>name : Cyrus IMAPD
> >>version : v2.1.15 2003/08/15 19:34:42
> >>vendor : Project Cyrus
> >>support-url: http://asg.web.cmu.edu/cyrus
> >>os : SunOS
> >>os-version : 5.9
> >>environment: Cyrus SASL 2.1.15
> >> Sleepycat Software: Berkeley DB 4.1.25: (December 19, 20=
> >>delprune cmd=3D"ctl_deliver -E 3"
> >This is normal for large volume email sites. If you want a smaller
> >deliver.db, consider expiring duplicates faster (ctl_deliver -E 2).
> >Is your deliver.db continually growing?
> Vu le mardi 04/11/2003 a 17:42:35 par Proxy-ScanMx.
> Analyse antivirale par ProxyConcept (http://proxyconcept.com)
More information about the Info-cyrus