Displaying 20 results from an estimated 5000 matches similar to: "index worker 2.3.7 undefined symbol errors"
2019 Jul 21
0
index worker 2.3.7 undefined symbol errors (more info)
Some supplemental information:
This is happening on every email delivered into Dovecot via LMTP. The
curious things are that the message is a) successfully delivered and b)
sieved into the correct directory.
Another observation is that:
mail_deliver_ctx_get_log_var_expand_table
is defined globally in core/src/lib-lda/mail-deliver.c (and used there)
but the ONLY external call in the entire
2019 Jul 22
1
index worker 2.3.7 undefined symbol errors (more info)
On 21 Jul 2019, at 23.14, Dirk Koopman via dovecot <dovecot at dovecot.org> wrote:
>
> Some supplemental information:
>
> This is happening on every email delivered into Dovecot via LMTP. The curious things are that the message is a) successfully delivered and b) sieved into the correct directory.
>
> Another observation is that:
>
>
2019 Jul 22
0
index worker 2.3.7 undefined symbol errors
On 19 Jul 2019, at 13.20, Dirk Koopman via dovecot <dovecot at dovecot.org> wrote:
> But I am left with this:
>
> Jul 19 14:09:52 localhost dovecot: indexer-worker: Error: User <someone> lookup failed: Couldn't load required plugin /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() faile: /usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol:
2015 May 05
4
Failed running extprograms execute via socket - fatal recv(MSG_PEEK) failed disconnected
> > Last two changes should fix this:
>
>
> Not yet -- this may be unrelated(?) but here is what I have
> after installing the newest source package:
>
> Error: Couldn't load required plugin /usr/local/lib/dovecot/lib90_sieve_plugin.so:
> dlopen() failed: /usr/local/lib/dovecot/lib90_sieve_plugin.so: undefined symbol:
> mail_deliver_ctx_get_log_var_expand_table
2018 Dec 19
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Dear list,
We been having some issues where the indexer-worker is crashing. This
happens on production servers which are handling a slight amount of
mail, but is also reproducible by moving messages. Also, users on my
server are complaining about "Trashed" items coming back etc.
Some details:
- Dovecot 2.3.2.1 in alpine:3.8 based Docker container. As part of the
Mailu distribution.
2015 May 03
2
Failed running extprograms execute via socket - fatal recv(MSG_PEEK) failed disconnected
On 4/30/2015 8:50 PM, E.B. wrote:
>> I switched from running my extprograms execute script directly
>> to running with dovecot socket. Log shows only this
>>
>> dovecot: lmtp(test at example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action execute: running program: test
>> dovecot: lmtp(test at example.com): Debug: Namespace : Using permissions from
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)
2015 May 05
1
Failed running extprograms execute via socket - fatal recv(MSG_PEEK) failed disconnected
E.B. schreef op 5-5-2015 om 9:40:
>>>> Last two changes should fix this:
>>>
>>> Not yet -- this may be unrelated(?) but here is what I have
>>> after installing the newest source package:
>>>
>>> Error: Couldn't load required plugin /usr/local/lib/dovecot/lib90_sieve_plugin.so:
>>> dlopen() failed:
2019 Jan 16
2
auth-worker: Error: double free or corruption (fasttop)
Dear list,
since the distri upgrade to glibc 2.28, i can't build working dovecot
binary's.
Older with glibc 2.27 are working. The distri is LFS based.
MariaDB 10.2.18 and 10.3.11 makes no difference. Having this on
different systems.
Messages Log:
Dec 19 17:10:38 test kernel: traps: auth[30189] general protection
ip:7f4b96d6598c sp:7ffef1f31710 error:0 in
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote:
>
>
>On 22.08.2017 13:37, Darac Marjal wrote:
>> Hello all,
>>
>> Hopefully this is something fairly simple.
>>
>> I've been trying to set up the Sieve Antispam system as detailed at
>> https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment,
>> whenever I change mailboxes
2018 Feb 05
1
Bug in dovecot 2.3 virtual plugin
Hi,
did you have time to investigate about 'Panic: file unichar.c' bug ?
Because I have the same problem with a 2.3.0 installation without
virtual plugin.
Thanks,
Marco
On 2018-01-03 16:52, Aki Tuomi wrote:
> This is not a bug in virtual plugin, but in some email which contains invalid unicode sequence somehow. Can you send me a core file? This should not have occured ofc but
2020 Apr 25
4
problem with a public folder
Hello,
I'm trying to set up a public folder called TestFolder. I'm getting this error:
#doveadm acl get -A "Public/TestFolder"
doveadm(username at example.com): Error: Can't open mailbox
Public/TestFolder: Mailbox doesn't exist: Public/TestFolder
Username ID Global Rights
# ls -ld /var/vmail/public
drwx------ 4 vmail vmail 512 Apr 15 23:17 public/
# ls -ld
2018 Jan 03
4
Bug in dovecot 2.3 virtual plugin
Hi there!
I compiled dovecot 2.3 from git. Because there is already a bug in
virtual-plugin, and i hoped, it get fixed... but it doesn't. So this
is the error-message from the log
J?n 03 16:27:08 aldebaran dovecot[26460]:
indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>:
Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion
failed:
2017 Apr 14
2
several misc questions, public folders and sharing, quota, ssl
Hi Aki,
Thanks for your reply. Sorry, hit the reply to and not the reply to all option.
So, even when a folder is a public folder I'm still needing to use the
acl plugin?
The public/TestFolder is showing up, the public/TestFolder1 is not.
Thanks.
Dave.
On 4/14/17, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> Please keep responses on the list. Thank you. =)
>
> Without ACL
2020 Apr 13
5
got a listener on 993
Hello,
Before I get in to my question is ssl on 993 or starttls on 143 better
from a security perspective?
I've noticed that I've got a dovecot listener on port 993, below is my
doveconf -n output I don't have an imaps listener uncommented should I
do so and set it's port to 0? Will that disable the 993 listener?
Thanks.
Dave.
# 2.3.10 (0da0eff44):
2019 Jan 27
1
auth-worker: Error: double free or corruption (fasttop)
Hi,
Sorry fo my late answer. The hole disty are stripped. I must first
rebuild all with debug symbols.
Here comes the complete gdb backtrace:
(gdb) bt full
#0 0x00007f49738486f7 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007f497384a091 in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x00007f497389220f in __libc_message () from
2017 Oct 31
2
dovecot-2.3 (-git) Warning (Was Re: dovecot Digest, Vol 174, Issue 64)
Hi,
On 30/10/2017 7:22 PM, dovecot-request at dovecot.org wrote:
> Message: 6
> Date: Mon, 30 Oct 2017 10:22:42 +0200
> From: Teemu Huovila <teemu.huovila at dovecot.fi>
> To: dovecot at dovecot.org
> Subject: Re: dovecot-2.3 (-git) Warning and Fatal Compile Error
> Message-ID: <7d2c0b5b-019a-067c-c6be-f36571ed9a96 at dovecot.fi>
> Content-Type: text/plain;
2019 Sep 04
2
Different passdb backends for different services
> Am 04.09.2019 um 08:24 schrieb Sami Ketola via dovecot <dovecot at dovecot.org>:
>
>
>
>> On 3 Sep 2019, at 19.08, R.N.S. via dovecot <dovecot at dovecot.org> wrote:
>>
>> I tried this, but I have done something wrong probably.
>>
>> I added this to 20-imap 20-pop 20-managesieve and 20-submission. Always in the protocol sections. I also
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,
2019 Nov 07
2
dovecot ignores users sieve-script
Hi there!
I recognized that dovecot ignores users sieve-script. The global and the
post-sieve-scripts are working, but users sievescript is ignored.
You can see the sieve trace-files last lines
? 65:?? finishing match with result: not matched
? 65: jump if result is true
? 65:?? not jumping
? 65: jumping to line 67
? 67: jumping to line 77
????? ## Finished executing script 'global'
?
?