3 out of 10 TCP burst connections get stuck in SYN_SENT.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
3 out of 10 TCP burst connections get stuck in SYN_SENT.
I am trying to run a web proxy in Debian Buster. But while testing performance I saw only 7 or 8 parallel connections got established at a time, to narrow down the issue is not with my web proxy; i ran IPERF on the debian and from another linux client i ran iperf -c <debian buster IP> -P 10; the test do not run successfully.
If i change -P from 10 to 7, things are fine.
On the Debian Buster Side, I see connections stuck in SYN_SENT state with UNREPLIED status.
From netstat, I see,
<x> times the listen queue of a socket overflowed
<y> SYNs to LISTEN sockets dropped
where x and y are Equal.
Tried changing the TCP Backlog, SYN Backlog and disabled timestamp etc, nothing helped.
I am trying to run a web proxy in Debian Buster. But while testing performance I saw only 7 or 8 parallel connections got established at a time, to narrow down the issue is not with my web proxy; i ran IPERF on the debian and from another linux client i ran iperf -c <debian buster IP> -P 10; the test do not run successfully.
If i change -P from 10 to 7, things are fine.
On the Debian Buster Side, I see connections stuck in SYN_SENT state with UNREPLIED status.
From netstat, I see,
<x> times the listen queue of a socket overflowed
<y> SYNs to LISTEN sockets dropped
where x and y are Equal.
Tried changing the TCP Backlog, SYN Backlog and disabled timestamp etc, nothing helped.
Any suggestions ?
Either the web server is configured to only allow 7 connections, or your proxy server is set that way.
Check with the web site (or test it while bypassing the proxy) to see how many simultaneous clients it allows. Then check the proxy config for the same. If the web server is not in your control you may need to work with their admin to figure this out.
Last edited by computersavvy; 04-14-2021 at 02:44 PM.
If reply #2 isn't it then maybe some restriction or limit on some program either by design or because of load maybe?? Wonder if top will show any issue on it or other system monitor?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.