Le 07/04/2013 22:56, Timo Sirainen a écrit :
> On Sun, 2013-04-07 at 21:47 +0200, to...@starbridge.org wrote:
>> since I've upgraded to 2.2.rc5 (c24783148d78), I've got the previous
>> error again:
>> It's happening on a large mailbox on almost every emails, w
Le 19/03/2013 07:24, Tonio a écrit :
>
>
>
> Le 18 mars 2013 à 14:47, Timo Sirainen a écrit :
>
>> On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
>>> Hi Timo,
>>> I've got a crash with dovecot 2.2
>>>
>>> dovecot
Hi Timo,
I've got a crash with dovecot 2.2
dovecot --version
2.2.rc2 (69c26a9e3be5)
It's occured when accessing with imap on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254 > 4248,
pool )
Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(
Le 10/08/2012 01:34, Timo Sirainen a écrit :
> Actually it wasn't that obvious:
> http://hg.dovecot.org/dovecot-2.1/rev/b082b8260782 plus
> http://hg.dovecot.org/dovecot-2.1/rev/9d0873cefa08
Thanks Timo,
it's working fine now
Best regards
Tonio Buonaguidi
Le 08/08/2012 15:41, Timo Sirainen a écrit :
On 8.8.2012, at 9.42, to...@starbridge.org wrote:
I've just tried this patch, so far pop-login error doesnt shows up , but now
I've got this one: (imap-login this time)
Aug 8 08:19:36 eol1 dovecot: imap-login: Fatal: master: service(
Le 07/08/2012 17:21, Timo Sirainen a écrit :
On 7.8.2012, at 18.16, to...@starbridge.org wrote:
I will give it a try ASAP, but is it a bad thing to run dovecot with many local
{} ?
Not a bad thing, but it uses up somewhat more memory.
Timo,
I've just tried this patch, so far pop-
Le 07/08/2012 16:57, Timo Sirainen a écrit :
On 7.8.2012, at 15.54, to...@starbridge.org wrote:
#0 settings_parser_dup (old_ctx=0xa26920, new_pool=0x6d6f632e32) at
settings-parser.c:1742
new_ctx =
iter =
new_link =
links =
key =
value
Le 07/08/2012 13:47, to...@starbridge.org a écrit :
Hi Timo,
I've got some errors with pop3 proxying and dovecot 2.1.9
I's occured on the proxy side:
Aug 7 13:16:47 dev1 dovecot: pop3-login: Fatal: master:
service(pop3-login): child 23046 killed with signal 11 (core dumped)
S
Hi Timo,
I've got some errors with pop3 proxying and dovecot 2.1.9
I's occured on the proxy side:
Aug 7 13:16:47 dev1 dovecot: pop3-login: Fatal: master:
service(pop3-login): child 23046 killed with signal 11 (core dumped)
Server side shows no error, and runs the same dovecot version.
Than
Le 31/07/2012 21:04, Timo Sirainen a écrit :
> On 29.7.2012, at 2.20, to...@starbridge.org wrote:
>
>> it seems ok now with memory problem, but an other error shows up:
>>
>> doveadm -v index -u c...@spamguard.fr INBOX
>> doveadm(c...@spamguard.fr): Info: INBOX: Cachi
Le 28/07/2012 18:34, Timo Sirainen a écrit :
> On 28.7.2012, at 19.09, Matthew Powell wrote:
>
>> This looks very much like an issue I've been having with fts-lucene.
>> Indexing works (or at least completes without errors) in 2.1.7, but runs out
>> of memory in 2.1.8.
>>
>> doveadm -v index -u u
Le 28/07/2012 18:09, Matthew Powell a écrit :
> On 2012-07-28, at 11.21, to...@starbridge.org wrote:
>
>> Fatal: master: service(indexer-worker): child 9582 returned error 83
>> (Out of memory (service indexer-worker { vsz_limit=256 MB }, you may
>> need to increase it)
Hi Timo,
since I've upgraded to 2.1.8, solr indexer doesnt work correctly.
I see a lot of these errors in logs:
Fatal: master: service(indexer-worker): child 9582 returned error 83
(Out of memory (service indexer-worker { vsz_limit=256 MB }, you may
need to increase it))
I've tried to set vsz_li
13 matches
Mail list logo
