similar to: Possible solr and indexing bug

Hello. I have one account with heavy traffic (big mails) and quite often indexes get corrupted. This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28. When corruption happens lmtp and pop3 segfault on accessing it like: > Mar 27 11:13:50 mbox dovecot[22370]: lmtp(24428): Connect from local

Hi, although i've search the archives, there are questions left regarding backup strategies and errors that occur. I'm using dovecot 2.3.11.3 with mdbox (mailbox size 50MB - 30GB). Every night, i ran the following command: doveadm -o mail_fsync=never -o plugin/quota= -o plugin/zlib_save=gz \ backup -u account mdbox:/nfs/storage/account/mdbox ### incremental backup Thanks to zlib

Hello, We have recently implemented dovecot directors to resolve an ongoing NFS lock/corruption issue. Everything was working great! So we updated our servers from centos 7.3 to 7.7 and dovecot 2.2.10 to 2.3.8 This was a bit of a failure and we were getting spammed with corrupt index files and logs. After we clear the index files with rm rf/mail/d/e/username/Maildir/dovecot*, they just come back

On 27 Mar 2019, at 12.42, Arkadiusz Mi?kiewicz via dovecot <dovecot at dovecot.org> wrote: > > > Hello. > > I have one account with heavy traffic (big mails) and quite often > indexes get corrupted. > > This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28. > > When corruption happens lmtp and pop3 segfault on accessing it like: >

Google tells me that these "should go away" but they don't. Seems to happen continuously while a user is viewing email. Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Archive/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Davies/dovecot.index Mar 7 09:29:52

2017-01-30 11:43 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > Hi! > > Please send these to dovecot at dovecot.org instead of us directly. Thank you. Ok, added to cc. > Also, did you try force-resync? Not help. # doveadm force-resync -u altek at altek.info \* doveadm(altek at altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index

Hi all, We have recently had some power failures have led to corrupt mdbox instances. Dovecot?s fsck appears to get caught in a loop when the recipient has a large amount of mail. In the example log output below, each ?rebuilding indexes? seems to be interrupted by a new IMAP connection. Later, when our folks realized the issue and blocked access to the mailbox, the index rebuild finished in

Hello. I have been on leave for several weeks and have managed to lose all emails received since December due to a server crash. I asked about log synch error back in March and have (repeatedly) deleted all .imap files but the errors continue. # 2.1.1: /usr/etc/dovecot/dovecot.conf # OS: Linux 2.6.33.5-desktop-2mnb i686 Mandriva Linux 2010.2 mail_access_groups = mail mail_location =

Hi, I am seeing constant "Log synchronization error"s in my logs. See later for an example. This is dovecot 2.2.4, pigeonhole 0.4.1, and postfix 2.10.1 (with mailbox_command = /usr/libexec/dovecot/deliver) on a Fedora 19 system. I am using packages from Atrpms so there are some patches applied - ask for details. The mailboxes have resently been moved from a i386 system. I have

Hi there! I get a lot of errormessages. My dovecot is: dovecot-core 2:2.3.2.1-1~stretch from Debian stable. I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html So the bug came back... The Log is attached Thanks Jakob -------------- next part -------------- Sep 11 19:18:37 mymail dovecot[29916]:

Hi there! I get a lot of errormessages. My dovecot is: dovecot-core 2:2.3.2.1-1~stretch from Debian stable. I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html So the bug came back... The Log is attached Thanks Jakob -------------- next part -------------- Sep 11 19:18:37 mymail dovecot[29916]:

After a (power)crash two accounts have been corrupted. I tried to rescue things by running force-resync multiple times, but that didn't work out. Searching the archives, I found a recent suggestion (by Timo) to delete the index files, but I'm not sure which files to delete and what the consequences will be. When I deleted ``storage/dovecot.map.index'' in an unimportant account

Hi! When I force-resync a mailbox of mine, I see following output: # doveadm force-resync -u $USER $PATH doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y2 != $X,$Y2) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: rebuilding indexes doveadm($USER): Error: mdbox .../storage: Duplicate GUID $G in

Two nights ago I took a leap and extended my testing of dovecot 1.1 by replacing 1.0 for the approx 15 users I had on 1.0. At that time I also for the first time tried dovecot 1.1 in a load balanced 2 server configuration with indexes on NFS. I was hoping I did this right, using the mail_nfs params and 1.1 so fchown etc would flush the access cache, but I am getting a number of messages and

Hello, today i got reappearing mails again, but not from purging. In the logs i only found this. I've got massive problems by many users because reappearing mails. If you need more information, i could provide. Sep 02 12:58:43 doveadm: Warning: Transaction log file /var/spool/mail/<user>/storage/dovecot.map.index.log was locked for 43 second s (mdbox storage rebuild) Sep 02 12:58:43

I have recently updated with 2.2.29.1-avh1~xenial1 ubuntu package on 16.04. It appears that I have a couple of duplicate GUIDs which fsck can't clear so the machine is looping through doing continuous fsck runs. Any way to determine what the offending messages are and how to delete or otherwise stop this? Jul 1 17:09:24 post dovecot: doveadm(djk at tobit.co.uk): Warning: fscking index

Any idea what?pid 7584 is? Aki On 2.9.2019 14.08, telsch via dovecot wrote: > Hello, > > today i got reappearing mails again, but not from purging. In the logs i > only found this. I've got massive problems by many users because > reappearing mails. If you need more information, i could provide. > > > Sep 02 12:58:43 doveadm: Warning: Transaction log file >

On 18.09.2017 12:20, Ralf Becker wrote: > Hi Aki, > > Am 18.09.17 um 11:13 schrieb Aki Tuomi: >> On 18.09.2017 12:10, Ralf Becker wrote: >>> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >>>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>>>

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

We have often found the below error in VPS servers using OpenVZ, and some cases using OpenStack, in neither case is used for storage or sharing ISCSI or NFS Client can not receive messages via POP3 or IMAP In /var/log/maillog the message below is seen Oct 31 15:28:26 vps dovecot: pop3(user at domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07400] ->