Displaying 20 results from an estimated 2000 matches similar to: "Dovecot 2.1rc1 + 2.0.16 woes regarding fts_squat"
2010 Jan 30
2
failed: Cannot allocate memory
Hi
when I try to index messages using squat on a 26'000 emails mailbox I
get the below errors at the point dovecot says "* OK Mailbox indexing
finished".
2010-01-30 08:12:50 sleipnir local7.err dovecot IMAP(spam at dom.com):
read(/var/tmp/dovecot/spam/indexes/.INBOX_score20/dovecot.index.search.uids)
failed: Cannot allocate memory
2010-01-30 08:12:50 sleipnir local7.err
2019 Mar 20
0
Dovecot crashing when attempting to search in virtual folder with fts_squat activated
Hi everyone,
I have now updated to dovecot 2.3.4.1 - unfortunately the issue still
persists. Can anyone help me figure out if this is due to a
misconfiguration on my part or another error?
Any help is greatly appreciated!
Cheers
Benjamin
Am 14.03.2019 um 23:28 schrieb benjamin at godbersen.info:
> Hi everyone,
>
> I am running into a problem when trying to use fts_squat in a virtual
2019 Mar 20
0
Dovecot crashing when attempting to search in virtual folder with fts_squat activated
Hi Michael,
thanks for getting back to me. I understand the alternatives to squat
are solr and lucene and have to be explicitly included into dovecot at
compilation. Unfortunately I am not in a position to manually compile
dovecot.
What other option do I have to use full text search in dovecot without
manually compilating my package?
Thanks and cheers
Benjamin
Am 20.03.2019 um 20:31
2009 Jul 24
2
fts_squat + virtual => crash
Hi,
dovecot's imap process segfaults when I search a virtual mailbox using
the fts_squat plugin. Is this supposed to work, or a known bug?
I've seen some changes commited to fts_solr a couple of months ago
that where supposed to fix search issues on virtual mailboxes, maybe
fts_squat needs to be fixed to?
log
===
rawlog
------
3551 SELECT "INBOX.virtual.unseen"
3552 UID
2012 Jun 16
3
question about fts_squat
just installed dovecot with fts_squat
config attached after message.
When i telnet to imap server and execute by hand
1 login user password
select foldername
search body "someword"
it works fine, and at blazing speed except first run (indexing).
i already indexed everything by doveadm index offline to prevent server
overload if multiple users (after i tell them) will try fulltext
2015 Oct 01
0
Does fts_lucene need fts_squat?
Hi ML!
Please look at this:
- I've got no lucene-index:
> # ls /dane/domeny/mejor.pl/mail/marcin/.maildir/lucene-indexes
> ls: cannot access /dane/domeny/mejor.pl/mail/marcin/.maildir/lucene-indexes: No such file or directory
- run search in body:
> echo -e "a select bugzilla\na search body flto\na logout\n" | /usr/libexec/dovecot/imap -u marcin at mejor.pl
> * PREAUTH
2015 Nov 03
0
[dovceot-2.2.19] doveadm fetch with fts_squat returns random results
Hi all!
I've got problem with results returned by doveadm fetch. The are random
and incorrect. I'll try show you:
- trying to fetch emails with both: nonexistent header name and non
existent value of header name:
-- doveadm fetch -u user at domain uid HEADER X-Sasdasdsendasasdasdasdasaer
XXtuxie |grep -c uid
0
- trying to fetch email with: non existent header name and existent
value of
2019 Mar 20
1
Dovecot crashing when attempting to search in virtual folder with fts_squat activated
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
We provide packages at https://repo.dovecot.org - maybe you can use these?
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
<div>
On 20 March 2019 22:19 Benjamin
2019 Mar 14
2
Dovecot crashing when attempting to search in virtual folder with fts_squat activated
Hi everyone,
I am running into a problem when trying to use fts_squat in a virtual
folder. Without fts_squat plugin the search (from, subject...) works in
all folders. With activated fts the search on the inbox folders works
expectedly well but any attempt to search anything in any virtual folder
leads to the following error. Similarly when attempting "doveadm fts
lookup". I also
2010 Sep 17
1
fts_squat hanging on some messages
Hello,
I recently upgraded to dovecot 2.0.2 (on gentoo ~amd64) and now
fts_squat's index building seems to hang for some of my mailboxes. The
imap process gets stuck at 100% cpu usage and dovecot.index.search is
never touched.
I traced the problem to a message (attached) for one of the
problematic mailboxes. Also attached are a full backtrace and the
output of dovecot -n.
The problem
2019 Mar 20
2
Dovecot crashing when attempting to search in virtual folder with fts_squat activated
fts_squat was deprecated in 2.1. There's a high likelihood it is buggy in a variety of ways in any recent Dovecot release.
michael
> On March 20, 2019 at 1:21 PM Benjamin Godbersen via dovecot <dovecot at dovecot.org> wrote:
>
> Hi everyone,
>
> I have now updated to dovecot 2.3.4.1 - unfortunately the issue still persists. Can anyone help me figure out if
2011 Nov 28
0
squat fts not working on 2.1rc1
Hello,
I tried to upgrade from 2.0.15 to 2.1.rc1 over the weekend but ran into
some problems with squat. My two largest mailboxes were corrupted,
producing this error:
Nov 27 17:38:12 kerio1 dovecot[42860]: imap(bigmailbox): Error:
Corrupted squat uidlist file
/var/mail/metro-email.com/bigmailbox/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.search.uids:
wrong indexid
There is a good chance
2006 Nov 23
1
rc15 dumped core
We have been running rc15 since Sunday experiencing no trouble,
but today one user crashed.
rc15 on Solaris-5.9, the server had app 6GB free memory at the time
of the crash, app 70% idle running with an avg.load at 4 of 8
processors available. The USER's INBOX was quite smooth, app 13MB
containing 320 messages.
The core dump was accompanied with these log-entries:
Nov 23 2006
12:27:00
2007 Nov 17
1
crash with fts_squat on an identified email
I have some folders with a good amount of spam. While demonstrating full text search to a user,
we found a folder that would crash dovecot while doing a fts. While splitting up the mailbox to
narrow it down, I found there are a good number of messages in that folder that all made it crash
in the same manner. I figured I'd narrow down a single one, get that fixed, then retest the rest.
I
2014 Dec 08
2
Error: mremap_anon(###) failed: Cannot allocate memory
We're running dovecot 2.2.15 with pigeonhole 0.4.6, in a clustered
environment, nfs with proxy and backend on all servers.
I've been seeing some odd errors from lmtp:
Error: mremap_anon(127930368) failed: Cannot allocate memory
It seems to affect specific users, but it doesn't seem to manifest in any
particular way; no user complaints. Just the occasional log message.
I would
2014 Dec 08
0
Error: mremap_anon(###) failed: Cannot allocate memory
On 12/08/2014 02:54 AM, Andy Dills wrote:
>
> We're running dovecot 2.2.15 with pigeonhole 0.4.6, in a clustered
> environment, nfs with proxy and backend on all servers.
>
> I've been seeing some odd errors from lmtp:
>
> Error: mremap_anon(127930368) failed: Cannot allocate memory
>
> It seems to affect specific users, but it doesn't seem to manifest
2019 Jun 20
0
mremap_anon() failed: Not enough space
On 19 Jun 2019, at 13:13, Dave McGuire via dovecot <dovecot at dovecot.org> wrote:
> Jun 19 14:47:31 <hostname> dovecot: [ID 583609 local0.error]
> imap(<address>): Error:
> mremap_anon(/var/mail/<domain>/<uname>/mailboxes/INBOX/Trash/dbox-Mails/dovecot.index.cache,
> 255557632) failed: Not enough space
>
> I'm running 2.2.36.1 under Solaris 10
2019 Jun 20
0
mremap_anon() failed: Not enough space
> It?s also possible that the cache files USED to grow quite large in
> previous versions and that now they are much more reasonable, but the
> only way to reset their size appears to be to delete them and let
> dovecot rebuild them.
I seem to recall these cache files ballooned in size when I did some
doveadm search queries -- under some circumstances some headers fetches
are cached
2019 Jun 20
1
mremap_anon() failed: Not enough space
On 6/20/19 6:07 AM, @lbutlr via dovecot wrote:
>> Jun 19 14:47:31 <hostname> dovecot: [ID 583609 local0.error]
>> imap(<address>): Error:
>> mremap_anon(/var/mail/<domain>/<uname>/mailboxes/INBOX/Trash/dbox-Mails/dovecot.index.cache,
>> 255557632) failed: Not enough space
>>
>> I'm running 2.2.36.1 under Solaris 10 (patched to
2012 May 11
2
multi-instance doveadm user -m woes
I'm having difficulty with the doveadm who command on a multi-instance setup of dovecot. When I run the who command on the non-standard instance with the -m flag (to see their mail location), this happens:
[root at wardentest3 dovecot]# doveadm -i mailtest user -m warden
doveadm(root): Error: user warden: Initialization failed: Namespace 'INBOX.': Ambiguous mail location setting,