Stripping of attachments using Horde 4/IMP 5.

Tue Jan 1 01:15:12 EST 2013

----- Message from awilliam at whitemice.org ---------
     Date: Mon, 31 Dec 2012 11:10:43 -0500
     From: Adam Tauno Williams <awilliam at whitemice.org>
Reply-To: awilliam at whitemice.org
  Subject: Re: Stripping of attachments using Horde 4/IMP 5.
       To: info-cyrus at lists.andrew.cmu.edu

> On Mon, 2012-12-31 at 10:33 +0100, Simon Matter wrote:
>> > The databases used are:
>> > -rw------- 1 cyrus mail 144 Dec  9 09:29 ./annotations.db
>> > ./annotations.db: Cyrus skiplist DB
>> > -rw------- 1 cyrus mail 144 Dec 30 11:30 ./db.backup1/annotations.db
>> > ./db.backup1/annotations.db: Cyrus skiplist DB
>> > -rw------- 1 cyrus mail 1882668 Dec 30 11:30 ./db.backup1/mailboxes.db
>> > ./db.backup1/mailboxes.db: Cyrus skiplist DB
>> > -rw------- 1 cyrus mail 144 Dec 30 11:00 ./db.backup2/annotations.db
>> > ./db.backup2/annotations.db: Cyrus skiplist DB
>> > -rw------- 1 cyrus mail 1882668 Dec 30 11:00 ./db.backup2/mailboxes.db
>> > ./db.backup2/mailboxes.db: Cyrus skiplist DB
>> > -rw------- 1 cyrus mail 18038784 Dec 30 11:30 ./deliver.db
>> > ./deliver.db: Berkeley DB (Btree, version 9, native byte-order)
>
> I can't image how the delivery database would create the problem you
> describe; so I'd doubt it is that.
>
> Irregardless of where the data is physically stored, does the filesystem
> pass an fsck?
>
>> > I don't have backtrace?  I am using RHEL rpms.
>
> That doesn't in any way prevent you from generating a backtrace.  You
> have a core file, just use gdb to generate the backtracr.
>
>> Unfortunately we can also not see what has been changed in the patched
>> RPMs you got from RH.
>> > But, is it OK to use NetApp Storage for /var/lib/imap file system?
>> NetApp often sounds like NFS but you told us you are not using NFS but FC
>> attached disks? If so I don't know why it shouldn't work exactly as local
>> disks would.
>
> +1 An FC or iSCSI attached volume *is* as a local disk.
>
>> But when I hear Horde/IMP I remember a problem that some people hit after
>> upgrading Horde/IMP. I don't remember what it was but you should find it
>> in the archives. IIRC it has been fixed in the latest version of
>> cyrus-imapd.
>
>
> --
> Adam Tauno Williams  GPG D95ED383
> Systems Administrator, Python Developer, LPI / NCLA
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>

I am trying generating backtrace for the first time.  Here is what I  
have run and the corresponding outouts.  Please guide me, if I need to  
do something more.

Host>gdb /usr/lib/cyrus-imapd/imapd coredump
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-56.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/cyrus-imapd/imapd...(no debugging  
symbols found)...done.
[New Thread 6949]
Reading symbols from /usr/lib64/libsasl2.so.2...(no debugging symbols  
found)...done.
Loaded symbols for /usr/lib64/libsasl2.so.2
Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging  
symbols found)...done.
Loaded symbols for /lib64/libgssapi_krb5.so.2
Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libkrb5.so.3
Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libk5crypto.so.3
Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libcom_err.so.2
Reading symbols from /lib64/libkrb5support.so.0...(no debugging  
symbols found)...done.
Loaded symbols for /lib64/libkrb5support.so.0
Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols  
found)...done.
Loaded symbols for /usr/lib64/libssl.so.10
Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/libcrypto.so.10
Reading symbols from /lib64/libresolv.so.2...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libresolv.so.2
Reading symbols from /lib64/libdb-4.7.so...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libdb-4.7.so
Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libz.so.1
Reading symbols from /lib64/libwrap.so.0...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libwrap.so.0
Reading symbols from /lib64/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libnsl.so.1
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libdl.so.2
Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libcrypt.so.1
Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libkeyutils.so.1
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols  
found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /lib64/libpthread.so.0
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging  
symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib64/libselinux.so.1...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libselinux.so.1
Reading symbols from /lib64/libfreebl3.so...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libfreebl3.so
Reading symbols from /usr/lib64/sasl2/libanonymous.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libanonymous.so
Reading symbols from /usr/lib64/sasl2/libcrammd5.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libcrammd5.so
Reading symbols from /usr/lib64/sasl2/libplain.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libplain.so
Reading symbols from /usr/lib64/sasl2/libsasldb.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libsasldb.so
Reading symbols from /usr/lib64/sasl2/liblogin.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/liblogin.so
Reading symbols from /usr/lib64/sasl2/libgssapiv2.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libgssapiv2.so
Reading symbols from /usr/lib64/sasl2/libdigestmd5.so...(no debugging  
symbols found)...done.
Loaded symbols for /usr/lib64/sasl2/libdigestmd5.so
Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols  
found)...done.
Loaded symbols for /lib64/libnss_files.so.2
Core was generated by `imapd'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007fc3605fc9c1 in ?? ()
Missing separate debuginfos, use: debuginfo-install  
cyrus-imapd-2.3.16-6.el6_2.5.x86_64
(gdb) bt
#0  0x00007fc3605fc9c1 in ?? ()
#1  0x00007fc360603998 in ?? ()
#2  0x00007fc3605efba6 in ?? ()
#3  0x00007fc3605f5488 in ?? ()
#4  0x00007fc3605f7dd1 in ?? ()
#5  0x00007fc3605df1e9 in main ()
(gdb)

----- End message from awilliam at whitemice.org -----

------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------