Re: limit for user exceeded
Hi
I Dont understand or I im thinking wrong:
process_limit = 25000
Older:
#fs.inotify.max_user_watches= 8192
#fs.inotify.max_user_instances = 16384
New:
fs.inotify.max_user_instances = 8192
fs.inotify.max_user_watches= process_limit x 2 + fs.inotify.max_user_instances
fs.inotify.max_user_watches= 58192
On 31.03.2020 13:44, Aki Tuomi wrote:
> I would prefer replies on the list... =)
>
> no. the idea is to *increase* the *current* value of
> fs.inotify.max_user_watches and fs.inotify.max_user_instances with 5
>
> fs.inotify.max_user_watches = 8192 + 5 = 58192
>
> Aki
>
>> On 31/03/2020 14:21 Maciej Milaszewski wrote:
>>
>>
>> Hi
>> How I understood it correctly
>>
>> service imap {
>> process_limit = 25000
>> }
>>
>> fs.inotify.max_user_watches= 5
>> fs.inotify.max_user_instances = 5
>>
>> ?
>>
>>
>> On 31.03.2020 12:14, Aki Tuomi wrote:
>>> Sorry, ment that we *increase* the current value with twice the process
>>> limit for IMAP.
>>>
>>> Aki
>>>
>>>> On 31/03/2020 13:12 Aki Tuomi wrote:
>>>>
>>>>
>>>> We usually set them to twice the number of process_limit for imap.
>>>>
>>>> Aki
>>>>
>>>>> On 31/03/2020 12:29 Maciej Milaszewski wrote:
>>>>>
>>>>>
>>>>> 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 = 24576
>>>>>
>>>>> One questions - should these values be equal?
Re: limit for user exceeded
Sorry, ment that we *increase* the current value with twice the process limit for IMAP. Aki > On 31/03/2020 13:12 Aki Tuomi wrote: > > > We usually set them to twice the number of process_limit for imap. > > Aki > > > On 31/03/2020 12:29 Maciej Milaszewski wrote: > > > > > > 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 = 24576 > > > > One questions - should these values be equal?
Re: limit for user exceeded
We usually set them to twice the number of process_limit for imap. Aki > On 31/03/2020 12:29 Maciej Milaszewski wrote: > > > 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 = 24576 > > One questions - should these values be equal?
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 = 24576 One questions - should these values be equal?
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
Timo Sirainen put forth on 8/11/2010 12:55 PM: But yeah, if you haven't added any limits to how many connections users can create, I guess they could easily use up 128 connections. IIRC, the default limit in 1.2 is 10 connections per IP--which IMO, for 99+% of users, is 8 too many, maybe 9. ;) -- Stan
[Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
From my log: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances # wc -l subscriptions 95 # cat /proc/sys/fs/inotify/max_user_instances 128 Why does 95 exceed 128? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
On Wed, 2010-08-11 at 17:37 +0200, Ralf Hildebrandt wrote: From my log: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances # wc -l subscriptions 95 That's irrelevant. # cat /proc/sys/fs/inotify/max_user_instances 128 Why does 95 exceed 128? You're using virtual users and you have over 128 connections running IDLE command. I suppose I should update that error message a bit.. This is the second time this has been asked me today. Maybe: Inotify instance limit for user vmail (UID 1234) exceeded, disabling.
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
* Timo Sirainen t...@iki.fi: On Wed, 2010-08-11 at 17:37 +0200, Ralf Hildebrandt wrote: From my log: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances # wc -l subscriptions 95 That's irrelevant. Well, I thought it would affect THAT user only. # cat /proc/sys/fs/inotify/max_user_instances 128 Why does 95 exceed 128? You're using virtual users No. and you have over 128 connections running IDLE command. That user is the ONLY user getting this error. He's the one user with the most subfolders. I suppose I should update that error message a bit.. This is the second time this has been asked me today. Maybe: Inotify instance limit for user vmail (UID 1234) exceeded, disabling. No, every user has his/her own UID :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
On Wed, 2010-08-11 at 18:16 +0200, Ralf Hildebrandt wrote: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances and you have over 128 connections running IDLE command. That user is the ONLY user getting this error. He's the one user with the most subfolders. Is it possible that the user has over 128 IMAP connections? :) That's the only reason for this error I can think of.
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
On Wed, 2010-08-11 at 18:08 +0100, Timo Sirainen wrote: On Wed, 2010-08-11 at 18:16 +0200, Ralf Hildebrandt wrote: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances and you have over 128 connections running IDLE command. That user is the ONLY user getting this error. He's the one user with the most subfolders. Is it possible that the user has over 128 IMAP connections? :) That's the only reason for this error I can think of. Oh, I know: You're using virtual mailboxes?
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
* Timo Sirainen t...@iki.fi: That user is the ONLY user getting this error. He's the one user with the most subfolders. Is it possible that the user has over 128 IMAP connections? :) That's the only reason for this error I can think of. Maybe folder * connections? God only knows what my users do! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
* Timo Sirainen t...@iki.fi: On Wed, 2010-08-11 at 18:08 +0100, Timo Sirainen wrote: On Wed, 2010-08-11 at 18:16 +0200, Ralf Hildebrandt wrote: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances and you have over 128 connections running IDLE command. That user is the ONLY user getting this error. He's the one user with the most subfolders. Is it possible that the user has over 128 IMAP connections? :) That's the only reason for this error I can think of. Oh, I know: You're using virtual mailboxes? no :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
On Wed, 2010-08-11 at 19:52 +0200, Ralf Hildebrandt wrote: Is it possible that the user has over 128 IMAP connections? :) That's the only reason for this error I can think of. Oh, I know: You're using virtual mailboxes? no :) Oh. That was a good theory, since I recently changed that code to support IDLEing. Although now that I read the subject, it was only in v2.0 and not v1.2.. But yeah, if you haven't added any limits to how many connections users can create, I guess they could easily use up 128 connections.
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
* Timo Sirainen t...@iki.fi: But yeah, if you haven't added any limits to how many connections users can create, I guess they could easily use up 128 connections. mail_max_userip_connections = 2048 that's because of the webmailer, which, due to imapproxy, uses many simultaneous connections. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 1.2: Inotify instance limit for user exceeded, disabling?
On Wed, 2010-08-11 at 19:59 +0200, Ralf Hildebrandt wrote:
* Timo Sirainen t...@iki.fi:
But yeah, if you haven't added any limits to how many connections users
can create, I guess they could easily use up 128 connections.
mail_max_userip_connections = 2048
that's because of the webmailer, which, due to imapproxy, uses many
simultaneous connections.
With v2.0 you could put that inside remote webmail {} block. I think.
[Dovecot] Inotify instance limit for user exceeded
Hello, i saw in my log followed messages: dovecot: 2010-01-18 13:20:54 Warning: IMAP(us...@domain1.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:01 Warning: IMAP(us...@domain2.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:23 Warning: IMAP(us...@domain2.com: Inotify instance limit for user exceeded, disabling. dovecot -c dovecot-domain1.com.conf -n: # 1.0.10: dovecot-domain1.com.conf remax-czech.cz base_dir: /var/run/domain1.com log_path: /var/log/dovecot/domain1.com/dovecot.log info_log_path: /var/log/dovecot/domain1.com/info.log log_timestamp: %F %T protocols: imap imaps pop3 pop3s listen: 127.0.0.1 ssl_cert_file: /usr/local/ssl/mail/domain1.comserver.crt ssl_key_file: /usr/local/ssl/mail/domain1.com/server.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot-domain1.com/login login_executable(default): /usr/local/dovecot/bin/dovecot/imap-login login_executable(imap): /usr/local/dovecot/bin/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/bin/dovecot/pop3-login login_max_processes_count: 40 login_max_connections: 42 max_mail_processes: 2000 verbose_proctitle: yes first_valid_uid: 507 last_valid_uid: 507 first_valid_gid: 502 last_valid_gid: 502 fsync_disable: yes mail_executable(default): /usr/local/dovecot/bin/dovecot/imap mail_executable(imap): /usr/local/dovecot/bin/dovecot/imap mail_executable(pop3): /usr/local/dovecot/bin/dovecot/pop3 mail_process_size: 300 mail_plugin_dir(default): /usr/local/dovecot-1.0.10/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.0.10/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.0.10/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login user: vmail verbose: yes passdb: driver: vpopmail userdb: driver: vpopmail There is about 2500 users on domain1.com, so i should raise max_mail_processes ? -- Lampa
Re: [Dovecot] Inotify instance limit for user exceeded
On 18/01/2010 14:49, Lampa wrote: Hello, i saw in my log followed messages: dovecot: 2010-01-18 13:20:54 Warning: IMAP(us...@domain1.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:01 Warning: IMAP(us...@domain2.com): Inotify instance limit for user exceeded, disabling. dovecot: 2010-01-18 13:21:23 Warning: IMAP(us...@domain2.com: Inotify instance limit for user exceeded, disabling. Hello, I've solved a similar trouble with: fs.inotify.max_user_instances = 256 in /etc/sysctl.conf The default is 128.
Re: [Dovecot] Inotify instance limit for user exceeded, disabling?
On Wed, 2009-05-27 at 09:21 -0400, dove...@corwyn.net wrote: The error message also implies that something has been disabled. If I increase /proc/sys/fs/inotify/max_user_instances will it fix automatically, or do I need to do something else? since it's a kernel message, I suspect just restarting dovecot won't do it. Kernel increases the limit immediately, so you don't need to do anything else. There's no need to even restart Dovecot (although existing IMAP processes that failed to use inotify before won't be using it until the client reconnects). And what exactly is breaking when I receive this notification? When IMAP client uses IDLE command, Dovecot can't use inotify to notify the client immediately after new message has been received. signature.asc Description: This is a digitally signed message part
[Dovecot] 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(i...@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 surprise given the error message really). I can fix that with echo 256 /proc/sys/fs/inotify/max_user_instances , but as /proc is temporary, so if I change it won't it break if/when the system reboots? The error message also implies that something has been disabled. If I increase /proc/sys/fs/inotify/max_user_instances will it fix automatically, or do I need to do something else? since it's a kernel message, I suspect just restarting dovecot won't do it. And what exactly is breaking when I receive this notification? The proc docs indicate: /proc/sys/fs/inotify (since Linux 2.6.13) This directory contains files max_queued_events, max_user_instances, and max_user_watches, that can be used to limit the amount of kernel memory consumed by the inotify interface. For further details, see http://linux.die.net/man/7/inotifyinotify(7). Is this dovecot monitoring for new mail? thanks Rick [r...@agencymail inotify]# dovecot -n # 1.1.8: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 i686 Red Hat Enterprise Linux Server release 5.2 (Tikanga) ext3 ssl_cert_file: /etc/httpd/certs/agencymail_example_com.crt ssl_key_file: /etc/httpd/certs/agencymail.example.com.key.no.password login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_max_processes_count: 256 mail_uid: 1015 mail_gid: 105 mail_location: maildir:/var/spool/mail/%d/%n/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): acl quota imap_quota expire trash mail_plugins(imap): acl quota imap_quota expire trash mail_plugins(pop3): expire quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle imap_client_workarounds(imap): delay-newmail outlook-idle imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh dict_db_config: /etc/dovecot-db.conf auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: static socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vuser group: vuser plugin: quota: maildir quota_rule: *:storage=10240 quota_rule2: Trash:storage=100M acl: vfile:/etc/dovecot/acls trash: /etc/dovecot-trash.conf expire: Trash 14 Trash/* 14 Spam 14 expire_dict: proxy::expire dict: expire: mysql:/etc/dovecot-dict-expire.conf Rick Steeves http://www.sinister.net The more I learn, it seems, the less I know. Frazz
Re: [Dovecot] Inotify instance limit for user exceeded, disabling?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 27 May 2009, dove...@corwyn.net wrote: surprise given the error message really). I can fix that with echo 256 /proc/sys/fs/inotify/max_user_instances , but as /proc is temporary, so if I change it won't it break if/when the system reboots? See man sysctl Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSh1L9nWSIuGy1ktrAQJ+0wf+N6SKut3mM+6ZqOH2hjqgE9wsix9QfFeZ 5vVls1vS6hMlSQhqSXYMW0UrDqvrH2ypPbgZpoClTU+Xvtc0yPhkqy7Bf3EJwEGY 4RY0W/aDTNHw6SAB3ilmQ03CACtnxMLZiUFndWOaoY+LtfHvYZZwEuyFvE1n7cQo 60wplS3DMrxzBtdKzrjsSUR8UrDQSTTfY0F4iFY553+GzcgKOLyqzT2yin0avjeI Y3jYBIC9ucr87kb82Jkmk4F/rQc2Falyk56LAJ9MuNQqyCZa9qWdnLoy28oXoRYM fUNQ4y7oWyRr2zu6TknLpCKz9Xmd9+CiGfCUq8lORzdfT/cGlZRlYw== =uZj7 -END PGP SIGNATURE-
[Dovecot] 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.
Re: [Dovecot] Inotify instance limit for user exceeded, disabling.
Anders wrote: 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? Okay, reading the source has me think that this is an OS limit, so I increased /proc/sys/fs/inotify/max_user_watches Is there some way to calculate the upper limit? I imaging that each folder in each connection needs a watch? Cheers, Anders.
Re: [Dovecot] Inotify instance limit for user exceeded, disabling.
On May 5, 2008, at 11:15 AM, Anders wrote: Anders wrote: 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? Okay, reading the source has me think that this is an OS limit, so I increased /proc/sys/fs/inotify/max_user_watches It says instance limit, so I think the problem was max_user_instances instead. Is there some way to calculate the upper limit? I imaging that each folder in each connection needs a watch? They're added when IDLE command is run. Only one IDLE command can be running at a time per each connection. With maildir it listens for two directories. But there is only one instance created per process. I guess you're using a single UID for all users? In that case the upper limits are: - max_user_instances = max_mail_processes setting - max_user_watches = max_mail_processes setting*2 PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Inotify instance limit for user exceeded, disabling.
Timo Sirainen wrote: They're added when IDLE command is run. Only one IDLE command can be running at a time per each connection. With maildir it listens for two directories. But there is only one instance created per process. So each process has one inotify instance with just two watches. I was under the impression that subfolders were also watched, but after testing a bit, it seems to not be true. Only the SELECTed box is watched, right? What confused me was that Thunderbird will show new messages in several folders, but I guess it must be using multiple connections, one per open folder. Is there some way to have clients watch all folders? Server-side filtering loses a bit of its value when you are not notified of the new mail. I guess you're using a single UID for all users? In that case the upper limits are: - max_user_instances = max_mail_processes setting - max_user_watches = max_mail_processes setting*2 I think max_user_watches is per instance, so should that just be 2? Cheers, Anders.
