similar to: Fwd: Some mails do not get replicated anymore after memory-exhaust

I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] ->

Where would I find the core file? I'm not finding anything obvious. The replicator path is /usr/local/libexec/dovecot/replicator Daniel On 3/22/2017 12:52 AM, Aki Tuomi wrote: > Can you provide us gdb bt full dump? > > gdb /usr/libexec/dovecot/replicator /path/to/core > > on some systems, it's /usr/lib/dovecot/replicator > > Aki > > On 21.03.2017 23:48,

Le mar. 5 mars 2019 ? 10:08, Gerald Galster via dovecot <dovecot at dovecot.org> a ?crit : > > you could try to stop replication for the user you are deleting: > doveadm replicator remove [-a replicator_socket_path] username > > Good idea! But I have a problem. I tried to stop the replication (doveadm replicator remove <myuser>) for an user on both server. Verified with

So nobody has any idea why this could happen? Let me know if I should provide more Information Thanks Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis at gdv-dl.de<mailto:Thomas.Tsiakalakis at gdv-dl.de> GDV Dienstleistungs-GmbH Glockengie?erwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de>

On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda <gerben.wierda at rna.nl> wrote: >One step further in my quest to create a replacement mail server. > >I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: > >Jan 06 00:50:31 replicator: Panic: data

I posted a few days back asking about configuration issues with a modestly large number of IMAP connections. Several people were kind enough to respond with various ideas. Armed with those ideas and Google, I was able to determine the underlying configuration issues with CentOS 7 and Dovecot 2.2.10. I did some further benchmarking to ensure that we could properly plan our server

An embedded and charset-unspecified text was scrubbed... Name: dovecot.txt URL: <http://dovecot.org/pipermail/dovecot/attachments/20140512/f984dc96/attachment.txt>

> I don't know if it makes a difference, I don't have quotes on my > mail_plugins: I don't have quotes too (It's difference between config file and dovecot -n output) > Did you check permissons on the replication fifos? For what? I think that problems on slave. How it should work in automatic mode? I repeat that from slave manually all works fine: >> As I

Dear all, I am using VMWare and I have cloned my emails server. Now I do have two identicals servers, both running the same version of dovecot (2.2.13) and imap. Let's call them: server1.domain.ltd and server2.domain.ltd. I would like to sync both server using dsync. Dovecot is working well except concerning the sync. dsync config server1.domain.ltd # Enable the replication plugin

In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't finished yet, but it appears to work and I've enabled it for my @dovecot.fi mails. Some issues: - public namespace isn't replicated at all - shared namespace is replicated, but not private mail flags - I've only tested SSH replication setup now, not director replication setup (and director setup

Hi Mike, Is the value of the 'doveadm_port' if I am choosing: mail_replica = tcp:server1.domain.ltd no ? I might be wrong too ;) Thx Le mardi 24 janvier 2017 ? 11:41:28, vous ?criviez : > Hello, > I might be wrong, but the port which will be used for the replicator > port is the value of 'doveadm_port' which in your case is 4711. > Mike; > On 01/23/2017

Very minor bug; not specifying the user mask with 'doveadm replicator replicate -f' causes a segfault: server:~# doveadm replicator replicate -f Segmentation fault server:~# doveadm replicator replicate -f '*' 123 users updated server:~# gdb /usr/bin/doveadm core.2418 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7 This GDB was configured as

Hello Aki, Thank you for getting back. I tried your suggestion, but nope... I also checked the perms on dirss/files to be vmail rw(x)------ ; yet does not changed the beahaviour :( On 05/26/2017 12:29 PM, Aki Tuomi wrote: > You probably want to set subscriptions=no, so they will be done in the > parent namespace instead. > > Aki > > > On 26.05.2017 13:22, dovecot at

Hello Gerald, > Besides you have configured mysql userdb twice: > >> userdb { >> args = /etc/dovecot/dovecot-sql-master.conf.ext >> driver = sql >> } >> userdb { >> args = /etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } Great!!! This was the root cause. Second userdb with dovecot-sql-master.conf rewrite the first one, but

Hi list, I'm getting stuck at the replication part for my BDC. Could someone familiar with OpenLDAP replication shed some light? I'm sure that password is correct Thanks for taking a look at! 1. slapd.conf (master) # $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8 2003/05/24 23:19:14 kurt Exp $ # # See slapd.conf(5) for details on configuration options. # # include

Hi folks, Wondering if this is expected behavior; we'd like to be able to pause replication for a particular account on our 2.2.32 active-active cluster, but delivering a message (LMTP) to the account seems to turn replication back on again: (replication on) server1:~# doveadm replicator status rgiles username priority fast sync full sync success sync

One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jan 06 00:50:32 replicator: Fatal: master:

Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the

Hello Community, I am trying to figure out hwo to use the virtual mailboxes, but remain a bit confused: - I see the Virtual speudo-folder - Eventuelly the name of the boxes underneath - But cannot see more, nor subscrie to the virtual mailboxes Dovecot: # 2.2.29.1 (e0b76e3): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: Linux 4.4.50-v7+ armv7l Debian 8.0 ext4

Hello Timo, 2.2rc3: replication unconfigured (no "replica" in doveconf -n output), # doveadm replicator status starts the dovecot/replicator process, which keeps running, leading to "sync: User has no mail_replica in userdb" errors for each user every 5 minutes. Same after "doveadm replicator replicate some-even-nonexisting-user". Lutz