default_client_limit

P

pondoli

Verified User
Joined
Feb 3, 2010
Messages
15
Hi,


When I try to restart Dovecot from Service Monitor it will stop Dovecot but not start it:

Code: 
An error has occurred
Details
/sbin/service dovecot restart 2>&1


After running the start commando manually I get this response:

Code: 
[root@server etc]# /sbin/service dovecot restart
Shutting down dovecot:                                     [  OK  ]
Starting dovecot: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 2048), because of default_client_limit
                                                           [  OK  ]
[root@server etc]#

How can I fix this?


Thanks in advance!
 
Assuming that you are running CentOS, you can increase ulimit:

Edit /etc/security/limits.conf and add this two lines above # End of file, like this:

Code: 
*                soft    nofile          65535
*                hard    nofile          65535

# End of file

Then run "service dovecot restart" to check that the warning is not there anymore.

Edit: You can check you current limits with the command: ulimit -a
 
Hi,

I edited the config file and restart dovecot. But I'm still getting the same error:

Code: 
root@server security]# /sbin/service dovecot restart
Shutting down dovecot:                                     [  OK  ]
Starting dovecot: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 2048), because of default_client_limit
                                                           [  OK  ]
[root@server security]#


After the restart the ulimit -a returns:
Code: 
[root@server security]# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 71680
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 71680
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
[root@server security]#
 
I see that your ulimit -a still has 1024 on open files:

Code: 
open files                      (-n) 1024

The above line should show 65535 after you added the two lines to /etc/security/limits.conf

I don't know why this did not work for you. You might need to log out of your ssh session and then log in again before you see the changes. So try to log out of ssh, and then log in and run the ulimit -a command again to see if it still shows 1024.

Also maybe this is a VPS? I don't know if that can be a problem for this.

However, you should not need to worry about the warning in Dovecot, it should be harmless. Also that warning should not be related to that Dovecot did not start for you.

However, I also had the Dovecot warning, and the warning went away for me after I raised the open files like I posted previous reply.
 
You must log in or register to reply here.
Back
Top