Re: [Dovecot] more problems with dovecot-1.1 beta3
On 22.10.2007, at 6.24, sergey ivanov wrote: deliver(seriv): Oct 21 09:44:57 Error: Cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/ dovecot.index.cache: Newly added field got lost unexpectedly This happens once if cache file doesn't exist yet. This and several other bugs have been fixed in nightly snapshots already, you can use them until I'll release beta4 probably tomorrow. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] more problems with dovecot-1.1 beta3
Timo Sirainen wrote: On 21.10.2007, at 11.35, sergey ivanov wrote: dovecot: Oct 21 04:00:30 Error: IMAP(seriv): posix_fallocate() failed: Invalid argument I guess this happens if Solaris libc has posix_fallocate() but the kernel doesn't support it. This should help: http://hg.dovecot.org/dovecot/rev/a9dfe05dfadd Thank you! With this patch 10 first minutes with dovecot-1.1 do not exposed any problem, I will keep eye on it and report if something happens. -- Sergey Ivanov.
Re: [Dovecot] more problems with dovecot-1.1 beta3
sergey ivanov wrote: Timo Sirainen wrote: On 21.10.2007, at 11.35, sergey ivanov wrote: dovecot: Oct 21 04:00:30 Error: IMAP(seriv): posix_fallocate() failed: Invalid argument I guess this happens if Solaris libc has posix_fallocate() but the kernel doesn't support it. This should help: http://hg.dovecot.org/dovecot/rev/a9dfe05dfadd Thank you! With this patch 10 first minutes with dovecot-1.1 do not exposed any problem, I will keep eye on it and report if something happens. First 14 hours of the run, everything looks fine but the messages in dovecot.log: --- deliver(seriv): Oct 21 09:44:57 Error: Cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 11:01:43 Error: Cache file /var/spool/imap/seriv/.imap/.sisyphus-cybertalk-lists-altlinux-org/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 11:12:14 Error: Cache file /var/spool/imap/seriv/.imap/.xen-users-lists-xensource-com/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 11:31:36 Error: Cache file /var/spool/imap/seriv/.imap/.JewisClubMaoz-yahoogroups-com/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 12:00:25 Error: Cache file /var/spool/imap/seriv/.imap/.centos-announce-centos-org/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 15:42:37 Error: Cache file /var/spool/imap/seriv/.imap/.ma-linux-calypso-tux-org/dovecot.index.cache: Newly added field got lost unexpectedly deliver(seriv): Oct 21 17:30:19 Error: Cache file /var/spool/imap/seriv/.imap/.IsraelEldad-yahoogroups-com/dovecot.index.cache: Newly added field got lost unexpectedly --- I have deleted all dovecot.index* files after stopping dovecot-1.0.5 and before starting patched dovecot-1.1. -- WBR, Sergey Ivanov.
Re: [Dovecot] more problems with dovecot-1.1 beta3
On Thu, 2007-10-18 at 15:16 -0400, Sergey wrote: Thank you for pointing me about -xc99 flag, I have compiled and installed dovecot inplace of version 1.0.5 without any special actions on the upgrade. And after starting it immediately got in it's log file messages like: --- dovecot: Oct 16 23:10:18 Error: IMAP(seriv): file_set_size() failed with index cache file /var/spool/imap/seriv/.imap/.git-altlinux-ru/dovecot.index.cache: Invalid argument Could you apply this patch and see what it logs then: http://hg.dovecot.org/dovecot/rev/b7d8695d864d dovecot: Oct 16 23:52:28 Panic: IMAP(seriv): file client.c: line 105: assertion failed: (!client-destroyed) Fixed: http://hg.dovecot.org/dovecot/rev/86e964111b1f dovecot: Oct 18 15:02:58 Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 384). Either grow the limit or change login_max_processes_count a nd max_mail_processes settings .. One more problem is with fd limit: I have a small dovecot installation, so don't want to increase fd limit. I tried to decreasee max_mail_processes, login_max_processes_count and login_max_connections, but still I have .. login_max_connections: 120 max_mail_processes: 128 Changing login_max_connections doesn't affect anything because you're using login_process_per_connection=yes. The needed fd count is calculated from login_max_processes_count(pop3) + login_max_processes_count(imap) + max_mail_processes. So in your case 128+128+128. signature.asc Description: This is a digitally signed message part
