> On 25 June 2014 11:53, Roberto De Ioris <[email protected]> wrote: > >> >> > >> > >> > I think that this may be a system related limit, but not sure why >> there >> is >> > not efet when I change them: >> > >> > *net.core.somaxconn=1000000* >> > *net.core.netdev_max_backlog = 1000000* >> > *net.ipv4.tcp_max_syn_backlog=1000000* >> > *net.netfilter.nf_conntrack_max=1000000* >> > *net.netfilter.nf_conntrack_count=250000* >> > >> > After restart I get them same issue. >> > >> > Also netstatus: netstat -an | awk '/^tcp/ {print $NF}' | sort | uniq >> -c | >> > sort -rn >> > >> > >> > *15389 TIME_WAIT* >> > * 4494 ESTABLISHED* >> > * 474 FIN_WAIT2* >> > * 462 CLOSE_WAIT* >> > * 55 LAST_ACK* >> > * 31 FIN_WAIT1* >> > * 18 LISTEN* >> > * 16 SYN_RECV* >> > * 4 CLOSING* >> > * 1 SYN_SENT* >> > >> > >> > >> >> On my systems i cannot set the backlog to a value higher than 16bit >> (65535). >> > > In my case there is limit only to net.core.somaxconn = 65535, for other > settings I see no errors when I apply them with sysctl -p. > >
net.core.somaxconn is the only one needed for the listen() syscall, so it is the one you need to ensure it is set correctly. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
