-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trafficserver 9.2.5 FIN sent immediatly on connection to backend server #11858
Comments
Forgot to mention: this is also logged from time to time 20241113.23h15m17s CONNECT: Invalid argument [22] connecting to 83.246.80.131:18443 for host='cloud-foo.de' url='https://cloud-foo.de:18443/favicon.ico' marking down |
|
This is #11465 and I've just pushed a backport of the fix in 10.x to the f40 repo. You can get that build (and provide feedback) here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b3c4e8da81 |
omg... it works \o/ |
I can't give the package a +1 karma, Fedoras Infrastructure Login is (again) down :( Update: FAS login fixed. |
Yay! |
OS: Fedora 40
Version: 9.2.5
Worked on Fedora 39 with same version, downgrade to fc39 version same release tested, same result.
It does not matter where the backendserver is, local on another port or on a different ip.
This dump is locally on the same server:
22:48:01.224680 IP 83.246.80.131.53420 > 83.246.80.131.18443: Flags [S], seq 4065112379, win 65495, options [mss 65495,sackOK,TS val 2381864768 ecr 0,nop,wscale 7], length 0
22:48:01.224689 IP 83.246.80.131.18443 > 83.246.80.131.53420: Flags [S.], seq 2155888146, ack 4065112380, win 65483, options [mss 65495,sackOK,TS val 2381864768 ecr 2381864768,nop,wscale 7], length 0
22:48:01.224698 IP 83.246.80.131.53420 > 83.246.80.131.18443: Flags [.], ack 1, win 512, options [nop,nop,TS val 2381864768 ecr 2381864768], length 0
22:48:01.224994 IP 83.246.80.131.53420 > 83.246.80.131.18443: Flags [F.], seq 1, ack 1, win 512, options [nop,nop,TS val 2381864769 ecr 2381864768], length 0
22:48:01.225168 IP 83.246.80.131.18443 > 83.246.80.131.53420: Flags [F.], seq 1, ack 2, win 512, options [nop,nop,TS val 2381864769 ecr 2381864769], length 0
22:48:01.225178 IP 83.246.80.131.53420 > 83.246.80.131.18443: Flags [.], ack 2, win 512, options [nop,nop,TS val 2381864769 ecr 2381864769], length 0
Immediatly after the SYN-ACK is ACKed ATS sends a FIN package. And than it logs:
20241113.22h48m01s CONNECT: attempt fail [CONNECTION_ERROR] to 83.246.80.131:18443 for host='cloud-foo.de' connection_result=Invalid argument [22] error=Invalid argument [22] attempts=3 url='https://cloud-foo.de:18443/equery.js'
A connect with curl to that ip:port works flawless.. The cert is the same as ATS would use.
the remap is unchanged for years now:
map http://cloud-foo.de/ http://cloud-foo.de:18080/
map https://cloud-foo.de/ https://cloud-foo.de:18443/
something is stopping ats from sending data at all throu that connection.
the firewall has been disabled , no change.
new Systemd version: "systemd-255.13-1.fc40.x86_64" old was systemd-254
Already tested:
The text was updated successfully, but these errors were encountered: