mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
new section on open file limits
This commit is contained in:
parent
7e4d2bcbbf
commit
2539e1e735
1 changed files with 21 additions and 0 deletions
|
@ -30,4 +30,25 @@ When developing the state tree it is geenrally recommended to invoke
|
|||
state.highstate with salt-call, this displays a great deal more information
|
||||
about the highstate execution then if it is called remotely.
|
||||
|
||||
Too many open files
|
||||
===================
|
||||
|
||||
The salt-master needs at least 2 sockets per host that connects to it, one for
|
||||
the Publisher and one for response port. Thus, large installations may upon
|
||||
scaling up the number of minions accessing a given master, encounter:
|
||||
|
||||
12:45:29,289 [salt.master ][INFO ] Starting Salt worker process 38
|
||||
Too many open files
|
||||
sock != -1 (tcp_listener.cpp:335)
|
||||
|
||||
The solution to this would be to check the number of files allowed to be
|
||||
opened by the user running salt-master (root by default):
|
||||
|
||||
[root@salt-master ~]# ulimit -n
|
||||
1024
|
||||
|
||||
And modify that value to be at least equal to the number of minions x 2.
|
||||
This setting can be changed in limits.conf as the nofile value(s),
|
||||
and activated upon new a login of the specified user.
|
||||
|
||||
So, an environment with 1800 minions, would need 1800 x 2 = 3600 as a minimum
|
||||
|
|
Loading…
Add table
Reference in a new issue