On Wed, Apr 29, 2009 at 12:37:09AM -0500, James R. Leu wrote: > Hello, > > I'm new to the list and am looking for a recommendation > on where to post a question about a crash I seeing with > imapd. > > I'm going to include the info I have, if this is not the correct > info or the correct place, please kindly point out what I'm > missing or where I should post. Thanks. > > db4-4.3.29-9.fc6 > cyrus-imapd-2.3.7-2.el5 > kernel-2.6.18-92.1.22.el5 > > running on CentOS 5.2 > > I'm running cyrus-imapd inside a VirtualBox VM that gets > its disk via ISCSI. > > I see the imapd processes die in the 10's producing > core files that have the following stack trace. > > Core was generated by `imapd -s'. > Program terminated with signal 11, Segmentation fault. > [New process 27178] > #0 index_searchmsg (substr=0x96612c0 "statistics", pat=0x964cd70, > msgfile=0xbfa19604, format=0, skipheader=1, > cacheitem=0x2458eb6c <Address 0x2458eb6c out of bounds>) at index.c:3267 > 3267 subparts = CACHE_ITEM_BIT32(cacheitem); > (gdb) where > #0 index_searchmsg (substr=0x96612c0 "statistics", pat=0x964cd70, > msgfile=0xbfa19604, format=0, skipheader=1, > cacheitem=0x2458eb6c <Address 0x2458eb6c out of bounds>) at index.c:3267 > #1 0x00c2d979 in index_search_evaluate (mailbox=0xd30380, > searchargs=0x964dfd8, msgno=2934, msgfile=0xbfa19604) at index.c:3227 > #2 0x00c2dd1e in _index_search (msgno_list=0xbfa19644, mailbox=0xd30380, > searchargs=0x964dfd8, highestmodseq=0x0) at index.c:1012 > #3 0x00c2e135 in index_search (mailbox=0xd30380, searchargs=0x964dfd8, > usinguid=1) at index.c:1071 > #4 0x00c1116b in cmd_search (tag=0x9661768 "6", usinguid=1) at imapd.c:4465 > #5 0x00c1e2bc in cmdloop () at imapd.c:1664 > #6 0x00c20441 in service_main (argc=2, argvat imapd.c:793 > #7 0x00c04d21 in main (argc=2, argv=0xbfa1bea4, envp=0xbfa1beb0) > at service.c:532 > (gdb) > > When I searched > http://cyrusimap.web.cmu.edu/archive/search.php?mailbox=archive.cyrus-devel > for index_searchmsg, it only comes up with two hits for a patch by > Bron Gondwana <br...@fastmail.fm> from March. > > Is the above a known issue? If so, is there any sort of work around or > resource I can change to alleviate the issue? Otherwise can someone in the > know give me a rough idea of where in the life-cycle of the imapd process > this code path might be executed so I can start to dig into the issue > myself. > > Thank you in advance.
Walk up the tree up a couple of times and 'p *mailbox'. That will tell you which mailbox has the corrupted cache file. Then run reconstruct on that mailbox, which will fix the cache file. (the patches stop it crashing, but don't fix the cache file. There are also quite a few patches in more recent versions of cyrus that stop it corrupting cache files... 2.3.14 is pretty good. I think we've got most of them!) Regards, Bron.
