Displaying 20 results from an estimated 6000 matches similar to: "1.2: Inotify instance limit for user exceeded, disabling?"
2009 May 27
2
Inotify instance limit for user exceeded, disabling?
I'm seeing this message in my /var/log/maillog:
May 26 12:35:00 agencymail dovecot: IMAP(info at example.com): Inotify
instance limit for user exceeded, disabling. Increase
/proc/sys/fs/inotify/max_user_instances
I rummaged through google, and found :
http://www.dovecot.org/list/dovecot-cvs/2008-May/011132.html
which says I need to increase /proc/sys/fs/inotify/max_user_instances
(no
2008 Dec 29
3
odd epoll() errors
>From my log:
Dec 29 16:43:58 postamt dovecot: Dovecot v1.1.7 starting up
Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files
Dec 29 16:43:59 postamt dovecot: Temporary failure in creating login processes, slowing down for now
Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files
Dec 29 16:43:59 postamt dovecot: Fatal:
2008 May 05
1
Inotify instance limit for user exceeded, disabling.
Hi.
What does the warning "Inotify instance limit for user exceeded,
disabling." mean, and how do I get rid of it? I assume that I have to
change a limit somewhere?
Regards,
Anders.
2020 Mar 31
3
limit for user exceeded
Hi
System debian 8.11 dovecot-2.2.36.4 and I have some warnings in log likes:
Warning: Inotify watch limit for user exceeded, disabling. Increase
/proc/sys/fs/inotify/max_user_watches
cat /proc/sys/fs/inotify/max_user_watches
8192
in sysctl i change
#fs.inotify.max_user_watches= 8192
#fs.inotify.max_user_instances = 16384
fs.inotify.max_user_watches= 16384
fs.inotify.max_user_instances =
2008 Feb 25
2
Update from 1.0.10 -> 1.1rc1: Odd "quota exceeded" output
>From my log:
Feb 25 14:53:26 postamt postfix/local[22546]: 0EAA8220697: to=<username at postamt.charite.de>, relay=local, delay=0.61,
delays=0.16/0.04/0/0.42, dsn=5.7.0, status=bounced (permission denied. Command output: Warning: Growing pool 'Environment' with: 4096 Quota exceeded )
I'm not sure if "Warning: Growing pool 'Environment' with: 4096"
should
2013 Mar 07
1
Inotify max_user_instances
Maybe I have multiple problems - dunno.
I've started seeing the following log lines:
Mar 7 07:46:22 bubba dovecot: imap(dmiller at amfes.com): Warning: Inotify
instance limit for user 5000 (UID vmail) exceeded, disabling. Increase
/proc/sys/fs/inotify/max_user_instances
max_user_instances is currently 128.
I've tried stopping and restarting dovecot - the message immediately
returns.
2010 Jan 18
1
Inotify instance limit for user exceeded
Hello,
i saw in my log followed messages:
dovecot: 2010-01-18 13:20:54 Warning: IMAP(user1 at domain1.com): Inotify
instance limit for user exceeded, disabling.
dovecot: 2010-01-18 13:21:01 Warning: IMAP(user2 at domain2.com): Inotify
instance limit for user exceeded, disabling.
dovecot: 2010-01-18 13:21:23 Warning: IMAP(user2 at domain2.com: Inotify
instance limit for user exceeded, disabling.
2012 Sep 24
1
Logging question regarding delete actions
A user is logged in via imap from multiple devices.
The log has this:
Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15347, msgid=<1341851741.4ffb085d2e2b7 at swift.generated>, size=15675
Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15739, msgid=<b23b2e42f6ae9ba1602690be42b7b5c7.squirrel at webmail.charite.de>, size=18134
Sep 21
2012 Mar 02
2
2.1: Error: Maildir filename has wrong S value, renamed the file from
Hi!
Starting with 2.1.1 we suddely encounter quite a lot of these messages:
Mar 2 11:09:28 postamt dovecot: imap(username): Error: Maildir filename has wrong S value, renamed the file from /home/a/i/username/Maildir/.A*Teens.Eink&AOQ-ufe, Spenden etc/cur/1323207735.M64829P19819.postamt.charite.de,S=5137:2,S to /home/a/i/username/Maildir/.A*Teens.Eink&AOQ-ufe, Spenden
2014 Jan 06
2
inotify max_user instances
Hello,
Timo, last year when you remoted into our server and performed the
migration from courier-imap, we ran into this issue, and you solved it
by doing:
echo 1024 > /proc/sys/fs/inotify/max_user_instances
Then you said you were going to solve this permanently by changing the
init script...
Here is what you said (this is from the skype chat):
[2012-06-04 10:40:43 AM] timosirainen:
2010 Oct 05
4
2.0.5: deliver crashing
>From my log:
Oct 6 00:10:36 postamt kernel: [2353838.557216] deliver[2799]: segfault at 48 ip b77dd649 sp bfcf3b48 error 6 in libdovecot-storage.so.0.0.0[b778e000+b8000]
Oct 6 00:14:39 postamt kernel: [2354082.014722] deliver[6399]: segfault at 48 ip b7779649 sp bf9ca028 error 6 in libdovecot-storage.so.0.0.0[b772a000+b8000]
Oct 6 00:28:12 postamt kernel: [2354894.551201] deliver[13972]:
2009 Jul 07
2
Wrong credential caching
A user logged in with a captial "L" for his username:
Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss
Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): lookup
Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): unknown user
Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss
Jul
2010 Oct 08
2
2.0.5 masteruser problem with uncached users
a "masteruser" login fails:
Oct 8 15:12:54 postamt dovecot: auth: Debug: auth(masteruser,141.42.206.38,master): Master user lookup for login: nonworkinguser
Oct 8 15:12:54 postamt dovecot: auth: passdb(masteruser,141.42.206.38,master): Master user logging in as nonworkinguser
Oct 8 15:12:54 postamt dovecot: auth: Debug: cache(nonworkinguser,141.42.206.38): expired
Oct 8 15:12:54
2011 Jul 21
1
BUG: Unknown internal error
With a recent checkout of dovecot-2 I'm getting a few "BUG: Unknown
internal error" messages.
The log for one such incident:
Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): copy from INBOX: box=INBOX.Trash, uid=6385, msgid=<4DA3E334.000005.02956 at ILONA-PC>, size=90980
Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): copy from INBOX: box=INBOX.Trash, uid=6386,
2007 Oct 02
2
Strange errors
One of our users seems to have strange problems with his mailbox:
Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096, but next_uid = 1097
Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096,
2012 Feb 27
1
Error with 2.0.18
Today I found this in my log:
Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: mmap(/home/t/s/tscxxxf/Maildir/dovecot.index.search.uids) failed: Cannot allocate memory
Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: Corrupted squat uidlist file /home/t/s/tscxxxf/Maildir/dovecot.index.search.uids: uidlist not found
Feb 26 14:27:52 postamt dovecot: imap(tscxxxf): Panic: file
2011 Mar 31
1
Increase /proc/sys/fs/inotify/max_user_instances
Hi
I allready have set 256 on max_user_instances , and in the log i keep
seeing
Mar 28 10:08:44 mail dovecot: imap(some.username): Warning: Inotify
instance limit for user 98 (UID vmail) exceeded, disabling. Increase
/proc/sys/fs/inotify/max_user_instances
All users use thunderbird 3.1.9 , and from time to time this show in log
, with a random user.
What can i do to resolve this issue ?
my
2012 Mar 15
1
2.1: timeout waiting for lock?
Mar 15 09:46:11 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock
Mar 15 09:46:11 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0
Mar 15 09:47:26 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock
Mar 15 09:47:26 postamt dovecot: pop3(username): Couldn't open
2013 Aug 09
2
Error: Threading lost Message ID?
QUERY: THREAD REFERENCES ISO-8859-1 ALL
RESPONSE: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-08-09 15:42:34]
Aug 9 15:41:48 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID
Aug 9 15:42:34 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID
What does that mean? WHY has the Message-Id
2012 Feb 28
1
quota warning script not working after upgrade to 2.1.1
With 2.0.18 I was using a quota warning script like this:
plugin {
...
# Quota
quota = maildir
quota_rule = INBOX.Trash:storage=+2048M
quota_warning = storage=99%% quota-warning 99 %u
quota_warning2 = storage=95%% quota-warning 95 %u
quota_warning3 = storage=90%% quota-warning 90 %u
quota_warning4 = storage=85%% quota-warning 85 %u
}
# der schickt die Quota warnmails
service