Your message dated Mon, 14 Sep 2009 12:10:28 -0400
with message-id <[email protected]>
and subject line Re: Bug#536247: dovecot-common: dovecot-auth segfaults randomly
has caused the Debian Bug report #536247,
regarding dovecot-common: dovecot-auth segfaults randomly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
536247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536247
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dovecot-common
Version: 1:1.1.16-1
Severity: important


Several times a day, dovecot-auth crashes, disconnecting the connected
users of course.  syslog output from one day is below.  Thanks, Andrew.

messages.4.gz:Jul  2 12:26:24 helium kernel: dovecot-auth[26364]: segfault at 
100000008 ip 7faf466441eb sp 7fff50a3f260 error 4 in 
libc-2.9.so[7faf465d2000+149000]
messages.4.gz:Jul  2 13:43:31 helium kernel: dovecot-auth[32422]: segfault at 
100000008 ip 7fd2bc7551eb sp 7fffc6b50370 error 4 in 
libc-2.9.so[7fd2bc6e3000+149000]
messages.4.gz:Jul  2 15:06:39 helium kernel: dovecot-auth[1611]: segfault at 
100000008 ip 7f59c2df61eb sp 7fffcd1f2a10 error 4 in 
libc-2.9.so[7f59c2d84000+149000]
messages.4.gz:Jul  2 16:28:47 helium kernel: dovecot-auth[17309]: segfault at 
100000008 ip 7f5b0a2f51eb sp 7fff146eff10 error 4 in 
libc-2.9.so[7f5b0a283000+149000]


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (300, 'unstable'), (200, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dovecot-common depends on:
ii  adduser                3.110             add and remove users and groups
ii  libbz2-1.0             1.0.5-2           high-quality block-sorting file co
ii  libc6                  2.9-13            GNU C Library: Shared libraries
ii  libcomerr2             1.41.3-1          common error description library
ii  libdb4.7               4.7.25-7          Berkeley v4.7 Database Libraries [
ii  libgssapi-krb5-2       1.7dfsg~beta3-1   MIT Kerberos runtime libraries - k
ii  libk5crypto3           1.7dfsg~beta3-1   MIT Kerberos runtime libraries - C
ii  libkrb5-3              1.7dfsg~beta3-1   MIT Kerberos runtime libraries
ii  libldap-2.4-2          2.4.15-1.1        OpenLDAP libraries
ii  libmysqlclient15off    5.0.81-1          MySQL database client library
ii  libpam-runtime         1.0.1-9           Runtime support for the PAM librar
ii  libpam0g               1.0.1-9           Pluggable Authentication Modules l
ii  libpq5                 8.3.7-1           PostgreSQL C client library
ii  libsqlite3-0           3.6.14.2-1        SQLite 3 shared library
ii  libssl0.9.8            0.9.8k-3          SSL shared libraries
ii  openssl                0.9.8k-3          Secure Socket Layer (SSL) binary a
ii  ucf                    3.0018            Update Configuration File: preserv
ii  zlib1g                 1:1.2.3.3.dfsg-13 compression library - runtime

dovecot-common recommends no packages.

Versions of packages dovecot-common suggests:
ii  ntp                     1:4.2.4p6+dfsg-2 Network Time Protocol daemon and u
ii  ntpdate                 1:4.2.4p6+dfsg-2 client for setting system time fro

-- no debconf information



--- End Message ---
--- Begin Message ---
I was never able to track this down with valgrind.  Following Heisenberg's 
uncertainty principle, it seems that instrumenting the problem changed it.

Now I've upgraded to dovecot 1.2.4-2, removed all of the debugging 
configuration including valgrind, and I haven't observed this problem any 
more.  Since I can no longer reproduce the problem, I'm closing this bug.

Thanks for your help.
Andrew.


--- End Message ---

Reply via email to