similar to: replicator crashing - oom

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,

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, Daniel Miller wrote: > 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:

sysctl kernel.core_pattern usually indicates where cores are placed. If it says 'core' you are probably not gonna find it. Aki On 22.03.2017 18:11, Daniel Miller wrote: > 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:

Think I got it: #0 0x00007fddaf597c37 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fddaf59b028 in __GI_abort () at abort.c:89 #2 0x00007fddaf9c0c86 in default_fatal_finish (type=<optimized out>, status=status at entry=0) at failures.c:201 #3 0x00007fddaf9c0d6e in i_internal_fatal_handler (ctx=0x7fff7197d000, format=<optimized out>,

Sorry for the re-post - just want to make sure you saw this: #0 0x00007fddaf597c37 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fddaf59b028 in __GI_abort () at abort.c:89 #2 0x00007fddaf9c0c86 in default_fatal_finish (type=<optimized out>, status=status at entry=0) at failures.c:201 #3 0x00007fddaf9c0d6e in i_internal_fatal_handler

For my primary namespace this is working fine - thanks to the developers! It also appears to work great for shared folders as well. But my virtual folders aren't returning results - at least not to the client. The logs show FTS Xapian opening several DB files and getting results - but nothing is being returned to client. Is this a config issue on my side or is this a current limitation of

Logs: Jun 5 06:02:25 bubba dovecot: imap(dmiller at amfes.com)<25877><IjkkJZOKPvKsOk9d>: Opening DB (RO) /var/mail/amfes.com/dmiller/sdbox/xapian-indexes/db_f2857830c70c844e2f1d00003bc41c5f Jun 5 06:02:25 bubba dovecot: imap(dmiller at amfes.com)<25877><IjkkJZOKPvKsOk9d>: FTS Xapian: FLAG=AND Jun 5 06:02:25 bubba dovecot: imap(dmiller at

Yes, latest git version. The logs show (as I read them) returned results - yet nothing shows in the client. The logs look the same (with different numbers) when querying "regular" folders - but results are shown in clients. -- Daniel On June 6, 2019 12:16:08 AM Joan Moreau <jom at grosjo.net> wrote: > Hi > Are you using the latest git version ? > WHich part exactly

All, I am running samba as an AD on a Debian buster: *ii python-samba 2:4.9.5+dfsg-5+deb10u1 armel Python bindings for Sambaii samba 2:4.9.5+dfsg-5+deb10u1 armel SMB/CIFS file, print, and login server for Unixii samba-common 2:4.9.5+dfsg-5+deb10u1 all common files used by both the Samba server and clientii

I've completed my mailbox rebuild - theoretically I should be free of corruption. I used dsync to export from mdbox to maildir (so should be clean) then used a virtual machine with Dovecot to import back to mdbox in another location. So...theoretically I should be free of all corruption now... Running an fts update - "doveadm search text -u user at domain.com xyzzyx" works on

On 2017-06-23 15:09, Marcus Rueckert wrote: > On Fri, 23 Jun 2017 11:38:28 -0700 > Daniel Miller <dmiller at amfes.com> wrote: > >> While auditing my logs after an account was compromised, I see a >> number of entries like: >> >> Jun 23 11:32:18 bubba dovecot: auth: >> ldap("one-of-my-accounts",127.0.0.1): invalid credentials > >

Attempting to delete a folder from within the trash folder using Thunderbird. I see the following in the log: Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Error: Raw backtrace:

I hate asking questions on mailing lists, but I've exhausted my googling and FAQ trawling skills. If I've missed the pertinent doc, please tell me where to RTFM. Environment: I'm running postfix 2.3.2 on a Solaris 10 server. Mail goes into standard mbox format in /var/mail. Users can access their mail via shell (pine, mutt), POP3 or IMAP, and the pop3/imap server is

Continuing to see errors on this with some new messages. Is it possible this has anything to do with zlib plugin, or possibly having a mix of zlib compressed & uncompressed messages with mdbox? I recently added zlib to deliver plugin list. -- Daniel L. Miller, VP - Engineering, SET AM Fire & Electronic Services, Inc. [AMFES] dmiller at amfes.com 702-312-5276

doveadm search -u dmiller at amfes.com text xyzxyz doveadm(dmiller at amfes.com): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset <= lstream->v_size) doveadm(dmiller at amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3ca8a) [0x7fcf3daaca8a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)

When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour? -- Daniel

I thought I had cleared out the corruption I had before - perhaps I was mistaken. What steps should I take to help locate these issues? Currently using 2.1rc1. I see the following errors in my logs, including out of memory and message size issues (at 15:30): Jan 4 05:17:17 bubba dovecot: indexer-worker(user1 at domain.com): Error: Raw backtrace:

Came across this in the logs... Nov 3 16:08:00 bubba dovecot: imap(dmiller at amfes.com): Error: Attachment file /var/mail/attachments/dc/73/dc7398c85dd02efe8a14fe6cc019b2cf07eec600-d5ca962aaae7d14c587400003bc41c5f size mismatch: 122626 != 165655 There's about a dozen different file entries listed in the error log. I'm using 2.0.6, mdbox, and the mails are stored on a local XFS

I just tried switching to lmtp from lda. Messages are being delivered, but I now see messages similar to: Jul 26 22:59:21 bubba dovecot: lmtp(20508): Disconnect from local: Client quit (in reset) in my log for every message. Is this a normal sign-off - or does this indicate a misconfiguration? -- Daniel

While auditing my logs after an account was compromised, I see a number of entries like: Jun 23 11:32:18 bubba dovecot: auth: ldap("one-of-my-accounts",127.0.0.1): invalid credentials I'm trying to figure out where this login attempt is coming from. I do run ASSP (an SMTP proxy) on this server, as well as Postfix - but I wouldn't think there'd be any communication with