Displaying 20 results from an estimated 1000 matches similar to: "dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory"
2016 Mar 30
2
crash after out of memory?
We're encountering a crash when proxying to an Exchange server:
Mar 30 10:40:47 mproxy dovecot: imap-login: Login: user=<xxxbxxx>, method=PLAIN, rip=10.39.76.71, lip=141.42.206.11, mpid=18556, TLS, session=<H98xGkAvfvMKJ0xH>
Mar 30 10:40:49 mproxy dovecot: imap(xxxbxxx): Fatal: block_alloc(134217728): Out of memory
Mar 30 10:40:49 mproxy dovecot: imap(xxxbxxx): Error: Raw
2018 Apr 11
0
two unrelated issues, lastlogin, and an out of memory fatal error
Hi!
On 10.04.2018 19:31, David Mehler wrote:
> Hello,
>
> I've got a few misc issues that I'm trying to get a handle on.
>
> I'm having what is probably a simple error with last logins. It's not
> working, unable to write values to the database. Here's the log lines:
>
> 2018-04-10 10:43:34 imap-login: Info: Login: user=<user at domain.com>,
>
2018 Apr 11
3
two unrelated issues, lastlogin, and an out of memory fatal error
Hello Aki,
Thanks for your suggestion. I followed it and the wiki at:
https://wiki.dovecot.org/Plugins/LastLogin
Good news, I get a record in the users table, with the username that
just logged in. This is good. Bad news is I got unexpected output from
the last_login time stamp. Here's the table and the user:
mysql> describe users;
2018 Apr 10
2
two unrelated issues, lastlogin, and an out of memory fatal error
Hello,
I've got a few misc issues that I'm trying to get a handle on.
I'm having what is probably a simple error with last logins. It's not
working, unable to write values to the database. Here's the log lines:
2018-04-10 10:43:34 imap-login: Info: Login: user=<user at domain.com>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=75934, TLS,
2009 Jan 13
4
Out of memory
Sorry for previous post with incorrect referrals/thread.
For large mailboxes (64k + messages) using maildir I got random "out
of memory" errors.
[mail addresses hidden]
dovecot: Dec 05 18:25:27 Error: IMAP(****@****): block_alloc(): Out of memory
dovecot: Dec 05 18:25:27 Error: child 14142 (imap) returned error 83 (Out of memory)
dovecot: Dec 05 18:27:29 Error: IMAP(****@****):
2018 Sep 10
0
make check (pigeonhole)
I did so as non-root user and got the same error.
On 9/10/2018 9:10 AM, Aki Tuomi wrote:
> Have you attempted this as non-root user?
>
>
>
> ---
> Aki Tuomi
> Dovecot oy
>
> -------- Original message --------
> From: Eric Broch <ebroch at whitehorsetc.com>
> Date: 10/09/2018 18:03 (GMT+02:00)
> To: dovecot at dovecot.org
> Subject: Re: make check
2016 May 15
2
indexer-worker out of memory with vsz_limit=750 MB?!
We're running 2.2.24 with fts_lucene and I wonder why indexer-working
can be out-of-memory even with
vsz_limit=750 MB
?!
Peer
May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Fatal:
pool_system_realloc(134217728): Out of memory
May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xaa4b7)
2010 Aug 18
1
Error: Index file too large ? 904 bytes ?
My 1.2.13 build is giving me errors based on the same conf file that was working perfectly for 1.2.12 :
Aug 18 03:28:27 IMAP(dclarke): Error: Index file too large: /var/mail/dclarke/dovecot.index
Aug 18 03:28:27 IMAP(dclarke): Fatal: block_alloc(2147483648): Out of memory
Aug 18 03:28:27 dovecot: Error: child 12560 (imap) returned error 83 (Out of memory - see mail_process_size setting)
The
2018 Sep 10
1
make check (pigeonhole)
Dovecot list,
1) I downloaded latest dovecot and pigeonhole tar balls and extracted on
latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and
dovecot-2.3-pigeonhole-0.5.2.tar.gz
2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into
dovecot (dovecot-2.3.2.1) directory
3) built dovecot with following config and paramerters:
patch -p1 <
2014 Sep 05
0
lmtp memory usage problem - Fatal: pool_system_realloc(268435456): Out of memory
Hi.
In my setup exim delivers mails to dovecot using LMTP. In one LMTP session exim
can deliver up to 200 recipients (batch_max set to that value).
Now the problem is that sometimes 256MB is not enoug for dovecot lmtp to handle
incoming emails.
My questions:
- how big memory limit should be for lmtp? I was thinking that lmtp (more or less) simply
reads from one descriptor and writes to file,
2019 May 13
6
Frequent Out of Memory for service(config)
Hello Group,
We have dovecot deployed as solely a Pop3 service that is used by our
applications to pass mail from one application to another internally. We
have roughly 4 applications that connect to the Pop3 service every 2
seconds, to check for new messages and pop them for processing if they are
present. Depending on the site, we have between 1024-2048MB of memory set
for default_vsz_limit.
2018 Nov 07
0
doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such file or directory
Hi,
Build options - --sysconfdir=/etc/dovecot
doveconf -Pn > dovecot-new.conf
doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such
file or directory
I can make a symlink, but first I'd like to know is this a bug or
misconfiguration.
--
Mart
2018 Nov 07
1
doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such file or directory
Hello,
Am 07.11.2018 um 14:04 schrieb Mart Pirita:
> Hi,
>
>
>
> Build options - --sysconfdir=/etc/dovecot
you should use --sysconfdir=/etc
sysconfig is path to sysconfig, not dovecotconfig.
>
> doveconf -Pn > dovecot-new.conf
> doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such
> file or directory
>
> I can make a symlink, but first
2014 Feb 07
1
Dovecot 2.2.10 crash / infinite loop bug
Hello,
I though this bug should be reported, although there is workaround
already made and in use.
Dovecot 2.2.10 crashes into out of memory error when there is defined
system users (userdb+passdb) and own virtual users (userdb+passdb).
Removing either one solves the issue and Dovecot is working as it
should. When memory leak (I replaced pw_init and gr_init with the
version that is found
2006 Oct 10
3
Out of memory errors
Do these errors indicate a memory leak? I see them in the logs a few times per day on each of our servers, running CVS dovecot-20060924...
Oct 8 22:21:30 mail38b dovecot: auth(default): block_alloc(): Out of memory
Oct 8 22:21:30 mail38b dovecot: child 6391 (auth) returned error 83 (Out of memory)
Oct 9 20:05:05 mail38b dovecot: auth(default): pool_system_realloc(): Out of memory
Oct 9
2019 May 15
0
Frequent Out of Memory for service(config)
On 13.5.2019 22.56, Root Kev via dovecot wrote:
> Hello Group,
>
> We have dovecot deployed as solely a Pop3 service that is used by our
> applications to pass mail from one application to another internally.?
> We have roughly 4 applications that connect to the Pop3 service every
> 2 seconds, to check for new messages and pop them for processing if
> they are present.?
2016 Oct 26
2
multiple SSL certificates story
Hi.
Little story :-)
I'm playing with dovecot 2.2.25 and multiple SSL certificates. ~7000 certificates
which are loaded twice, so my dovecot has ~14 000 certificate pairs
(14k key + 14k cert) in config.
14 000 local_name entries. Like these:
local_name imap.example.com {
ssl_cert = </etc/certs/cert1.pem
ssl_key = </etc/certs/cert1.pem
}
local_name pop3.example.com {
ssl_cert =
2008 Jul 17
1
child xxxxx (imap) returned error 83 (Out of memory)
Hi list,
> Jul 17 12:15:10 seamus dovecot: IMAP(someone at somehost.org): block_alloc(): Out of memory
> Jul 17 12:15:10 seamus dovecot: child 26181 (imap) returned error 83 (Out of memory)
I found those two entries in the logs this morning. The system has
ample free memory. What's going on?
--
martin | http://madduck.net/ | http://two.sentenc.es/
"i wish i hadn't slept
2012 Jun 29
1
auth service: out of memory
Hi,
I have some out of memory errors in my logs (file errors.txt attached)
I'm using dovecot 2.0.19, I can see some memory leaks fix in hg after
the 2.0.19 release but they seem related to imap-login service,
I attached my config too, is something wrong there? Should I really
increase the limit based on my settings?
Can these commits fix the reported leak?
2013 Jul 08
2
Crashes with 2.2.4 setup that worked perfectly with 2.2.2 (.2.3 also crashes)
I am not sure how to get the symbols necessary, however the following is
the backtrace (this is Fedora 19 latest everything):
Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of
memory
Jul 8 03:23:02 MX dovecot: auth: Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f97a952f437] ->
/usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f97a952f4fe] ->