Software: Apache. PHP/5.5.15 uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 SYSTEM Safe-mode: OFF (not secure) E:\nuevo\apache\logs\ drwxrwxrwx | |
| Viewing file: Select action/file-type: [Sun Nov 03 00:10:23.706669 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 00:14:55.381146 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 00:14:55.396746 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 00:15:46.237235 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 00:17:00.976967 2019] [proxy:error] [pid 14276:tid 18380] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:17:00.976967 2019] [proxy:error] [pid 14276:tid 18380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:17:00.976967 2019] [proxy_http:error] [pid 14276:tid 18380] [client 201.245.192.253:41470] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:17:02.022168 2019] [proxy:error] [pid 14276:tid 18232] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:17:02.022168 2019] [proxy_http:error] [pid 14276:tid 18232] [client 201.245.192.253:37712] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:17:23.051005 2019] [proxy:error] [pid 14276:tid 18232] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:17:23.051005 2019] [proxy:error] [pid 14276:tid 18232] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:17:23.051005 2019] [proxy_http:error] [pid 14276:tid 18232] [client 201.245.192.253:37714] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:27:01.437621 2019] [proxy:error] [pid 14276:tid 18232] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:27:01.437621 2019] [proxy:error] [pid 14276:tid 18232] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:27:01.437621 2019] [proxy_http:error] [pid 14276:tid 18232] [client 201.245.192.253:41476] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:27:01.718422 2019] [proxy:error] [pid 14276:tid 18424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:27:01.718422 2019] [proxy_http:error] [pid 14276:tid 18424] [client 201.245.192.253:37724] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:27:22.747259 2019] [proxy:error] [pid 14276:tid 18424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:27:22.747259 2019] [proxy:error] [pid 14276:tid 18424] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:27:22.747259 2019] [proxy_http:error] [pid 14276:tid 18424] [client 201.245.192.253:37726] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:37:00.697074 2019] [proxy:error] [pid 14276:tid 18764] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:37:00.697074 2019] [proxy:error] [pid 14276:tid 18764] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:37:00.697074 2019] [proxy_http:error] [pid 14276:tid 18764] [client 201.245.192.253:41498] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:37:01.508275 2019] [proxy:error] [pid 14276:tid 18280] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:37:01.508275 2019] [proxy_http:error] [pid 14276:tid 18280] [client 201.245.192.253:37736] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 00:37:22.552712 2019] [proxy:error] [pid 14276:tid 18280] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 00:37:22.552712 2019] [proxy:error] [pid 14276:tid 18280] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 00:37:22.552712 2019] [proxy_http:error] [pid 14276:tid 18280] [client 201.245.192.253:37738] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:16:26.503629 2019] [proxy:error] [pid 14276:tid 18540] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Sun Nov 03 01:16:26.503629 2019] [proxy:error] [pid 14276:tid 18540] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Sun Nov 03 01:16:26.503629 2019] [proxy_http:error] [pid 14276:tid 18540] [client 152.61.128.50:39659] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Sun Nov 03 01:16:26.722029 2019] [proxy:error] [pid 14276:tid 18540] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Nov 03 01:16:26.940430 2019] [proxy:error] [pid 14276:tid 18540] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Nov 03 01:17:01.057690 2019] [proxy:error] [pid 14276:tid 19176] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:17:01.057690 2019] [proxy:error] [pid 14276:tid 19176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 01:17:01.057690 2019] [proxy_http:error] [pid 14276:tid 19176] [client 201.245.192.253:37768] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:17:01.057690 2019] [proxy:error] [pid 14276:tid 19176] AH00940: HTTP: disabled connection for (172.22.1.16) [Sun Nov 03 01:17:01.135690 2019] [proxy:error] [pid 14276:tid 18540] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:17:01.135690 2019] [proxy_http:error] [pid 14276:tid 18540] [client 201.245.192.253:41516] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:27:00.519943 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:27:00.519943 2019] [proxy:error] [pid 14276:tid 18852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 01:27:00.519943 2019] [proxy_http:error] [pid 14276:tid 18852] [client 201.245.192.253:41522] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:27:01.440344 2019] [proxy:error] [pid 14276:tid 19176] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:27:01.440344 2019] [proxy_http:error] [pid 14276:tid 19176] [client 201.245.192.253:37780] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:27:22.469181 2019] [proxy:error] [pid 14276:tid 19176] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:27:22.469181 2019] [proxy:error] [pid 14276:tid 19176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 01:27:22.469181 2019] [proxy_http:error] [pid 14276:tid 19176] [client 201.245.192.253:37782] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:30:01.963861 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 01:32:46.216550 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 01:37:00.855797 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:37:00.855797 2019] [proxy:error] [pid 14276:tid 18336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 01:37:00.855797 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:41578] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:37:01.089798 2019] [proxy:error] [pid 14276:tid 18436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:37:01.089798 2019] [proxy_http:error] [pid 14276:tid 18436] [client 201.245.192.253:37792] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 01:37:22.103034 2019] [proxy:error] [pid 14276:tid 18436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 01:37:22.103034 2019] [proxy:error] [pid 14276:tid 18436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 01:37:22.103034 2019] [proxy_http:error] [pid 14276:tid 18436] [client 201.245.192.253:37794] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:17:00.327212 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:17:00.327212 2019] [proxy:error] [pid 14276:tid 18336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:17:00.327212 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:41596] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:17:00.810812 2019] [proxy:error] [pid 14276:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:17:00.810812 2019] [proxy_http:error] [pid 14276:tid 17956] [client 201.245.192.253:37824] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:17:21.839649 2019] [proxy:error] [pid 14276:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:17:21.839649 2019] [proxy:error] [pid 14276:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:17:21.839649 2019] [proxy_http:error] [pid 14276:tid 17956] [client 201.245.192.253:37826] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:20:53.922022 2019] [negotiation:error] [pid 14276:tid 18892] [client 34.202.229.16:49476] AH00690: no acceptable variant: E:/nuevo/apache/error/HTTP_NOT_FOUND.html.var [Sun Nov 03 02:20:54.670823 2019] [negotiation:error] [pid 14276:tid 18980] [client 34.202.229.16:49576] AH00690: no acceptable variant: E:/nuevo/apache/error/HTTP_NOT_FOUND.html.var [Sun Nov 03 02:27:00.819066 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:27:00.819066 2019] [proxy:error] [pid 14276:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:27:00.819066 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:41602] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:27:01.599068 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:27:01.599068 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:37836] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:27:22.627905 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:27:22.627905 2019] [proxy:error] [pid 14276:tid 18644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:27:22.627905 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:37838] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:37:00.078519 2019] [proxy:error] [pid 14276:tid 19164] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:37:00.078519 2019] [proxy:error] [pid 14276:tid 19164] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:37:00.078519 2019] [proxy_http:error] [pid 14276:tid 19164] [client 201.245.192.253:41608] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:37:01.217321 2019] [proxy:error] [pid 14276:tid 18448] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:37:01.217321 2019] [proxy_http:error] [pid 14276:tid 18448] [client 201.245.192.253:37848] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:37:22.261758 2019] [proxy:error] [pid 14276:tid 18448] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 02:37:22.261758 2019] [proxy:error] [pid 14276:tid 18448] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 02:37:22.261758 2019] [proxy_http:error] [pid 14276:tid 18448] [client 201.245.192.253:37850] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 02:44:51.636147 2019] [proxy:error] [pid 14276:tid 18728] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Sun Nov 03 02:44:51.636147 2019] [proxy:error] [pid 14276:tid 18728] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Sun Nov 03 02:44:51.636147 2019] [proxy_http:error] [pid 14276:tid 18728] [client 152.61.192.232:42674] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Sun Nov 03 02:44:51.901348 2019] [proxy:error] [pid 14276:tid 18728] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Nov 03 02:44:52.119748 2019] [proxy:error] [pid 14276:tid 18728] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Nov 03 02:56:20.736157 2019] [proxy:error] [pid 14276:tid 17944] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Nov 03 02:56:20.736157 2019] [proxy:error] [pid 14276:tid 17944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Nov 03 02:56:20.736157 2019] [proxy_http:error] [pid 14276:tid 17944] [client 66.249.66.153:40348] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Nov 03 03:17:00.392335 2019] [proxy:error] [pid 14276:tid 18920] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:17:00.392335 2019] [proxy:error] [pid 14276:tid 18920] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:17:00.392335 2019] [proxy_http:error] [pid 14276:tid 18920] [client 201.245.192.253:41618] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:17:01.000736 2019] [proxy:error] [pid 14276:tid 19164] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:17:01.000736 2019] [proxy_http:error] [pid 14276:tid 19164] [client 201.245.192.253:37882] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:17:22.045173 2019] [proxy:error] [pid 14276:tid 19164] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:17:22.045173 2019] [proxy:error] [pid 14276:tid 19164] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:17:22.045173 2019] [proxy_http:error] [pid 14276:tid 19164] [client 201.245.192.253:37884] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:27:00.728189 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:27:00.728189 2019] [proxy:error] [pid 14276:tid 18336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:27:00.728189 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:41624] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:27:00.837389 2019] [proxy:error] [pid 14276:tid 18728] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:27:00.837389 2019] [proxy_http:error] [pid 14276:tid 18728] [client 201.245.192.253:37894] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:27:21.850626 2019] [proxy:error] [pid 14276:tid 18728] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:27:21.850626 2019] [proxy:error] [pid 14276:tid 18728] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:27:21.850626 2019] [proxy_http:error] [pid 14276:tid 18728] [client 201.245.192.253:37896] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:37:00.065642 2019] [proxy:error] [pid 14276:tid 18836] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:37:00.065642 2019] [proxy:error] [pid 14276:tid 18836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:37:00.065642 2019] [proxy_http:error] [pid 14276:tid 18836] [client 201.245.192.253:41630] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:37:00.580443 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:37:00.580443 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:37906] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 03:37:21.609280 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 03:37:21.609280 2019] [proxy:error] [pid 14276:tid 18644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 03:37:21.609280 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:37908] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:17:00.535458 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:17:00.535458 2019] [proxy:error] [pid 14276:tid 18644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:17:00.535458 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:41636] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:17:01.097059 2019] [proxy:error] [pid 14276:tid 18448] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:17:01.097059 2019] [proxy_http:error] [pid 14276:tid 18448] [client 201.245.192.253:37938] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:17:22.125896 2019] [proxy:error] [pid 14276:tid 18448] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:17:22.125896 2019] [proxy:error] [pid 14276:tid 18448] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:17:22.125896 2019] [proxy_http:error] [pid 14276:tid 18448] [client 201.245.192.253:37940] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:26:59.950911 2019] [proxy:error] [pid 14276:tid 18692] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:26:59.950911 2019] [proxy:error] [pid 14276:tid 18692] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:26:59.950911 2019] [proxy_http:error] [pid 14276:tid 18692] [client 201.245.192.253:41642] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:27:00.886913 2019] [proxy:error] [pid 14276:tid 18728] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:27:00.886913 2019] [proxy_http:error] [pid 14276:tid 18728] [client 201.245.192.253:37950] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:27:21.915749 2019] [proxy:error] [pid 14276:tid 18728] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:27:21.915749 2019] [proxy:error] [pid 14276:tid 18728] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:27:21.915749 2019] [proxy_http:error] [pid 14276:tid 18728] [client 201.245.192.253:37952] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:37:00.317965 2019] [proxy:error] [pid 14276:tid 18836] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:37:00.317965 2019] [proxy:error] [pid 14276:tid 18836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:37:00.317965 2019] [proxy_http:error] [pid 14276:tid 18836] [client 201.245.192.253:41656] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:37:00.567566 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:37:00.567566 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:37962] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:37:21.596403 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 04:37:21.596403 2019] [proxy:error] [pid 14276:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 04:37:21.596403 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:37964] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 04:41:21.727625 2019] [core:error] [pid 14276:tid 18352] (20024)The given path is misformatted or contained invalid characters: [client 159.203.187.200:43994] AH00127: Cannot map GET /w00tw00t.at.blackhats.romanian.anti-sec:) HTTP/1.1 to file [Sun Nov 03 04:41:21.899225 2019] [authz_core:error] [pid 14276:tid 19164] [client 159.203.187.200:44030] AH01630: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin [Sun Nov 03 04:41:22.055225 2019] [authz_core:error] [pid 14276:tid 18836] [client 159.203.187.200:44080] AH01630: client denied by server configuration: E:/nuevo/phpMyAdmin/scripts [Sun Nov 03 05:00:57.813690 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 05:00:57.813690 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 05:16:59.851780 2019] [proxy:error] [pid 14276:tid 18920] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:16:59.851780 2019] [proxy:error] [pid 14276:tid 18920] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:16:59.851780 2019] [proxy_http:error] [pid 14276:tid 18920] [client 201.245.192.253:41662] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:17:00.210581 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:17:00.210581 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:37994] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:17:21.239417 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:17:21.239417 2019] [proxy:error] [pid 14276:tid 18336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:17:21.239417 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:37996] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:22:23.099948 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 05:27:00.172034 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:27:00.172034 2019] [proxy:error] [pid 14276:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:27:00.172034 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:41668] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:27:00.998836 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:27:00.998836 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:38006] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:27:22.027673 2019] [proxy:error] [pid 14276:tid 18644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:27:22.027673 2019] [proxy:error] [pid 14276:tid 18644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:27:22.027673 2019] [proxy_http:error] [pid 14276:tid 18644] [client 201.245.192.253:38008] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:36:59.525087 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 05:36:59.571887 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:36:59.571887 2019] [proxy:error] [pid 14276:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:36:59.571887 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:41674] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:37:00.804289 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:37:00.804289 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:38018] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:37:21.833126 2019] [proxy:error] [pid 14276:tid 18336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 05:37:21.833126 2019] [proxy:error] [pid 14276:tid 18336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 05:37:21.833126 2019] [proxy_http:error] [pid 14276:tid 18336] [client 201.245.192.253:38020] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 05:49:22.632392 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 05:50:06.047268 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 06:01:50.934507 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 06:01:50.950107 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 06:14:07.396200 2019] [authz_core:error] [pid 14276:tid 17944] [client 51.15.216.220:52308] AH01630: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin [Sun Nov 03 06:14:07.708201 2019] [authz_core:error] [pid 14276:tid 18728] [client 51.15.216.220:52508] AH01630: client denied by server configuration: E:/nuevo/phpMyAdmin/scripts [Sun Nov 03 06:17:00.041703 2019] [proxy:error] [pid 14276:tid 18352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:17:00.041703 2019] [proxy:error] [pid 14276:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:17:00.041703 2019] [proxy_http:error] [pid 14276:tid 18352] [client 201.245.192.253:41694] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:17:00.166504 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:17:00.166504 2019] [proxy_http:error] [pid 14276:tid 18852] [client 201.245.192.253:38050] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:17:21.210941 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:17:21.210941 2019] [proxy:error] [pid 14276:tid 18852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:17:21.210941 2019] [proxy_http:error] [pid 14276:tid 18852] [client 201.245.192.253:38052] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:26:59.379156 2019] [proxy:error] [pid 14276:tid 19136] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:26:59.379156 2019] [proxy:error] [pid 14276:tid 19136] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:26:59.379156 2019] [proxy_http:error] [pid 14276:tid 19136] [client 201.245.192.253:41700] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:26:59.909557 2019] [proxy:error] [pid 14276:tid 19004] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:26:59.909557 2019] [proxy_http:error] [pid 14276:tid 19004] [client 201.245.192.253:38062] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:27:21.031994 2019] [proxy:error] [pid 14276:tid 19004] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:27:21.031994 2019] [proxy:error] [pid 14276:tid 19004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:27:21.031994 2019] [proxy_http:error] [pid 14276:tid 19004] [client 201.245.192.253:38064] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:27:44.900036 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 06:36:59.808611 2019] [proxy:error] [pid 14276:tid 18980] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:36:59.808611 2019] [proxy:error] [pid 14276:tid 18980] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:36:59.808611 2019] [proxy_http:error] [pid 14276:tid 18980] [client 201.245.192.253:41706] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:37:00.713412 2019] [proxy:error] [pid 14276:tid 18920] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:37:00.713412 2019] [proxy_http:error] [pid 14276:tid 18920] [client 201.245.192.253:38074] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 06:37:21.757849 2019] [proxy:error] [pid 14276:tid 18920] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 06:37:21.757849 2019] [proxy:error] [pid 14276:tid 18920] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 06:37:21.757849 2019] [proxy_http:error] [pid 14276:tid 18920] [client 201.245.192.253:38076] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:04:37.202322 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 07:08:43.464354 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 07:16:59.280025 2019] [proxy:error] [pid 14276:tid 18344] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:16:59.280025 2019] [proxy:error] [pid 14276:tid 18344] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:16:59.280025 2019] [proxy_http:error] [pid 14276:tid 18344] [client 201.245.192.253:41712] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:17:00.060026 2019] [proxy:error] [pid 14276:tid 19052] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:17:00.060026 2019] [proxy_http:error] [pid 14276:tid 19052] [client 201.245.192.253:38106] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:17:21.104463 2019] [proxy:error] [pid 14276:tid 19052] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:17:21.104463 2019] [proxy:error] [pid 14276:tid 19052] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:17:21.104463 2019] [proxy_http:error] [pid 14276:tid 19052] [client 201.245.192.253:38108] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:26:59.662680 2019] [proxy:error] [pid 14276:tid 18160] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:26:59.662680 2019] [proxy:error] [pid 14276:tid 18160] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:26:59.662680 2019] [proxy_http:error] [pid 14276:tid 18160] [client 201.245.192.253:41718] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:26:59.849880 2019] [proxy:error] [pid 14276:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:26:59.849880 2019] [proxy_http:error] [pid 14276:tid 18080] [client 201.245.192.253:38118] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:27:20.956717 2019] [proxy:error] [pid 14276:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:27:20.956717 2019] [proxy:error] [pid 14276:tid 18080] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:27:20.956717 2019] [proxy_http:error] [pid 14276:tid 18080] [client 201.245.192.253:38120] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:27:59.816385 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 07:36:59.031332 2019] [proxy:error] [pid 14276:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:36:59.031332 2019] [proxy:error] [pid 14276:tid 18080] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:36:59.031332 2019] [proxy_http:error] [pid 14276:tid 18080] [client 201.245.192.253:41728] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:37:00.638135 2019] [proxy:error] [pid 14276:tid 18896] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:37:00.638135 2019] [proxy_http:error] [pid 14276:tid 18896] [client 201.245.192.253:38130] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 07:37:21.682572 2019] [proxy:error] [pid 14276:tid 18896] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 07:37:21.682572 2019] [proxy:error] [pid 14276:tid 18896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 07:37:21.682572 2019] [proxy_http:error] [pid 14276:tid 18896] [client 201.245.192.253:38132] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:11:07.439730 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 08:13:40.397999 2019] [proxy:error] [pid 14276:tid 18564] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:13:40.397999 2019] [proxy:error] [pid 14276:tid 18564] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:13:40.397999 2019] [proxy_http:error] [pid 14276:tid 18564] [client 66.249.88.123:52170] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:13:41.412001 2019] [proxy:error] [pid 14276:tid 18232] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:13:41.412001 2019] [proxy_http:error] [pid 14276:tid 18232] [client 66.249.88.127:45143] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:13:45.483608 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:13:45.483608 2019] [proxy_http:error] [pid 14276:tid 18852] [client 179.18.12.57:29441] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:14:07.713647 2019] [proxy:error] [pid 14276:tid 19108] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:14:07.713647 2019] [proxy:error] [pid 14276:tid 19108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:14:07.713647 2019] [proxy_http:error] [pid 14276:tid 19108] [client 181.53.12.41:32799] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:15:06.510150 2019] [proxy:error] [pid 14276:tid 18828] AH00940: HTTP: disabled connection for (172.22.1.16) [Sun Nov 03 08:15:42.561813 2019] [proxy:error] [pid 14276:tid 18932] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:15:42.561813 2019] [proxy:error] [pid 14276:tid 18932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:15:42.561813 2019] [proxy_http:error] [pid 14276:tid 18932] [client 181.53.12.41:31349] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:16:59.547949 2019] [proxy:error] [pid 14276:tid 18828] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:16:59.547949 2019] [proxy:error] [pid 14276:tid 18828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:16:59.547949 2019] [proxy_http:error] [pid 14276:tid 18828] [client 201.245.192.253:41782] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:17:00.249950 2019] [proxy:error] [pid 14276:tid 19020] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:17:00.249950 2019] [proxy_http:error] [pid 14276:tid 19020] [client 201.245.192.253:38162] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:17:21.278787 2019] [proxy:error] [pid 14276:tid 19020] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:17:21.278787 2019] [proxy:error] [pid 14276:tid 19020] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:17:21.278787 2019] [proxy_http:error] [pid 14276:tid 19020] [client 201.245.192.253:38164] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:18:03.835662 2019] [proxy:error] [pid 14276:tid 18168] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:18:03.835662 2019] [proxy:error] [pid 14276:tid 18168] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:18:03.835662 2019] [proxy_http:error] [pid 14276:tid 18168] [client 181.53.12.41:18546] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 08:19:06.953372 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 08:26:58.947801 2019] [proxy:error] [pid 14276:tid 18564] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:26:58.947801 2019] [proxy:error] [pid 14276:tid 18564] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:26:58.947801 2019] [proxy_http:error] [pid 14276:tid 18564] [client 201.245.192.253:41870] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:26:59.961803 2019] [proxy:error] [pid 14276:tid 19108] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:26:59.961803 2019] [proxy_http:error] [pid 14276:tid 19108] [client 201.245.192.253:38174] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:27:21.068640 2019] [proxy:error] [pid 14276:tid 19108] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:27:21.068640 2019] [proxy:error] [pid 14276:tid 19108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:27:21.068640 2019] [proxy_http:error] [pid 14276:tid 19108] [client 201.245.192.253:38176] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:36:59.346056 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:36:59.346056 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:36:59.346056 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:41876] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:36:59.704857 2019] [proxy:error] [pid 14276:tid 18104] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:36:59.704857 2019] [proxy_http:error] [pid 14276:tid 18104] [client 201.245.192.253:38186] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 08:37:20.733693 2019] [proxy:error] [pid 14276:tid 18104] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 08:37:20.733693 2019] [proxy:error] [pid 14276:tid 18104] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 08:37:20.733693 2019] [proxy_http:error] [pid 14276:tid 18104] [client 201.245.192.253:38188] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:16:58.911071 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:16:58.911071 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:16:58.911071 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:41896] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:17:00.112273 2019] [proxy:error] [pid 14276:tid 18516] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:17:00.112273 2019] [proxy_http:error] [pid 14276:tid 18516] [client 201.245.192.253:38222] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:17:21.141110 2019] [proxy:error] [pid 14276:tid 18516] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:17:21.141110 2019] [proxy:error] [pid 14276:tid 18516] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:17:21.141110 2019] [proxy_http:error] [pid 14276:tid 18516] [client 201.245.192.253:38224] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:22:28.274449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 09:26:59.262525 2019] [proxy:error] [pid 14276:tid 18232] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:26:59.262525 2019] [proxy:error] [pid 14276:tid 18232] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:26:59.262525 2019] [proxy_http:error] [pid 14276:tid 18232] [client 201.245.192.253:41902] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:26:59.886526 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:26:59.886526 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:38234] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:27:20.915363 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:27:20.915363 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:27:20.915363 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:38236] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:36:58.740378 2019] [proxy:error] [pid 14276:tid 18620] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:36:58.740378 2019] [proxy:error] [pid 14276:tid 18620] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:36:58.740378 2019] [proxy_http:error] [pid 14276:tid 18620] [client 201.245.192.253:41908] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:36:59.598379 2019] [proxy:error] [pid 14276:tid 18488] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:36:59.598379 2019] [proxy_http:error] [pid 14276:tid 18488] [client 201.245.192.253:38246] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 09:37:20.627216 2019] [proxy:error] [pid 14276:tid 18488] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 09:37:20.627216 2019] [proxy:error] [pid 14276:tid 18488] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 09:37:20.627216 2019] [proxy_http:error] [pid 14276:tid 18488] [client 201.245.192.253:38248] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:16:59.194594 2019] [proxy:error] [pid 14276:tid 19116] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:16:59.194594 2019] [proxy:error] [pid 14276:tid 19116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:16:59.194594 2019] [proxy_http:error] [pid 14276:tid 19116] [client 201.245.192.253:41974] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:17:00.114996 2019] [proxy:error] [pid 14276:tid 18548] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:17:00.114996 2019] [proxy_http:error] [pid 14276:tid 18548] [client 201.245.192.253:38284] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:17:21.128233 2019] [proxy:error] [pid 14276:tid 18548] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:17:21.128233 2019] [proxy:error] [pid 14276:tid 18548] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:17:21.128233 2019] [proxy_http:error] [pid 14276:tid 18548] [client 201.245.192.253:38286] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:26:58.625647 2019] [proxy:error] [pid 14276:tid 18392] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:26:58.625647 2019] [proxy:error] [pid 14276:tid 18392] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:26:58.625647 2019] [proxy_http:error] [pid 14276:tid 18392] [client 201.245.192.253:41992] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:26:59.967249 2019] [proxy:error] [pid 14276:tid 18548] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:26:59.967249 2019] [proxy_http:error] [pid 14276:tid 18548] [client 201.245.192.253:38296] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:27:21.011686 2019] [proxy:error] [pid 14276:tid 18548] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:27:21.011686 2019] [proxy:error] [pid 14276:tid 18548] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:27:21.011686 2019] [proxy_http:error] [pid 14276:tid 18548] [client 201.245.192.253:38298] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:36:59.101902 2019] [proxy:error] [pid 14276:tid 18920] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:36:59.101902 2019] [proxy:error] [pid 14276:tid 18920] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:36:59.101902 2019] [proxy_http:error] [pid 14276:tid 18920] [client 201.245.192.253:41998] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:36:59.694703 2019] [proxy:error] [pid 14276:tid 18412] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:36:59.694703 2019] [proxy_http:error] [pid 14276:tid 18412] [client 201.245.192.253:38308] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 10:37:20.723540 2019] [proxy:error] [pid 14276:tid 18412] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 10:37:20.723540 2019] [proxy:error] [pid 14276:tid 18412] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 10:37:20.723540 2019] [proxy_http:error] [pid 14276:tid 18412] [client 201.245.192.253:38310] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:16:58.588916 2019] [proxy:error] [pid 14276:tid 18264] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:16:58.588916 2019] [proxy:error] [pid 14276:tid 18264] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:16:58.588916 2019] [proxy_http:error] [pid 14276:tid 18264] [client 201.245.192.253:42076] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:16:59.103717 2019] [proxy:error] [pid 14276:tid 18044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:16:59.103717 2019] [proxy_http:error] [pid 14276:tid 18044] [client 201.245.192.253:38340] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:17:20.116954 2019] [proxy:error] [pid 14276:tid 18044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:17:20.116954 2019] [proxy:error] [pid 14276:tid 18044] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:17:20.116954 2019] [proxy_http:error] [pid 14276:tid 18044] [client 201.245.192.253:38342] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:26:59.002771 2019] [proxy:error] [pid 14276:tid 18996] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:26:59.002771 2019] [proxy:error] [pid 14276:tid 18996] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:26:59.002771 2019] [proxy_http:error] [pid 14276:tid 18996] [client 201.245.192.253:42082] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:26:59.829572 2019] [proxy:error] [pid 14276:tid 18256] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:26:59.829572 2019] [proxy_http:error] [pid 14276:tid 18256] [client 201.245.192.253:38364] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:27:20.858409 2019] [proxy:error] [pid 14276:tid 18256] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:27:20.858409 2019] [proxy:error] [pid 14276:tid 18256] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:27:20.858409 2019] [proxy_http:error] [pid 14276:tid 18256] [client 201.245.192.253:38374] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:34:09.345127 2019] [core:error] [pid 14276:tid 18096] (20024)The given path is misformatted or contained invalid characters: [client 52.36.251.200:9494] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file, referer: http://dama.gov.co [Sun Nov 03 11:34:09.501127 2019] [core:error] [pid 14276:tid 18096] (20024)The given path is misformatted or contained invalid characters: [client 52.36.251.200:9494] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Sun Nov 03 11:36:58.387023 2019] [proxy:error] [pid 14276:tid 18876] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:36:58.387023 2019] [proxy:error] [pid 14276:tid 18876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:36:58.387023 2019] [proxy_http:error] [pid 14276:tid 18876] [client 201.245.192.253:42088] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:36:59.572626 2019] [proxy:error] [pid 14276:tid 18104] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:36:59.572626 2019] [proxy_http:error] [pid 14276:tid 18104] [client 201.245.192.253:38386] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 11:37:20.617062 2019] [proxy:error] [pid 14276:tid 18104] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 11:37:20.617062 2019] [proxy:error] [pid 14276:tid 18104] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 11:37:20.617062 2019] [proxy_http:error] [pid 14276:tid 18104] [client 201.245.192.253:38390] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:16:58.950440 2019] [proxy:error] [pid 14276:tid 19080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:16:58.950440 2019] [proxy:error] [pid 14276:tid 19080] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:16:58.950440 2019] [proxy_http:error] [pid 14276:tid 19080] [client 201.245.192.253:42142] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:16:59.012840 2019] [proxy:error] [pid 14276:tid 18772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:16:59.012840 2019] [proxy_http:error] [pid 14276:tid 18772] [client 201.245.192.253:38424] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:17:20.057277 2019] [proxy:error] [pid 14276:tid 18772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:17:20.057277 2019] [proxy:error] [pid 14276:tid 18772] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:17:20.057277 2019] [proxy_http:error] [pid 14276:tid 18772] [client 201.245.192.253:38428] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:26:58.334693 2019] [proxy:error] [pid 14276:tid 18140] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:26:58.334693 2019] [proxy:error] [pid 14276:tid 18140] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:26:58.334693 2019] [proxy_http:error] [pid 14276:tid 18140] [client 201.245.192.253:42172] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:26:59.738695 2019] [proxy:error] [pid 14276:tid 18524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:26:59.738695 2019] [proxy_http:error] [pid 14276:tid 18524] [client 201.245.192.253:38436] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:27:20.767532 2019] [proxy:error] [pid 14276:tid 18524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:27:20.767532 2019] [proxy:error] [pid 14276:tid 18524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:27:20.767532 2019] [proxy_http:error] [pid 14276:tid 18524] [client 201.245.192.253:38440] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:30:41.758285 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 12:36:58.857747 2019] [proxy:error] [pid 14276:tid 18600] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:36:58.857747 2019] [proxy:error] [pid 14276:tid 18600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:36:58.857747 2019] [proxy_http:error] [pid 14276:tid 18600] [client 201.245.192.253:42178] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:36:59.512948 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:36:59.512948 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:38448] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 12:37:20.541785 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 12:37:20.541785 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 12:37:20.541785 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:38452] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:16:58.375962 2019] [proxy:error] [pid 14276:tid 18532] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:16:58.375962 2019] [proxy:error] [pid 14276:tid 18532] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:16:58.375962 2019] [proxy_http:error] [pid 14276:tid 18532] [client 201.245.192.253:42242] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:16:59.077963 2019] [proxy:error] [pid 14276:tid 18724] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:16:59.077963 2019] [proxy_http:error] [pid 14276:tid 18724] [client 201.245.192.253:38480] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:17:20.106800 2019] [proxy:error] [pid 14276:tid 18724] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:17:20.106800 2019] [proxy:error] [pid 14276:tid 18724] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:17:20.106800 2019] [proxy_http:error] [pid 14276:tid 18724] [client 201.245.192.253:38484] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:18:04.395278 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 13:26:58.789816 2019] [proxy:error] [pid 14276:tid 17980] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:26:58.789816 2019] [proxy:error] [pid 14276:tid 17980] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:26:58.789816 2019] [proxy_http:error] [pid 14276:tid 17980] [client 201.245.192.253:38492] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:26:58.789816 2019] [proxy:error] [pid 14276:tid 17980] AH00940: HTTP: disabled connection for (172.22.1.16) [Sun Nov 03 13:26:58.805416 2019] [proxy:error] [pid 14276:tid 18148] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:26:58.805416 2019] [proxy_http:error] [pid 14276:tid 18148] [client 201.245.192.253:42248] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:35:16.165490 2019] [proxy:error] [pid 14276:tid 18960] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:35:16.165490 2019] [proxy:error] [pid 14276:tid 18960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:35:16.165490 2019] [proxy_http:error] [pid 14276:tid 18960] [client 179.18.24.24:63027] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 13:35:24.215104 2019] [proxy:error] [pid 14276:tid 18008] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:35:24.215104 2019] [proxy_http:error] [pid 14276:tid 18008] [client 179.18.24.24:62992] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 13:36:58.252069 2019] [proxy:error] [pid 14276:tid 18960] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:36:58.252069 2019] [proxy:error] [pid 14276:tid 18960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:36:58.252069 2019] [proxy_http:error] [pid 14276:tid 18960] [client 201.245.192.253:42254] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:36:59.078871 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:36:59.078871 2019] [proxy_http:error] [pid 14276:tid 18852] [client 201.245.192.253:38504] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:37:20.107708 2019] [proxy:error] [pid 14276:tid 18852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 13:37:20.107708 2019] [proxy:error] [pid 14276:tid 18852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 13:37:20.107708 2019] [proxy_http:error] [pid 14276:tid 18852] [client 201.245.192.253:38508] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 13:53:16.545388 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 14:12:00.215361 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 14:12:00.527362 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 14:16:57.817084 2019] [proxy:error] [pid 14276:tid 18096] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:16:57.817084 2019] [proxy:error] [pid 14276:tid 18096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:16:57.817084 2019] [proxy_http:error] [pid 14276:tid 18096] [client 201.245.192.253:42286] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:16:58.659485 2019] [proxy:error] [pid 14276:tid 18956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:16:58.659485 2019] [proxy_http:error] [pid 14276:tid 18956] [client 201.245.192.253:38538] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:17:19.703922 2019] [proxy:error] [pid 14276:tid 18956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:17:19.703922 2019] [proxy:error] [pid 14276:tid 18956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:17:19.703922 2019] [proxy_http:error] [pid 14276:tid 18956] [client 201.245.192.253:38542] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:26:58.246539 2019] [proxy:error] [pid 14276:tid 18564] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:26:58.246539 2019] [proxy:error] [pid 14276:tid 18564] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:26:58.246539 2019] [proxy_http:error] [pid 14276:tid 18564] [client 201.245.192.253:42304] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:26:59.213740 2019] [proxy:error] [pid 14276:tid 18124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:26:59.213740 2019] [proxy_http:error] [pid 14276:tid 18124] [client 201.245.192.253:38764] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:27:20.242577 2019] [proxy:error] [pid 14276:tid 18124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:27:20.242577 2019] [proxy:error] [pid 14276:tid 18124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:27:20.242577 2019] [proxy_http:error] [pid 14276:tid 18124] [client 201.245.192.253:38766] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:36:58.691593 2019] [proxy:error] [pid 14276:tid 18772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:36:58.691593 2019] [proxy:error] [pid 14276:tid 18772] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:36:58.691593 2019] [proxy_http:error] [pid 14276:tid 18772] [client 201.245.192.253:42312] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:36:58.941194 2019] [proxy:error] [pid 14276:tid 18424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:36:58.941194 2019] [proxy_http:error] [pid 14276:tid 18424] [client 201.245.192.253:38776] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 14:37:19.970031 2019] [proxy:error] [pid 14276:tid 18424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 14:37:19.970031 2019] [proxy:error] [pid 14276:tid 18424] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 14:37:19.970031 2019] [proxy_http:error] [pid 14276:tid 18424] [client 201.245.192.253:38780] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 15:14:34.377555 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 16:01:31.867304 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 16:17:00.614935 2019] [proxy:error] [pid 14276:tid 18412] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 16:17:00.614935 2019] [proxy:error] [pid 14276:tid 18412] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 16:17:00.614935 2019] [proxy_http:error] [pid 14276:tid 18412] [client 201.245.192.253:54602] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 16:26:59.921188 2019] [proxy:error] [pid 14276:tid 17968] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 16:26:59.921188 2019] [proxy:error] [pid 14276:tid 17968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 16:26:59.921188 2019] [proxy_http:error] [pid 14276:tid 17968] [client 201.245.192.253:54612] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 16:37:00.381842 2019] [proxy:error] [pid 14276:tid 18408] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 16:37:00.381842 2019] [proxy:error] [pid 14276:tid 18408] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 16:37:00.381842 2019] [proxy_http:error] [pid 14276:tid 18408] [client 201.245.192.253:54618] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 16:39:42.980928 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:16:59.868857 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 17:16:59.868857 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 17:16:59.868857 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:54714] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 17:27:00.157911 2019] [proxy:error] [pid 14276:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 17:27:00.157911 2019] [proxy:error] [pid 14276:tid 18080] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 17:27:00.157911 2019] [proxy_http:error] [pid 14276:tid 18080] [client 201.245.192.253:54740] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 17:29:27.546970 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:36:59.542164 2019] [proxy:error] [pid 14276:tid 18360] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 17:36:59.542164 2019] [proxy:error] [pid 14276:tid 18360] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 17:36:59.542164 2019] [proxy_http:error] [pid 14276:tid 18360] [client 201.245.192.253:54750] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 17:43:37.374063 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:43:37.374063 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:43:58.387300 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:43:58.387300 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:43:58.387300 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:50:58.293237 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:50:58.293237 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 17:50:58.308837 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:17:00.043180 2019] [proxy:error] [pid 14276:tid 18376] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 18:17:00.043180 2019] [proxy:error] [pid 14276:tid 18376] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 18:17:00.043180 2019] [proxy_http:error] [pid 14276:tid 18376] [client 201.245.192.253:54894] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 18:26:59.302633 2019] [proxy:error] [pid 14276:tid 19124] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 18:26:59.302633 2019] [proxy:error] [pid 14276:tid 19124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 18:26:59.302633 2019] [proxy_http:error] [pid 14276:tid 19124] [client 201.245.192.253:54966] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.709449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.725049 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.725049 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.740649 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:08.771849 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:09.442650 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:09.458250 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:09.489451 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:09.489451 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:09.489451 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:30.955088 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:30.955088 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:30.955088 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:27:30.955088 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:31.759406 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:32.009006 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:30:32.024606 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:33:38.023733 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:33:38.117333 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:33:38.678934 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:33:38.694534 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.368600 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.368600 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.415400 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.602601 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.602601 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.602601 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:16.633801 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:44.105449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:44.105449 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:44.620250 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:44.620250 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:34:44.620250 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:36:59.654087 2019] [proxy:error] [pid 14276:tid 18436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 18:36:59.654087 2019] [proxy:error] [pid 14276:tid 18436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 18:36:59.654087 2019] [proxy_http:error] [pid 14276:tid 18436] [client 201.245.192.253:54986] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 18:51:47.748047 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 18:51:47.748047 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:16:59.078701 2019] [proxy:error] [pid 14276:tid 19020] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 19:16:59.078701 2019] [proxy:error] [pid 14276:tid 19020] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 19:16:59.078701 2019] [proxy_http:error] [pid 14276:tid 19020] [client 201.245.192.253:55084] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 19:26:35.234513 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.234513 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.234513 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.250113 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.250113 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.265714 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:35.265714 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 19:26:59.570556 2019] [proxy:error] [pid 14276:tid 18272] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 19:26:59.570556 2019] [proxy:error] [pid 14276:tid 18272] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 19:26:59.570556 2019] [proxy_http:error] [pid 14276:tid 18272] [client 201.245.192.253:55112] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 19:36:59.812810 2019] [proxy:error] [pid 14276:tid 19036] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 19:36:59.812810 2019] [proxy:error] [pid 14276:tid 19036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 19:36:59.812810 2019] [proxy_http:error] [pid 14276:tid 19036] [client 201.245.192.253:55136] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 19:53:36.186561 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 20:16:59.253025 2019] [proxy:error] [pid 14276:tid 18632] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 20:16:59.253025 2019] [proxy:error] [pid 14276:tid 18632] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 20:16:59.253025 2019] [proxy_http:error] [pid 14276:tid 18632] [client 201.245.192.253:55210] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 20:21:12.893870 2019] [proxy:error] [pid 14276:tid 17952] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 20:21:12.893870 2019] [proxy:error] [pid 14276:tid 17952] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 20:21:12.893870 2019] [proxy_http:error] [pid 14276:tid 17952] [client 181.53.12.41:42771] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 20:21:13.065471 2019] [proxy:error] [pid 14276:tid 18828] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 20:21:13.065471 2019] [proxy_http:error] [pid 14276:tid 18828] [client 181.53.12.41:42776] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Nov 03 20:26:59.698079 2019] [proxy:error] [pid 14276:tid 18448] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 20:26:59.698079 2019] [proxy:error] [pid 14276:tid 18448] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 20:26:59.698079 2019] [proxy_http:error] [pid 14276:tid 18448] [client 201.245.192.253:55220] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 20:27:38.916548 2019] [cgi:error] [pid 14276:tid 18352] [client 59.126.0.174:40776] script not found or unable to stat: E:/nuevo/htdocs/setup.cgi [Sun Nov 03 20:31:20.873738 2019] [core:error] [pid 14276:tid 18960] (20024)The given path is misformatted or contained invalid characters: [client 54.36.150.117:46074] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Sun Nov 03 20:36:58.988732 2019] [proxy:error] [pid 14276:tid 18796] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 20:36:58.988732 2019] [proxy:error] [pid 14276:tid 18796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 20:36:58.988732 2019] [proxy_http:error] [pid 14276:tid 18796] [client 201.245.192.253:55320] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 20:46:15.160909 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 21:16:59.505348 2019] [proxy:error] [pid 14276:tid 18264] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 21:16:59.505348 2019] [proxy:error] [pid 14276:tid 18264] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 21:16:59.505348 2019] [proxy_http:error] [pid 14276:tid 18264] [client 201.245.192.253:55418] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 21:26:58.842801 2019] [proxy:error] [pid 14276:tid 18272] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 21:26:58.842801 2019] [proxy:error] [pid 14276:tid 18272] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 21:26:58.842801 2019] [proxy_http:error] [pid 14276:tid 18272] [client 201.245.192.253:55446] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 21:36:59.303456 2019] [proxy:error] [pid 14276:tid 18488] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 21:36:59.303456 2019] [proxy:error] [pid 14276:tid 18488] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 21:36:59.303456 2019] [proxy_http:error] [pid 14276:tid 18488] [client 201.245.192.253:55476] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 21:39:35.646930 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 21:52:06.881850 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 22:06:23.604155 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 22:16:58.728070 2019] [proxy:error] [pid 14276:tid 18612] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 22:16:58.728070 2019] [proxy:error] [pid 14276:tid 18612] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 22:16:58.728070 2019] [proxy_http:error] [pid 14276:tid 18612] [client 201.245.192.253:55532] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 22:26:59.126325 2019] [proxy:error] [pid 14276:tid 18960] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 22:26:59.126325 2019] [proxy:error] [pid 14276:tid 18960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 22:26:59.126325 2019] [proxy_http:error] [pid 14276:tid 18960] [client 201.245.192.253:55540] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 22:36:58.541777 2019] [proxy:error] [pid 14276:tid 18216] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 22:36:58.541777 2019] [proxy:error] [pid 14276:tid 18216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 22:36:58.541777 2019] [proxy_http:error] [pid 14276:tid 18216] [client 201.245.192.253:55548] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 22:51:21.972094 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 23:06:30.439690 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Nov 03 23:16:59.198794 2019] [proxy:error] [pid 14276:tid 18960] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 23:16:59.198794 2019] [proxy:error] [pid 14276:tid 18960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 23:16:59.198794 2019] [proxy_http:error] [pid 14276:tid 18960] [client 201.245.192.253:55618] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 23:26:58.551847 2019] [proxy:error] [pid 14276:tid 18564] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 23:26:58.551847 2019] [proxy:error] [pid 14276:tid 18564] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 23:26:58.551847 2019] [proxy_http:error] [pid 14276:tid 18564] [client 201.245.192.253:55624] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 23:36:58.887701 2019] [proxy:error] [pid 14276:tid 18564] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed [Sun Nov 03 23:36:58.887701 2019] [proxy:error] [pid 14276:tid 18564] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Sun Nov 03 23:36:58.887701 2019] [proxy_http:error] [pid 14276:tid 18564] [client 201.245.192.253:55630] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Sun Nov 03 23:42:22.541470 2019] [mpm_winnt:warn] [pid 14276:tid 19920] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0312 ]-- |