Re: [Dovecot] Segfault in quota-fs plugin
Hi Brandon, since our patches are very similar, they should be a good way to fix this issue. For me it's working since 7 days now without a harm. See: http://markmail.org/message/p736w5f4dmamfnom Ralf Brandon Davidson schrieb am 23.09.2009 03:41: > Hi all, > > We recently attempted to update our Dovecot installation to version > 1.2.5. After doing so, we noticed a constant stream of crash messages in > our log file: > > Sep 22 15:58:41 hostname dovecot: imap-login: Login: user=, > method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, TLS > Sep 22 15:58:41 hostname dovecot: dovecot: child 6339 (imap) killed with > signal 11 (core dumps disabled) > > We rolled back to version 1.2.4, and installed 1.2.5 on a test system - > something we'll have to make sure to do *before* rolling new versions > into production. > > Anyway, after examining a few core files from the test system, it looks > like the recent changes to the quota plugin (specifically the maildir > backend's late initialization fix) have broken the other backends. Stack > trace and further debugging are available here: > http://uoregon.edu/~brandond/dovecot-1.2.5/bt.txt > > The relevant code seems to have been added in changeset 9380: > http://hg.dovecot.org/dovecot-1.2/rev/fe063e0d7109 > > Specifically, quota.c line 447 does not check to see if the backend > implements init_limits before calling it, resulting in a null function > call for all backends that do not do so. Since this crash would appear > to affect all quota backends other than maildir, it should be a pretty > easy to reproduce. > > I've attached a patch which seems to fix the obvious code issue. I can't > guarantee it's the correct fix since this is my first poke at the > Dovecot source, but it seems to have stopped the crashing on our test > host. > > Regards, > > -Brandon -- __ Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier Mail: beck...@fh-trier.deFon: +49 651 8103 499 Web: http://www.fh-trier.de/~beckerrFax: +49 651 8103 214 PubKey: http://www.fh-trier.de/~beckerr Crypto: GnuPG, S/MIME __ Wenn Gott gewollt haette, dass E-Mail in HTML geschrieben wuerden, endeten Gebete traditionell mit . (Tom Listen) smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] SharedMailboxes in a distributed environment
Timo Sirainen wrote: > On Sep 22, 2009, at 4:23 PM, Christian Rohmann wrote: > >> Is there no way to share mailboxes (folders) between different servers? > Not yet. "yet" sounds like "Yeah, reasonable request. There is already something planned" :-P Christian
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Mark Sapiro ha scritto: I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Same problem here, after about the same time from last server re start. Last restart log is: Sep 14 19:05:07 server dovecot: Dovecot v1.2.5 starting up (core dumps disabled) First failure is: Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted After the attached piece of log, the mail log is full of the same failure, and no customer can login using pop3 (imap works with no problems) After a server restart the problem was vanished. May be there is some kind of resource leakage. Marco P.S: This is my configuration is # 1.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-xen-amd64 x86_64 Debian 5.0.3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/server.pem ssl_key_file: /etc/ssl/private/server.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login first_valid_uid: 2000 last_valid_uid: 2000 first_valid_gid: 2000 last_valid_gid: 2000 mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire trash mail_plugins(imap): quota imap_quota expire trash mail_plugins(pop3): quota expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_save_uidl(default): no pop3_save_uidl(imap): no pop3_save_uidl(pop3): yes pop3_save_uidl(managesieve): no pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f pop3_uidl_format(managesieve): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): namespace: type: private separator: . inbox: yes list: yes subscriptions: yes namespace: type: private separator: . prefix: INBOX. hidden: yes list: no subscriptions: yes lda: postmaster_address: postmas...@xcon.it mail_plugins: quota sieve expire auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:user::proxy::quota quota2: dict:domain:%d:proxy::quota_domain trash: /etc/dovecot/dovecot-trash.conf expire: Trash 7 Trash/* 7 Cestino 7 Cestino/* 7 Junk 30 Spam 30 expire_dict: proxy::expire sieve: ~/.dovecot.sieve sieve_dir: ~/sieve dict: quota: pgsql:/etc/dovecot/dovecot-dict-quota.conf quota_domain: pgsql:/etc/dovecot/dovecot-dict-quota-domain.conf expire: pgsql:/etc/dovecot/dovecot-dict-expire.conf -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4 Sep 23 06:26:12 server dovecot: pop3-login: Login: user=, method=PLAIN, rip=11.22.33.44 lip=11.22.33.44 TLS Sep 23 06:26:13 server dovecot: POP3(x...@xxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 23 06:26:14 server dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 23 06:26:14 server dovecot: POP3(x...@xxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 23 06:26:15 server dovecot: pop3-login: Login: user=, method=PLAIN, rip=11.22.33.44 lip=11.22.33.44 TLS Sep 23 06:26:15 server doveco
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote: First failure is: Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted That's really the first one, and there's no kind of an error from dovecot master process? This sounds like wrong fd is being passed to pop3-login, but why it's being done only randomly I can't really think of..
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On Sep 23, 2009, at 11:27 AM, Timo Sirainen wrote: On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote: First failure is: Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted That's really the first one, and there's no kind of an error from dovecot master process? This sounds like wrong fd is being passed to pop3-login, but why it's being done only randomly I can't really think of.. It could be useful to know what the fd actually is. See what it logs with the attached patch? diff Description: Binary data
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Timo Sirainen ha scritto: On Sep 23, 2009, at 11:27 AM, Timo Sirainen wrote: On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote: First failure is: Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted That's really the first one, and there's no kind of an error from dovecot master process? This sounds like wrong fd is being passed to pop3-login, but why it's being done only randomly I can't really think of.. It could be useful to know what the fd actually is. See what it logs with the attached patch? Patch applied, now we must wait until the problem will show itself again (may be a week or so). Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Marco Nenciarini ha scritto: Patch applied, now we must wait until the problem will show itself again (may be a week or so). The patch does not compile, need another parameter (may be 1024?) Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On Sep 23, 2009, at 12:11 PM, Marco Nenciarini wrote: Marco Nenciarini ha scritto: Patch applied, now we must wait until the problem will show itself again (may be a week or so). The patch does not compile, need another parameter (may be 1024?) Oh, sorry. Use io->fd for the second one too.
Re: [Dovecot] Disconnected: Too many invalid IMAP commands
On Mon, Sep 21, 2009 at 01:24:27PM +0300, Timo Sirainen wrote: > I guess I should mention that I don't really mind people asking > questions when they're using an old version, but if it's a bug > report there's a good chance the answer is then "upgrade". Indeed, thanks for the patience and sorry for my off-topic level, as I was developer too (mplayer for example) I know it's quite hard to do anything with bug reports about old (and/or even obsolated) versions when the development/bug fixing is done on the current branch ...
Re: [Dovecot] windows imap clients
On 9/23/2009, Charles Sprickman (sp...@bway.net) wrote: > Charles (and Nikolay), thanks very much for pointing me at the TB3 beta. And of course, they just released b4... I didnt check the changelog to see if any of your issues were addressed, but I certainly hope - since you are apparently going to continue using it - that you will help them fix these problems by updating to b4, and reporting any issues that still exist to bugzilla: https://bugzilla.mozilla.org/ -- Best regards, Charles
Re: [Dovecot] Solr Plugin make only INBOX able to search
On Mon, Sep 14, 2009 at 2:54 AM, Timo Sirainen wrote: > > BTW. Note that Solr schema file was changed a bit to use less disk > space. But that shouldn't have caused this kind of a bug. The problem is caused by my custom schema. My changes are breaking the search someway. Thank you Timo. >
Re: [Dovecot] Dovecot 1.2.5 segfaults.
Hi Brandon, On Tue, 22 Sep 2009, Brandon Davidson wrote: Tom, Tom Diehl wrote: I just updated to dovecot 1.2.5 on centos5. 1.2.4 did not show this problem. I am going to roll back for the time being but I am willing to do whatever I need to to fix this. This is an x86_64 system. filesystem is ext3. I am now seeing the following in the logs: Sep 22 17:31:06 vfoggy kernel: imap[18644]: segfault at rip rsp 7fff83e31c88 error 14 I think I just posted a patch for your issue. It's possible there is another null function call in 1.2.5, but I'd bet against it. I can provide updated RPMs for testing if you are interested. I just built a new rpm and installed it on one of my machines. So far so good. It will be interesting to see if Timo agrees with this fix or if he wants to fix it in a different way. Thanks for the patch. Regards, -- Tom Diehl tdi...@rogueind.com Spamtrap address mtd...@rogueind.com
[Dovecot] Managesieve and Proxy
Hello list, is it possible to use the dovecot proxy feature for the mangaesieve server also ? Regards, Oliver
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Timo Sirainen wrote: >On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote: > >> First failure is: >> >> Sep 23 06:26:14 server dovecot: pop3-login: Fatal: >> io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted > >That's really the first one, and there's no kind of an error from >dovecot master process? This sounds like wrong fd is being passed to >pop3-login, but why it's being done only randomly I can't really think >of.. In my case, I see a few different kinds of messages. I posted a sequence earlier. Here it is again. At least one of each unusual message I see is included in this two minute period, and these are all the dovecot messages in that period and the initial message is the first unusual one that occurred. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 22 19:07:48 sbh16 dovecot: pop3-login: Login: user=, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Sep 22 19:07:48 sbh16 dovecot: POP3(mark): Disconnected: Logged out top=0/0, retr=0/0, del=0/218, size=2550090 Sep 22 19:08:15 sbh16 dovecot: dovecot: Created login processes successfully, unstalling Sep 22 19:08:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:08:15 sbh16 dovecot: dovecot: child 21735 (login) returned error 89 (Fatal failure) Sep 22 19:08:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 22 19:08:21 sbh16 dovecot: pop3-login: Login: user=, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Sep 22 19:08:22 sbh16 dovecot: POP3(mark): Disconnected: Logged out top=0/0, retr=1/57566, del=0/218, size=2550090 Sep 22 19:09:15 sbh16 dovecot: dovecot: Created login processes successfully, unstalling Also, here are all the dovecot messages from a five minute period when this first started. The scenario here is a remote machine connects every five minutes via an SSH tunnel and retrieves and deletes (with fetchmail pop3) all the mail for 4 users. Sep 21 03:28:17 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:28:17 sbh16 dovecot: POP3(fran): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 21 03:28:17 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:28:17 sbh16 dovecot: POP3(dma): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 21 03:28:17 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:28:17 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 21 03:28:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:28:28 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:28:28 sbh16 dovecot: POP3(aaron): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 21 03:29:28 sbh16 dovecot: dovecot: Created login processes successfully, unstalling Sep 21 03:29:28 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 21 03:29:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:30:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:31:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:32:28 sbh16 dovecot: dovecot: child 25038 (login) returned error 89 (Fatal failure) Sep 21 03:32:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:33:28 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 21 03:33:36 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:33:36 sbh16 dovecot: POP3(fran): Disconnected: Logged out top=1/21613, retr=0/0, del=1/1, size=21607 Sep 21 03:33:36 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Sep 21 03:33:36 sbh16 dovecot: POP3(dma): Disconnected: Logged out top=1/21607, retr=0/0, del=1/1, size=21601 I have installed the patch adding fd_debug_verify_leaks(io->fd, io->fd); and I will report any recurrence. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
[Dovecot] The file doesn't contain a certificate.
Yesterday I upgraded dovecot from 1.1.16 to 1.2.4 using portupgrade I am now getting the following messages in the log file: Sep 23 12:00:41 imap-login: Fatal: Can't load certificate file /etc/ssl/imaps.example.org.csr: The file doesn't contain a certificate. The certificate file contains exactly what it did before: -BEGIN CERTIFICATE REQUEST- MIIBhTCB7wIBADBGMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFDASBgNVBAcT C0xvcyBBbmdlbGVzMRQwEgYDVQQKEwtCb3hJU1AsIExMQzCBnzANBgkqhkiG9w0B AQEFAAOBjQAwgYkCgYEAue0xYWcYcLHQoI/nQj2tG3AV0Mepx1pvHbCSqmKxelyo z5cToH9kFIPzxDJvL8ChQ21ftM7m79ChfiXgWsUhHuaoeNdwr12FQ+nbbZoaELGZ 3keZv93rYkGstkL8zxTIquDq1dKSp+3e1T7M0ktphlYWuNEv8vHa4zM3n5izdmcC AwEAAaAAMA0GCSqGSIb3DQEBBQUAA4GBAA1JnGM4A5HvRy+TFjMrUHoJr79DaMpj qmKT2R5uW0iQnRGjrSfMCaZgyEQqKU5eCAVx5xTih7iO7VKLP5zKRVMSAJ5kQW1o 7bM/NvbnI+Jdz749VkZtUXWWVNlIB0uVXp++moWN5+y94kj3f1VhHQke+pS8NWGG YxhXEZtBBUdO -END CERTIFICATE REQUEST- I even tried creating an new certificate and still get the same error NO changes were made to any config files I have tried to test the connection by: telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. (at this point it hangs and never responds, I have to kill the pid) ANY help would be appreciated
Re: [Dovecot] The file doesn't contain a certificate.
On Qua, 23 Set 2009, A M wrote: Yesterday I upgraded dovecot from 1.1.16 to 1.2.4 using portupgrade I am now getting the following messages in the log file: Sep 23 12:00:41 imap-login: Fatal: Can't load certificate file /etc/ssl/imaps.example.org.csr: The file doesn't contain a certificate. The certificate file contains exactly what it did before: -BEGIN CERTIFICATE REQUEST- MIIBhTCB7wIBADBGMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFDASBgNVBAcT C0xvcyBBbmdlbGVzMRQwEgYDVQQKEwtCb3hJU1AsIExMQzCBnzANBgkqhkiG9w0B AQEFAAOBjQAwgYkCgYEAue0xYWcYcLHQoI/nQj2tG3AV0Mepx1pvHbCSqmKxelyo z5cToH9kFIPzxDJvL8ChQ21ftM7m79ChfiXgWsUhHuaoeNdwr12FQ+nbbZoaELGZ 3keZv93rYkGstkL8zxTIquDq1dKSp+3e1T7M0ktphlYWuNEv8vHa4zM3n5izdmcC AwEAAaAAMA0GCSqGSIb3DQEBBQUAA4GBAA1JnGM4A5HvRy+TFjMrUHoJr79DaMpj qmKT2R5uW0iQnRGjrSfMCaZgyEQqKU5eCAVx5xTih7iO7VKLP5zKRVMSAJ5kQW1o 7bM/NvbnI+Jdz749VkZtUXWWVNlIB0uVXp++moWN5+y94kj3f1VhHQke+pS8NWGG YxhXEZtBBUdO -END CERTIFICATE REQUEST- That's not a certificate, that's a certificate request. You send it to a company that sells certificates (along with your credit card number :-) ) and receive the certificate. Or you can generate a self-signed certificate by following the steps in http://openssl.linux-mirror.org/docs/HOWTO/certificates.txt . -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: [Dovecot] windows imap clients
On Wed, 23 Sep 2009, Charles Marcus wrote: On 9/23/2009, Charles Sprickman (sp...@bway.net) wrote: Charles (and Nikolay), thanks very much for pointing me at the TB3 beta. And of course, they just released b4... Literally the day after I upgraded to b3. :) I didnt check the changelog to see if any of your issues were addressed, but I certainly hope - since you are apparently going to continue using it - that you will help them fix these problems by updating to b4, and reporting any issues that still exist to bugzilla: Well, b3 took care of the offline access and the basic "search locally rather than server-side" issues quite well. b4 is like someone read my mind - the search field in the toolbar now can search everything, and the results are presented in a new tab. Nice layout - filters in the left pane to narrow the search, list of results in the right pane. 3.0 is really looking to be a nice release... Charles https://bugzilla.mozilla.org/ I'll report anything I can find/reproduce. -- Best regards, Charles
