similar to: indexes with ocfs2

Firstly, 2.2.13 is about 5 years old. So there's that. It would be helpful if you can reproduce this with 2.2.36. Also, you forgot to actually include in your log snippet the panic. So maybe few more lines before the Raw backtrace? Aki On 20.11.2019 10.54, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have "problem" with dovect 2.2.13 from repo debian8 and I don't

Hi, I am trying to update my old mails servers from dovecot 2.1.15 to 2.2.12 (freebsd ports) and upgrade to FreeBSD 10.0-P3. My mail storage are on NFS with index also. On 2.1.15 everything is ok, and in 10-mail.conf I have the good things to be added as wiki tell me (eg http://wiki2.dovecot.org/NFS). BUT, when I try a single connection like : $ telnet ::1 110 Trying ::1... Connected to

Hello, First, thanks for this great piece of software. I'm new to dovecot and i've just converted my old courier configuration on pop/imap server side, everithing is working just fine on this side and speed gain expected was found (not enough for our busy servers :). Setup is done with 3 dovecot virtual servers load balanced with a Hardware load balancer (this part is a big point of the

This is likely fixed in more recent version, can you try with 2.2.36? Aki On 20.11.2019 11.20, Maciej Milaszewski IQ PL wrote: > Hi > Thanx for replay. > > Log: > > http://paste.debian.net/1117077/ > > > On 20.11.2019 10:07, Aki Tuomi wrote: >> Firstly, 2.2.13 is about 5 years old. So there's that. It would be >> helpful if you can reproduce this with

Hi, I need to place a maildir storage on a NFS filesystem, so I set up the config like this: mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always lock_method = dotlock (also tried fcntl - local lockd is running, no success, now using dotlock, to be sure while debugging) The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in mail-index.c is the same) logs

Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs ->

Hi Thanx for replay. Log: http://paste.debian.net/1117077/ On 20.11.2019 10:07, Aki Tuomi wrote: > Firstly, 2.2.13 is about 5 years old. So there's that. It would be > helpful if you can reproduce this with 2.2.36. > > Also, you forgot to actually include in your log snippet the panic. So > maybe few more lines before the Raw backtrace? > > Aki > > On 20.11.2019

Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. Whale, CEH CHS CISA CISSP: > I have two servers pointing to an NFS mounted mail spool with > dovecot. Since I recently switched from using Dovecot v1.X, I > have been experiencing high CPU use with the two Dovecot > servers. > I am not certain why they are not well behaved. Here is the >

Hello, I'm deploing a new email cluster using Dovecot over GFS2. Actually I'm using courier over GFS. Actually I'm testing Dovecot with these parameters: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes lock_method = fcntl Are they correct? RedHat GFS support mmap, so is it better to enable it or leave it disabled? The documentation suggest the

Hi all, ok, so I've implemented an after sieve script with the following line in the plugins area : sieve_after = /home/mailboxes/sieve/to_spam_folder.sieve It seems to work ok on some accounts, but then I'm getting the following error in the deliver error log for many accounts : Error: sieve: script /home/mailboxes/sieve/to_spam_folder.sieve failed with unsuccessful implicit keep

I have two servers pointing to an NFS mounted mail spool with dovecot.? Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why they are not well behaved.? Here is the configuration information. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15:

Am Dienstag, den 18.12.2018, 14:26 -0500 schrieb Albert E. Whale, CEH CHS CISA CISSP: > I have, but I will be happy to review it once again. > > > On 12/18/18 2:14 PM, admin wrote: > > > > > > > Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. > > Whale, CEH CHS CISA CISSP: > > > >

Are you connecting to the same mailbox over NFS from multiple IMAP servers? If not and, at any given time, any mailbox will be accessed from a single NFS client, try to "dupe" Dovecot into thinking it's not using NFS. We're running quite successfully such setup with NFSv3 over TCP, which turned out to be the fastest and most reliable throughout the years. Here are the mount

dont play net cop here but since you want to try force your opinion down others throats heres one for you, if you want to try dictate to someone to bottom post to suite you how about you use proper net etiquette yourself and TRIM your posts On 12/19/18, admin <admin at awib.it> wrote: > Am Dienstag, den 18.12.2018, 14:26 -0500 schrieb Albert E. Whale, CEH > CHS CISA CISSP: >>

Hello all, We are facing extremely slow GFS2 issues in Redhat 7 64 bit. Backend is 16 Gbps FC SAN so no issues there. I have scoured the entire (anyways most of the) Internet and arrived at the following settings. mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes mmap_disable = yes lock_method = fcntl Did a systemctl restart dovecot and did not find any major

I have, but I will be happy to review it once again. On 12/18/18 2:14 PM, admin wrote: > Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. Whale, CEH > CHS CISA CISSP: >> >> I have two servers pointing to an NFS mounted mail spool with >> dovecot.? Since I recently switched from using Dovecot v1.X, I have >> been experiencing high CPU use with the two

Yes, multiple imap servers using one shared nfs storage. With the same config on 2.2.13 the public interface traffic was similar to the storage interface, around 100 mbps. After we switch to 2.2.27 the storage interface traffic jumped 10 times while the public interface stayed the same. This make us thinking that something is wrong and each time a user logs in the whole Inbox content is read

HI, I'm pulling my hair out a little trying to get dovecot to save it's index locally rather than in the NFS mount. No matter what I do it seems to save the indices in the Maildir on the NFS. I'm using dovecot 2.0.18 on CentOS 6.3. The relevant config I'm using: mmap_disable = no dotlock_use_excl = no # only needed with NFSv2, NFSv3+ supports O_EXCL and it's faster

Hello, I have issue with dovecot (v. 2.1.13)configuration after implementation dovecot-lda (I used maildrop earlier). Now i have 9 servers with storage by NFS v3. My problem is frequently dovecot-uidlist crashing. 2013-02-13T13:34:02.447969+01:00 k1 dovecot: imap(user at domain.com): Error: Broken file /path_to_mailbox/dovecot-uidlist line 3170: Invalid data: 2013-02-13T13:34:34.527715+01:00

Hello list, we continue our tests using Dovecot on a RHEL 6.1 Cluster Backend with GFS2, also we are using dovecot as a Director for user node persistence, everything was ok until we started stress testing the solution with imaptest, we had many deadlocks, cluster filesystems corruptions and hangs, specially in index filesystem, we have configured the backend as if they were on a NFS like setup