[MXS-866] Error 24, Too many open files. Failed to accept new client connection. Created: 2016-09-13  Updated: 2016-09-22  Resolved: 2016-09-20

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 1.4.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: cai sunny Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Linux 2.6.32-642.4.2.el6.x86_64 #1 SMP



 Description   

The connections about 1000.
But in maxscale log, it show error:
2016-09-13 07:34:55 error : Failed to obtain address for host XXXXXdb02, Temporary failure in name resolution
2016-09-13 07:34:49 error : Error 24, Too many open files. Failed to accept new client connection.
2016-09-13 07:34:49 error : Error 24, Too many open files. Failed to accept new client connection.
2016-09-13 07:34:51 error : Error 24, Too many open files. Failed to accept new client connection.
2016-09-13 07:34:51 error : Error 24, Too many open files. Failed to accept new client connection.

For maxscale process:
ps -ef|grep max
maxscale 25820 1 0 11:05 ? 00:00:13 /usr/bin/maxscale --user=maxscale
root 30122 25760 0 11:51 pts/0 00:00:00 grep max

cat /proc/25820/limits 

Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            10485760             unlimited            bytes     
Max core file size        0                    0                    bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             16384                16384                processes 
Max open files            65536                65536                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       15223                15223                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us

Please help check how to fix it.
Thanks!

 Comments   
Comment by Johan Wikman [ 2016-09-20 ]

Could you try updating to 1.4.3 and check whether the problem still exists.

Johan

Comment by Johan Wikman [ 2016-09-20 ]

Do you have any user specific limits? If so increase the limits for the maxscale user.

Comment by Johan Wikman [ 2016-09-20 ]

Closing as this does not appear to be a maxscale problem but a system configuration issue.

Comment by Johan Wikman [ 2016-09-20 ]

Actually, in 2.0 the init script sets the open file limit to a higher value. Please check from there how to address the issue.

Comment by cai sunny [ 2016-09-22 ]

From /proc/25820/limits, there is no user specific limits.

Generated at Thu Feb 08 04:02:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.