On 2/11/25 2:24 PM, Yann Ylavic wrote:
On Fri, Feb 7, 2025 at 5:56 PM jean-frederic clere <jfcl...@gmail.com> wrote:
I have the above error on windows:
+++
[Fri Feb 07 08:46:33.110167 2025] [proxy:debug] [pid 7440:tid 1168]
mod_proxy.c(1465): [client ::1:56280] AH01143: Running scheme balancer
handler (attempt 0)
[Fri Feb 07 08:46:33.110167 2025] [proxy_ajp:debug] [pid 7440:tid 1168]
mod_proxy_ajp.c(790): [client ::1:56280] AH00895: serving URL
ajp://[0:0:0:0:0:0:0:1]/
[Fri Feb 07 08:46:33.110167 2025] [proxy:debug] [pid 7440:tid 1168]
proxy_util.c(2797): AH00942: AJP: has acquired connection for
(0:0:0:0:0:0:0:1:8009)
[Fri Feb 07 08:46:33.110167 2025] [proxy:debug] [pid 7440:tid 1168]
proxy_util.c(3242): [client ::1:56280] AH00944: connecting
ajp://[0:0:0:0:0:0:0:1]/ to 0:0:0:0:0:0:0:1:8009
[Fri Feb 07 08:46:33.110167 2025] [proxy:debug] [pid 7440:tid 1168]
proxy_util.c(3450): [client ::1:56280] AH00947: connecting / to
[::1]:8009 (0:0:0:0:0:0:0:1:8009)
[Fri Feb 07 08:46:33.110167 2025] [proxy:error] [pid 7440:tid 2552] (OS
10048)Only one usage of each socket address (protocol/network
address/port) is normally permitted. : AH00957: AJP: attempt to connect
to [::1]:8009 (0:0:0:0:0:0:0:1:8009) failed
[Fri Feb 07 08:46:33.110167 2025] [proxy:error] [pid 7440:tid 2552]
AH00959: ap_proxy_connect_backend disabling worker for
(0:0:0:0:0:0:0:1:8009) for 60s
[Fri Feb 07 08:46:33.110167 2025] [proxy_ajp:error] [pid 7440:tid 2552]
[client ::1:49653] AH00896: failed to make connection to backend:
0:0:0:0:0:0:0:1
[Fri Feb 07 08:46:33.110167 2025] [proxy:debug] [pid 7440:tid 2552]
proxy_util.c(2813): AH00943: AJP: has released connection for
(0:0:0:0:0:0:0:1:8009)
+++
Does that ring bell to someone? I am using 2.4.x and my own build on
windows (windows server 2019)
"(OS 10048)" seems to be the "ephemeral ports exhausted" error on
Windows, so maybe [0] can help?
Yes that is the problem, but the cause is somewhere in httpd proxy.
When running a test using ab with my module (mod_cluster that uses
mod_proxy API), it passes with 2.4.58 and fails with 2.4.59.
There many more sockets in TIME_WAIT (20000 vs 15000) in 2.4.59
+++
$ netstat -n | grep TIME_WAIT | wc -l
21620
+++
Something in mod_proxy API changed and causes the problem, I need to
figure out what and how to call it the right way.
[0]
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/default-dynamic-port-range-tcpip-chang
helps
Regards;
Yann.
--
Cheers
Jean-Frederic
