Re: imapd (3.4.2) crashes on SEARCH RECENT - setting search_engine to none solves it.

Stephan Rattai <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi,

I guess you ran into this issue:

https://github.com/cyrusimap/cyrus-imapd/issues/3588

I tried to switch to Xapian but support for Xapian failed to compile under Debian, so I don't have an working search engine at the moment. 

Am 2. Februar 2022 23:30:35 MEZ schrieb Pascal Gienger via Info <[email protected]>:
>Setting the setting
>
>search_engine = none
>
>instead of
>
>search_engine = squat
>
>removes the crash and also returns useful results again.
>But that actually removes the possibility to make effective searches in
>
>the body text.
>Any hints in which direction I should look at?
>
>
>relevant parts of imapd.conf:
>
>conversations: 1
>conversations_keep_existing: 1
>search_engine: none
>sync_log: on
>sync_log_channels: squatter
>
>
>On 1/31/2022 9:02 PM, Pascal Gienger via Info wrote:
>> On 1/31/2022 8:46 PM, pascal via Info wrote:
>>> Dear cyrus maintainers,
>>>
>>> I compiled Cyrus IMAP 3.4.2 and upgraded all mailboxes to Version 17
>>> (worked without any problem).
>>>
>>> But:
>>> I have a reproducible crash.
>>> Data:
>>> - The mailbox is empty. But the same occurs on a normal filled
>mailbox.
>>> - Ubuntu 20.04.03 LTS
>>> - Self compiled from 3.4.2 tarball.
>>> - Mailbox migration was done via  reconstruct -V max  (finished 
>>> without error).
>>> - Backtrace shows SQUAT. But I recreated the squat index for that
>user 
>>> to check. Other body searches do work.
>>> - No murder.
>>> - No unix hierarchy divider.
>>> - no virtual domains.
>> 
>> Addon: I upgraded from Cyrus 3.2.4. Same config parameters. 3.2.4 did
>> not have this problem.
>> 

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T07a23f0783976d79-M6565f956a1da94d4e04fd1b4
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.