reconstruct segfault, questions regarding databases
Hi there, I'm trying to migrate cyrus to new servers which means the 32 bit machines will be replaced by 64 bit and 2.4.17 will be replaced by 2.5.6. Almost all databases should already be skiplist. To test the migration I restored the mailspool and made sure ownership is correct. Now if I run reconstruct -V max as the cyrus user, reconstruct crashes every couple of mailboxes leaving a log entry I don't understand, e.g.: reconstruct[21388]: WARNING: trying to rename cache file user.username.Folder (1 < 2) reconstruct[21388]: IOERROR: failed to load cache for user.username.Folder reconstruct[21388]: user.username.Folder: missing cache file, recreating kernel: [174505.936323] reconstruct[21388]: segfault at 4 ip 7ff81bddda58 sp 7fff88baa060 error 4 in libcyrus_imap.so.0.0.0[7ff81bdb+6b000] I don't see where that IOERROR could have come from, the cache file for the folder in question is there and accessible. On the next run of reconstruct this mailbox will be finished, but reconstruct will crash on another mailbox, so if I run it several times all mailboxes should be ok. It just doesn't seem very trustworthy... Another error I don't understand is DBERROR db5: Program version 5.1 doesn't match environment version blabla quota[2478]: DBERROR: dbenv->open '/var/spool/imap/db' failed: DB_VERSION_MISMATCH: Database environment version mismatch '/var/spool/imap/db' is a directory, so how can there be a database mismatch ? Inside this directory there are a couple of __db* files, that 'file' doesn't recognize, but also a file named log.10 that seems to be bdb. What are they and should they be deleted before the reconstruct ? Is there an advantage of choosing a single quota db rather than quotalegacy ? Would the usage of a single db file in twoskip format be faster ? Regards, Stephan 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
reconstruct crash in 2.5.6
Hello list, I'm still trying to migrate my 2.4. servers to 2.5.6 and end up with a crashing reconstruct -G. I ran reconstruct with gdb attached and got this: user.pete.Gesendet: missing cache file, recreating Program received signal SIGSEGV, Segmentation fault. cache_parserecord (cachebase=cachebase@entry=0x64c038, cache_offset=4, crec=crec@entry=0x7fff93c0) at imap/mailbox.c:441 441 crec->item[cache_ent].len = CACHE_ITEM_LEN(cacheitem); (gdb) bt #0 cache_parserecord (cachebase=cachebase@entry=0x64c038, cache_offset=4, crec=crec@entry=0x7fff93c0) at imap/mailbox.c:441 #1 0x77b8c64c in mailbox_cacherecord (mailbox=mailbox@entry=0x64c018, record=record@entry=0x7fff9330) at imap/mailbox.c:637 #2 0x77b921fa in mailbox_reconstruct_compare_update (discovered=0x7fff91c0, have_file=1, flags=28, valid_user_flags=0x7fff9190, record=0x7fff9330, mailbox=0x64c018) at imap/mailbox.c:4570 #3 mailbox_reconstruct (name=name@entry=0x603b80 "user.pete.Gesendet", flags=28) at imap/mailbox.c:5087 #4 0x0040299f in do_reconstruct (name=0x7fffc740 "user.pete.Gesendet", matchlen=18, maycreate=, rock=0x0) at imap/reconstruct.c:465 #5 0x77b97a70 in find_cb (rockp=rockp@entry=0x7fffcc50, key=key@entry=0x77e85a0c "user.pete.Gesendet", keylen=keylen@entry=18, data=, datalen=) at imap/mboxlist.c:2243 #6 0x7783ff7f in myforeach (db=0x629450, prefix=0x7fffd0d0 "*", prefixlen=0, goodp=0x77b97400 , cb=0x77b978d0 , rock=0x7fffcc50, tidptr=) at lib/cyrusdb_skiplist.c:1160 #7 0x77b9b516 in mboxlist_findall (namespace=0x603ac0, pattern=0x629270 "", isadmin=1, userid=, auth_state=, proc=0, rock=0x0) at imap/mboxlist.c:2559 #8 0x00402346 in main (argc=2, argv=0x7fffe728) at imap/reconstruct.c:326 Is there anything I can do about this ? Thanks, Stephan 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
Weird Characters in unexpunge
Hello all, unexpunge (cyrus 2.5.7) is showing weird behaviour when it comes to subject lines containing the double quotation mark ("). When running reconstruct -l the subject lines containg a '"' show up as {}Subject, for instance Subj: {109} Cron I redirected the output to a file and opened it with vim, which shows a ^M before end of the line, which is a carriage return if I'm not mistaken. So I guess there is a involved. The mail as such looks perfectly fine. Is this a feature or should I open a bug report ? Thanks, Stephan 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
Strange behaviour
Hi, I have a problem with cyrus imapd 2.5.7 - I connect to it with two clients, both of which are turned off over night. The processes however stay and if I start the clients again on the next morning, new processes get spawned instead of reusing the old ones. This continues till the limit for maxchild gets hit. When shutting down via initscript. which just sends a SIGTERM to the master process, there remain more or less zombies of imapd procs which can only be eliminated by sending a SIGKILL to the master. In the logs I see that some of the imapd procs stopped the way they should: imaps[13135]: graceful shutdown Others seemed hesitant: master[11489]: process type:SERVICE name:imaps path:/usr/local/bin/imapd age:36588.013s pid:13138 exited, status 75 Is there any way to resolve this ? So far I had to restart cyrus every other day to have access to my mail. Thanks, Stephan 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
Re: Strange behaviour
Thanks, that did the trick ! Cheerio, Stephan Am 06.03.2016 um 20:44 schrieb Nicola Nye via Info-cyrus: Hi Stephen, I remember documenting a similar problem not too long ago. Take a look at http://cyrusimap.org/imap/faqs/o-toomanyprocesses.html And see if there's any information there which helps. Cheers, Nicola - Original message - From: "Stephan via Info-cyrus" To: Info Cyrus Subject: Strange behaviour Date: Sat, 5 Mar 2016 10:37:26 +0100 Hi, I have a problem with cyrus imapd 2.5.7 - I connect to it with two clients, both of which are turned off over night. The processes however stay and if I start the clients again on the next morning, new processes get spawned instead of reusing the old ones. This continues till the limit for maxchild gets hit. When shutting down via initscript. which just sends a SIGTERM to the master process, there remain more or less zombies of imapd procs which can only be eliminated by sending a SIGKILL to the master. In the logs I see that some of the imapd procs stopped the way they should: imaps[13135]: graceful shutdown Others seemed hesitant: master[11489]: process type:SERVICE name:imaps path:/usr/local/bin/imapd age:36588.013s pid:13138 exited, status 75 Is there any way to resolve this ? So far I had to restart cyrus every other day to have access to my mail. Thanks, Stephan 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 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 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