similar to: double write-locking dovecot.index.log

Displaying 20 results from an estimated 100 matches similar to: "double write-locking dovecot.index.log"

2009 Jan 13
2
deliver: command died with signal 6
We recently upgraded to dovecot v1.0.15 (from v1.0.0 + some local fixes), and after this upgrade we've started to get a couple of failures from deliver: Jan 12 20:34:34 smtp1.ulh.mydomain.net deliver(someuser at somedomain.net): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45577c] -> /usr/local/dovecot/libexec/dovecot/deliver [0x45537c] ->
2010 Oct 10
1
Dovecot 2.0 lock upgrade assertion failure
Hi! I've now seen this assertion failure from lmtp (most frequent), pop3 (next frequent), and imap (rarely). It didn't start happening until the number of accounts on the server was increased into the 10k-25k range. It happens when index->file_lock is a read lock and mail_index_lock is called asking for a write lock. Dovecot 2.x dies at the assertion on line 62 of mail-index-lock.c
2013 Nov 20
0
Dovecot 2.2.5: Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos)
Hello, I have been seeing an issue with Dovecot 2.2.5 (which is the current version packaged by cPanel). This is happening with any action that tries to access the mailbox index via IMAP. This log and debug information comes from a force-resync attempt, however, the same errors are logged when the user tries to open the mailbox or move a message to it. (User, domain, and IPs in log have been
2007 Dec 05
2
exim/kmail vs. dovecot
I am using exim via dovecot_deliver to store messages in Maildir in my $HOME. I am using kmail to retrieve stuff. Unfortunately, something in my data crashes dovecot. I was using 1.0.rc14 from opensuse, but downloaded and installed 1.0.8 from the site. Here is the crash: Dec 5 18:05:09 h743107 dovecot: IMAP(kris): file mail-index-transaction.c: line 629 (mail_index_update_flags_range):
2005 Apr 14
2
maildir in NFS
How can I configure the dovecot for working with maildir's through NFS? If I add option "index_mmap_invalidate = yes" (as in doc/nfs.t) then in log I have this message: "Error: Error in configuration file /etc/dovecot.conf line 296: Unknown setting: index_mmap_invalidate" If I try to get the mail without option "index_mmap_invalidate" then I have in log this
2010 Apr 02
1
Dovecot Migration so far
We've been doing our own beta testing of Dovecot 2.0-beta4 IMAP (both direct IMAP and webmail-fronted), and we've had nothing but glowing compliments from our beta users/victims. I've also been running a lone box with the latest mercurial build and that's been running just fine too. All mail data is on NFS, but I've put indexes on the local disk, which has worked just dandy so
2008 May 07
1
Bug [1.1rc5]: Crash during "CPU architecture changed" index upgrade
Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file
2010 Apr 03
1
dovecot 2 beta4 errors & core dumps
Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:
2007 Oct 30
1
Errors in Dovecot 1.0.5
Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841
2010 Oct 10
3
Segfault in dovecot-lda 2.0.5
Hi, I've recently started using dovecot-lda to handle my local maildir deliveries from Exim. Unfortunately I've been experiencing the occasional failed delivery - My Exim logs were showing: Child process of virtual_dovecot_delivery transport (running command "/usr/local/libexec/dovecot/dovecot-lda -d $local_part@$domain -f $sender_address -a
2008 Oct 04
2
Dovecot 1.1.3 crash & backtrace
Backtrace:/usr/local/libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB
2018 Dec 04
0
[2.3.4] Segmentation faults
> On 04 December 2018 at 16:46 Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > > Hi > > How to solve this ? > > So many similar segfaults > > Thank you > > On 2018-11-30 06:11, Joan Moreau wrote: > > > ANother (very very long) example : > > > > # gdb /usr/libexec/dovecot/indexer-worker
2008 Aug 01
4
1.1.2: imap crash with SIGSEGV
GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as
2018 Dec 04
0
[2.3.4] Segmentation faults
We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. Aki > On 04 December 2018 at 17:16 Joan Moreau <jom at grosjo.net> wrote: > > > Thanks for mySql > > For Squat vs Solr, Solr does not reach Squat by very far in terms of > results : If I setup Solr, and search (via the search in Roundbube
2018 Dec 04
0
Squat
Yes, but the bottom line is that Squat does the job needed for end users, Solr does not On 2018-12-04 16:53, Michael Slusarz wrote: >> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> >> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. > > FWIW, Squat
2008 Nov 24
2
Indexes recovery failed
Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser at maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot:
2015 Mar 10
0
Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
Hi Stephan, I'm running the current stable version (Dovecot 2.2.15 and Pigeonhole 0.4.6), all works fine except an issue. In my configuration I have this default sieve script (I'm using Maildir): === require ["vnd.dovecot.duplicate", "fileinto", "mailbox"]; if header :matches "X-Spam-Status" "Yes, *" { fileinto
2008 Aug 23
0
imap crash with signal 6 (backtrace), dovecot 1.1.2
GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as
2018 Dec 04
2
[2.3.4] Segmentation faults
> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise. https://wiki.dovecot.org/Plugins/FTS > Aki > > > On 04 December
2007 Jun 12
1
SEGV when user over filesystem quota and "Move to Trash"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded,