Displaying 20 results from an estimated 30000 matches similar to: "Errors with count:User quota and NFS"
2016 Nov 01
1
Errors with count:User quota and NFS
On 2016-10-31 22:04, Timo Sirainen wrote:
>> Oct 31 10:52:37 imap(xxx at xxxx.xx): Warning: Locking transaction log
>> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31
>> seconds (syncing)
>> Oct 31 10:52:37 imap(xxx at xxx.xx): Warning: Locking transaction log
>> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31
>> seconds
2016 Mar 19
3
Crash when setting quota = count:User quota
Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Panic: file file-lock.c: line 269:
unreached
Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0 [0x35f647e07a] ->
/usr/lib/dovecot/libdovecot.so.0 [0x35f647e0e6] ->
/usr/lib/dovecot/libdovecot.so.0 [0x35f647d4ac] ->
/usr/lib/dovecot/libdovecot.so.0 [0x35f6481edf] ->
2017 Jan 18
2
Quota count does not work with lock_method=dotlock
Hello,
dovecot crashes when I switch the quota tracking from dict to count. The
following is working since years:
quota = dict:User quota::proxy::quota
I'm using a mysql quota dictionary.
Now I want to switch to the new "quota count" + "quota clone"
combination. I'm loading the "quota_clone" plugin, and:
#quota = dict:User quota::proxy::quota
2016 Oct 31
0
Errors with count:User quota and NFS
On 31 Oct 2016, at 12:01, Tom Sommer <mail at tomsommer.dk> wrote:
>
> I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors:
>
> Oct 31 10:52:13 imap(xxxx at xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted
> Oct 31
2017 Jan 24
1
Quota count does not work with lock_method=dotlock
On 24.01.2017 11:31, Tom Sommer wrote:
> On 2017-01-24 10:25, Aki Tuomi wrote:
>> On 24.01.2017 11:13, Tom Sommer wrote:
>>> On 2017-01-18 15:27, mkliewe at gmx.de wrote:
>>>
>>>> dovecot crashes when I switch the quota tracking from dict to count.
>>>
>>> I have the same problem, but I use 'dict:file' as quota backend -
>>>
2010 May 12
1
Problems with the fs-quota plugin on delivery stage
Hi All!
Just noticed a strange behavior of the FS quota plugin on delivery stage.
We use group FS quotas via NFS. And quota-tool says:
---
Disk quotas for group #5751796 (gid 5751796):
Filesystem blocks quota limit grace
nfse:/export 1276 10240 10240
---
I run:
---
cat ./test.eml | /usr/local/libexec/dovecot/deliver -e -n -d xxxx at xxxxx.xxxx
---
and get:
---
Quota
2017 Jan 24
2
Quota count does not work with lock_method=dotlock
On 24.01.2017 11:13, Tom Sommer wrote:
> On 2017-01-18 15:27, mkliewe at gmx.de wrote:
>
>> dovecot crashes when I switch the quota tracking from dict to count.
>
> I have the same problem, but I use 'dict:file' as quota backend -
> Maybe the error is due to quota_vsizes and not 'count'.
>
> // Tom Sommer
Hi!
What version of dovecot are you both using?
2016 Apr 07
2
Opportunistic quota recalc
On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote:
>
> On 2016-04-06 21:09, Tom Sommer wrote:
>> On 2016-04-06 20:38, Timo Sirainen wrote:
>>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote:
>>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset.
>>>> I get that
2009 Nov 13
2
Index file (date timestamp) issue on OS X 10.6.2 Server
Hi,
I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious!
I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.
2016 Mar 15
5
lmtp timeout, locks and crashes
I'm seeing some problems on accounts which get a lot of spam (like, a
lot).
I get these errors:
Mar 15 10:43:49 lmtp(12390): Error: Timeout (29s) while waiting for lock
for transaction log file
/var/spool/mail/dovecot/xxxx/xxxx/dovecot.list.index.log (WRITE lock
held by pid 12193)
---
Mar 15 10:43:49 lmtp(12034): Error: Transaction log file
2016 Mar 17
2
lmtp timeout, locks and crashes
On 2016-03-17 13:41, Tom Sommer wrote:
> On 2016-03-15 10:53, Tom Sommer wrote:
>> I'm seeing some problems on accounts which get a lot of spam (like, a
>> lot).
>
> I did an "strace" on one of the hundreds of lmtp processes.
>
> It's doing stat() on all files in the new folder for the receiver:
>
>
2016 Apr 06
2
Internal quota calculation error (redis), double mail delivery
Sometimes my redis connection times out, both for pop3, imap and lmtp. I
have no idea why, when I do a "doveadm quota recalc -u" it works just
fine?
I'm thinking the connection is lost somehow and not retried?
Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: redis: Lookup timed out in
30.000 secs
Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: Internal quota calculation
error
Apr 06
2016 Apr 06
2
Internal quota calculation error (redis), double mail delivery
On 2016-04-06 20:27, Timo Sirainen wrote:
> On 06 Apr 2016, at 16:54, Tom Sommer <mail at tomsommer.dk> wrote:
>>
>> Sometimes my redis connection times out, both for pop3, imap and lmtp.
>> I have no idea why, when I do a "doveadm quota recalc -u" it works
>> just fine?
>> I'm thinking the connection is lost somehow and not retried?
>>
2007 Jun 22
2
FreeBSD NFS file locking mechanism
Hi all,
I have some machines running FreeBSD and dovecot deployed. User's home
dir is on NFS mount and I've found that dovecot only works with
dotlock file locking mechanism, fcntl and flock failed. Now it causes
problem with thunderbird (thunderbird is cachine connections) waiting
forever and I noticed that dovecot is trying to acquire a lock but
unsuccessful since the lock file is in
2017 Jan 24
0
Quota count does not work with lock_method=dotlock
On 2017-01-24 10:25, Aki Tuomi wrote:
> On 24.01.2017 11:13, Tom Sommer wrote:
>> On 2017-01-18 15:27, mkliewe at gmx.de wrote:
>>
>>> dovecot crashes when I switch the quota tracking from dict to count.
>>
>> I have the same problem, but I use 'dict:file' as quota backend -
>> Maybe the error is due to quota_vsizes and not 'count'.
2008 Feb 26
3
nfs locking issues...
I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence
for making things working correctly over nfs. But I run into locking
issues if I run over nfs.
procmail is doing the delivery over nfs. uw-imap was ruining over nfs.
dovecot is fine if its on the nfs server (i.e. it has local access to
the disk, no nfs)
I run into lock deadlocks if I run dovecot over nfs
Users
2008 Apr 04
3
Dovecot and stale nfs-locks hanging processes
Greetings dovecot mailing list.
I have implemented a relatively big dovecot setup (250k users) and
overall I am very pleased with dovecot functionality and performance.
Setup description:
* dovecot 1.0.x
* FreeBSD 6.3
* Postfix (using dovecot deliver as LDA).
* OpenLdap backend
* Storage is NFS (Clariion EMC NFSd for Maildir, and FreeBSD NFSd for
Indexes).
* Locking is fcntl using
2018 Dec 18
2
High Load average on NFS Spool - v.2.1.15 & 2.2.13
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:
2017 Jan 24
0
Quota count does not work with lock_method=dotlock
On 2017-01-18 15:27, mkliewe at gmx.de wrote:
> dovecot crashes when I switch the quota tracking from dict to count.
I have the same problem, but I use 'dict:file' as quota backend - Maybe
the error is due to quota_vsizes and not 'count'.
// Tom Sommer
2006 Jun 13
2
nfs, dovecot, and maildirs
Hello - I know I am not the only one that will be trying, or has tried this
before. Here are my questions!
NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with
relevant patches (utime, etc)
Backend - netapp filer
End users - various clients all running IMAP
It looks like 1.0.beta8 is definately the way to go. I have a few questions
with regards to setup.
Is it now