client initial SYN packet intermittently ignored.....resulting in sloooowwwww website
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
client initial SYN packet intermittently ignored.....resulting in sloooowwwww website
Hi, I am running Ubuntu 21.04 (have nothing to compare to previous vers) with Apache2 and am trying to launch a web server. I find when I connect to the server it will intermittently not respond to the initial client's SYN packet. This can be seen on Tshark traces. I have searched various forums which now suggest that parameters in /etc/sysctl may need tweaking.(still no joy) All attempts to fix have failed.
Would anyone have any other ideas on areas to address to effect a fix ?? I can't believe this a generic problem on 21.04. I have discounted a problem with internet access, routers etc
Should I bite the bullet and load up Fedora or Centos. ??
Windows, as a matter of principle, is not an option.
SYN packet has nothing to do with the web server. It is part of TCP/IP protocol. Assuming you have a server accepting connections, not responding to SYN means you are either out of some resource: memory, network buffers, max connections, etc., or you are blocking connections with firewall.
Check the apache access and error log. If it drops SYN, apache should not see it at all.
Try making a simple listener with netcat (nc) and see if it does the same thing.
smallpond....or ....the tcp handshake has EVERYTHING to do with a web conversation as it's TCP based. Thank you for your input. I found the prob with a couple of anomolous routes and it's now fixed. You need to reign in your misguided advice and try and help peeps, instead of being a ..... xxxx night night
Last edited by rtmistler; 09-12-2021 at 10:05 AM.
Reason: Removed insults
“a couple of anomolous routes” seems to me to be an example of “blocking connections”…
So smallpond did, in fact, point to the solution in addition to suggesting other possibilities.
Web servers are networking 7th layer things. The TCP conversation happens in the 3rd or 4th layer…I’m not sure which…I’m a 7th layer guy…
Glad the we were able to help. Please mark your thread solved.
smallpond....or ....the tcp handshake has EVERYTHING to do with a web conversation as it's TCP based. Thank you for your input. I found the prob with a couple of anomolous routes and it's now fixed. You need to reign in your misguided advice and try and help peeps, instead of being a ..... xxxx night night
So bad/incorrect routes aren't a network issue?? Good to know. And aren't the vast majority of network services TCP based?? Smallpond correctly said it was some sort of network issue; and it was.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.