On Tue, 2008-09-16 at 10:34 -0300, Allan Cassaro wrote: > Hi, always when my server is on high load I saw this errors on logs: > > curie:~# uptime > 10:22:38 up 19 days, 19:19, 2 users, load average: 207.01, 169.27, 94.41 > > Sep 15 17:00:26 curie dovecot: imap-login: *** glibc detected *** > imap-login: malloc(): memory corruption: 0x00000000009f8560 *** > Sep 15 17:00:26 curie dovecot: child 24012 (login) killed with signal 6 > Sep 15 18:48:36 curie dovecot: auth(default_with_listener): BUG: > Authentication client said it's PID 0 > Sep 15 18:48:36 curie dovecot: child 24014 (login) killed with signal 11 > Sep 16 09:05:19 curie dovecot: imap-login: *** glibc detected *** > imap-login: malloc(): memory corruption: 0x00000000008c4bc0 *** > Sep 16 09:05:19 curie dovecot: child 24013 (login) killed with signal 6 > Sep 16 10:17:14 curie dovecot: imap-login: *** glibc detected *** > imap-login: malloc(): memory corruption: 0x000000000098bb30 *** > Sep 16 10:17:14 curie dovecot: child 24015 (login) killed with signal 6 > Sep 16 10:19:02 curie dovecot: child 24002 (login) killed with signal 6 > Sep 16 10:19:02 curie dovecot: managesieve-login: *** glibc detected > *** managesieve-login: double free or corruption (!prev):
These are pretty scary. If a user could cause these on will, it could mean a remotely exploitable security hole. But I've not been able to produce such crashes for a long time now and I haven't heard it happening with other people either. You sure the server's memory is OK? Another thing I could blame instead of Dovecot is OpenSSL :) > Sep 16 10:19:18 curie dovecot: Panic: IMAP(geduardo): file > maildir-save.c: line 241 (maildir_get_updated_filename): assertion > failed: (ctx->keywords_sync_ctx != NULL || mf->keywords_count == 0) This I fixed recently though: http://hg.dovecot.org/dovecot-1.1/rev/2922490759c9
signature.asc
Description: This is a digitally signed message part
