dovecot - Mar 2009 - dovecot-1.1.13 auth-worker killed

Hi,

I get these errors with dovecot 1.1.13 in my logs:

dovecot: Mar 27 12:00:34 Error: auth-worker(default): *** glibc detected ***
dovecot-auth: double free or corruption (!prev): 0x00002b30d5a7dd90 ***
dovecot: Mar 27 12:00:34 Error: auth(default):
worker-server(jan,147.251.48.141): Aborted: Worker process died unexpectedly
dovecot: Mar 27 12:00:34 Error: child 21838 (auth-worker) killed with signal 6
(core not dumped)
dovecot: Mar 27 12:10:23 Error: child 22711 (auth-worker) killed with signal 11
(core not dumped)
dovecot: Mar 27 12:10:23 Error: auth(default):
worker-server(thomas,209.85.146.140): Aborted: Worker process died unexpectedly

Haven't seen this with previous versions.

But somehow I fail to get the core dump. I do 'ulimit -c unlimited'
before starting dovecot,
I set
*               soft    core            8192
*               hard    core            8192
in limits.conf, /proc/sys/kernel/core_pattern is set to /tmp/core.

Regards,
Jiri Novosad

My dovecont -n:

# 1.1.13: /packages/run.64/dovecot-1.1.13//etc/dovecot.conf
# OS: Linux 2.6.18-92.1.22.el5 x86_64 Red Hat Enterprise Linux Server release
5.3 (Tikanga) ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot/log
info_log_path: /var/log/dovecot/info_log
protocols: pop3s imaps pop3 imap
listen(default): *
listen(imap): *
listen(pop3): *:110
ssl_listen(default): 
ssl_listen(imap): 
ssl_listen(pop3): *:995
ssl_cert_file: /etc/ssl/cert-anxur.fi.muni.cz.pem
ssl_key_file: /etc/ssl/serverkey-anxur.fi.muni.cz.pem
ssl_parameters_regenerate: 24
login_dir: /var/run/dovecot/login
login_executable(default):
/packages/run.64/dovecot-1.1.13/libexec/dovecot/imap-login
login_executable(imap):
/packages/run.64/dovecot-1.1.13/libexec/dovecot/imap-login
login_executable(pop3):
/packages/run.64/dovecot-1.1.13/libexec/dovecot/pop3-login
login_greeting: HI!
login_greeting_capability(default): yes
login_greeting_capability(imap): yes
login_greeting_capability(pop3): no
verbose_proctitle: yes
first_valid_uid: 200
mail_location: mbox:/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/home/%u/mail/.imap
mail_debug: yes
mail_full_filesystem_access: yes
maildir_copy_with_hardlinks: no
mbox_write_locks: fcntl
mbox_dirty_syncs: no
mbox_lazy_writes: no
dbox_rotate_days: 0
mail_drop_priv_before_exec: yes
mail_executable(default): /packages/run.64/dovecot-1.1.13/libexec/dovecot/imap
mail_executable(imap): /packages/run.64/dovecot-1.1.13/libexec/dovecot/imap
mail_executable(pop3): /packages/run.64/dovecot-1.1.13/libexec/dovecot/pop3
mail_plugin_dir(default): /packages/run.64/dovecot-1.1.13/lib/dovecot/imap
mail_plugin_dir(imap): /packages/run.64/dovecot-1.1.13/lib/dovecot/imap
mail_plugin_dir(pop3): /packages/run.64/dovecot-1.1.13//lib/dovecot/pop3
mail_log_max_lines_per_sec: 20
imap_max_line_length(default): 131072
imap_max_line_length(imap): 131072
imap_max_line_length(pop3): 65536
imap_client_workarounds(default): delay-newmail outlook-idle
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep
imap_client_workarounds(pop3): 
pop3_uidl_format(default): %08Xu%08Xv
pop3_uidl_format(imap): %08Xu%08Xv
pop3_uidl_format(pop3): %08Xv%08Xu
pop3_client_workarounds(default): 
pop3_client_workarounds(imap): 
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
  executable: /packages/run.64/dovecot-1.1.13/libexec/dovecot/dovecot-auth
  verbose: yes
  debug: yes
  passdb:
    driver: pam
    args: dovecot
  userdb:
    driver: passwd

On Fri, 2009-03-27 at 12:31 +0100, Jiri Novosad wrote:
> dovecot: Mar 27 12:00:34 Error: auth-worker(default): *** glibc detected
*** dovecot-auth: double free or corruption (!prev): 0x00002b30d5a7dd90 ***
Heap corruption, not good. How often does this happen?
> dovecot: Mar 27 12:00:34 Error: child 21838 (auth-worker) killed with
signal 6 (core not dumped)
> dovecot: Mar 27 12:10:23 Error: child 22711 (auth-worker) killed with
signal 11 (core not dumped)
It says it dumped core file, so it did write it somewhere. You just
might not be finding it.
> in limits.conf, /proc/sys/kernel/core_pattern is set to /tmp/core.
auth-workers are chdired to Dovecot's base_dir (e.g. /var/run/dovecot).
The core file is normally written there, do you see it? Try removing
path from core_pattern and see if it shows up there then?
>   passdb:
>     driver: pam
>     args: dovecot
What PAM configuration are you using?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20090401/7bbf52a7/attachment-0002.bin>

On 4/1/2009 5:25 PM, Timo Sirainen wrote:
>> dovecot: Mar 27 12:00:34 Error: child 21838 (auth-worker) killed with
signal 6 (core not dumped)
>> dovecot: Mar 27 12:10:23 Error: child 22711 (auth-worker) killed with
signal 11 (core not dumped)
> It says it dumped core file, so it did write it somewhere. You just
> might not be finding it.
? (core not dumped) means it *did* dump it? Ok, so what am I missing?

-- 

Best regards,

Charles