1. Topics
  2. How Warden limit socket queue?

How Warden limit socket queue?

Matthew Sykes <matthew.sykes@...>
 

As a user, you can't. Even though somaxconn is associated with the network
namespace, you need to be privileged (root) to change it.

If you wanted a higher default across all containers, you could modify
warden to do that as part if its net setup (linux/skeleton/net.sh).

On Mon, Nov 2, 2015 at 3:38 AM, yancey0623 <yancey0623(a)163.com> wrote:

Dear all!

I pushed an app with uwsgi, but it crashed. After investigation, the
argument “listen” in uwsgi.ini(uwsgi config file) is cause of crash. it’s
so large, when i reduce it from 256 to 128, it will be ok. here is the
error info


2015-11-02T16:35:11.57+0800 [App/0] ERR Listen queue size is greater
than the system max net.core.somaxconn (128).

2015-11-02T16:35:11.57+0800 [App/0] ERR VACUUM: pidfile removed.

my os argument is:

paas(a)tsh-cf-dev-01:~/hello-python$ cat /proc/sys/net/core/somaxconn

1024

Who knows where can i config these network args.?
--
Matthew Sykes
matthew.sykes(a)gmail.com

?
attachment.html

Yancey
 

Dear all!

I pushed an app with uwsgi, but it crashed. After investigation, the argument “listen” in uwsgi.ini(uwsgi config file)  is cause of crash. it’s so large, when i reduce it from 256 to 128, it will be ok. here is the error info


2015-11-02T16:35:11.57+0800 [App/0]      ERR Listen queue size is greater than the system max net.core.somaxconn (128).

2015-11-02T16:35:11.57+0800 [App/0]      ERR VACUUM: pidfile removed.

my os argument is:

paas@tsh-cf-dev-01:~/hello-python$ cat /proc/sys/net/core/somaxconn  

1024

Who knows where can i config these network args.?
1 - 2 of 2