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: [Mon Mar 29 00:01:40.423934 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 00:01:40.423934 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:01:40.423934 2021] [proxy_http:error] [pid 7396:tid 20828] [client 201.245.192.253:49276] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:01:40.626735 2021] [proxy:error] [pid 7396:tid 20828] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 00:01:40.798335 2021] [proxy:error] [pid 7396:tid 20600] (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 [Mon Mar 29 00:01:40.798335 2021] [proxy_http:error] [pid 7396:tid 20600] [client 201.245.192.253:52014] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:03:38.609742 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 00:03:38.609742 2021] [proxy:error] [pid 7396:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:03:38.609742 2021] [proxy_http:error] [pid 7396:tid 20680] [client 201.245.192.253:43089] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:11:40.198188 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 00:11:40.198188 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:11:40.198188 2021] [proxy_http:error] [pid 7396:tid 20084] [client 201.245.192.253:52020] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:11:40.697389 2021] [proxy:error] [pid 7396:tid 20176] (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 [Mon Mar 29 00:11:40.697389 2021] [proxy_http:error] [pid 7396:tid 20176] [client 201.245.192.253:49312] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:12:01.929026 2021] [proxy:error] [pid 7396:tid 20176] (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 [Mon Mar 29 00:12:01.929026 2021] [proxy:error] [pid 7396:tid 20176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:12:01.929026 2021] [proxy_http:error] [pid 7396:tid 20176] [client 201.245.192.253:49314] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:16:20.405880 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 00:21:40.658842 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 00:21:40.658842 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:21:40.658842 2021] [proxy_http:error] [pid 7396:tid 20828] [client 201.245.192.253:52026] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:21:41.033243 2021] [proxy:error] [pid 7396:tid 20704] (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 [Mon Mar 29 00:21:41.033243 2021] [proxy_http:error] [pid 7396:tid 20704] [client 201.245.192.253:49344] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:22:02.280480 2021] [proxy:error] [pid 7396:tid 20704] (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 [Mon Mar 29 00:22:02.280480 2021] [proxy:error] [pid 7396:tid 20704] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:22:02.280480 2021] [proxy_http:error] [pid 7396:tid 20704] [client 201.245.192.253:49346] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:23:39.999052 2021] [proxy:error] [pid 7396:tid 20632] (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 [Mon Mar 29 00:23:39.999052 2021] [proxy:error] [pid 7396:tid 20632] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:23:39.999052 2021] [proxy_http:error] [pid 7396:tid 20632] [client 201.245.192.253:39709] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:41:20.832115 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 00:43:38.580357 2021] [proxy:error] [pid 7396:tid 19956] (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 [Mon Mar 29 00:43:38.580357 2021] [proxy:error] [pid 7396:tid 19956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 00:43:38.580357 2021] [proxy_http:error] [pid 7396:tid 19956] [client 201.245.192.253:51825] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 00:57:18.252597 2021] [proxy:error] [pid 7396:tid 20960] (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 [Mon Mar 29 00:57:18.252597 2021] [proxy:error] [pid 7396:tid 20960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Mon Mar 29 00:57:18.252597 2021] [proxy_http:error] [pid 7396:tid 20960] [client 152.61.128.50:37633] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Mon Mar 29 00:57:18.486597 2021] [proxy:error] [pid 7396:tid 20960] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 00:57:18.704998 2021] [proxy:error] [pid 7396:tid 20960] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 01:01:40.411057 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 01:01:40.411057 2021] [proxy:error] [pid 7396:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:01:40.411057 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:52032] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:01:40.769858 2021] [proxy:error] [pid 7396:tid 20600] (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 [Mon Mar 29 01:01:40.769858 2021] [proxy_http:error] [pid 7396:tid 20600] [client 201.245.192.253:49456] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:02:02.001495 2021] [proxy:error] [pid 7396:tid 20600] (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 [Mon Mar 29 01:02:02.001495 2021] [proxy:error] [pid 7396:tid 20600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:02:02.001495 2021] [proxy_http:error] [pid 7396:tid 20600] [client 201.245.192.253:49458] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:03:40.640468 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 01:03:40.640468 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:03:40.640468 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:47481] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:11:40.871712 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 01:11:40.871712 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:11:40.871712 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:52038] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:11:40.902912 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 01:11:40.902912 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:49492] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:12:02.150149 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 01:12:02.150149 2021] [proxy:error] [pid 7396:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:12:02.150149 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:49494] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:21:40.099964 2021] [proxy:error] [pid 7396:tid 20276] (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 [Mon Mar 29 01:21:40.099964 2021] [proxy:error] [pid 7396:tid 20276] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:21:40.099964 2021] [proxy_http:error] [pid 7396:tid 20276] [client 201.245.192.253:49522] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:21:40.302765 2021] [proxy:error] [pid 7396:tid 20276] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 01:21:40.333965 2021] [proxy:error] [pid 7396:tid 20504] (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 [Mon Mar 29 01:21:40.333965 2021] [proxy_http:error] [pid 7396:tid 20504] [client 201.245.192.253:52044] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:23:15.260132 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 01:23:40.656976 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 01:23:40.656976 2021] [proxy:error] [pid 7396:tid 19836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:23:40.656976 2021] [proxy_http:error] [pid 7396:tid 19836] [client 201.245.192.253:47421] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:25:51.447606 2021] [proxy:error] [pid 7396:tid 21032] (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 [Mon Mar 29 01:25:51.447606 2021] [proxy:error] [pid 7396:tid 21032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Mon Mar 29 01:25:51.447606 2021] [proxy_http:error] [pid 7396:tid 21032] [client 152.61.192.232:45157] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Mon Mar 29 01:25:51.681606 2021] [proxy:error] [pid 7396:tid 21032] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 01:25:51.915607 2021] [proxy:error] [pid 7396:tid 21032] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 01:43:39.175881 2021] [proxy:error] [pid 7396:tid 20028] (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 [Mon Mar 29 01:43:39.175881 2021] [proxy:error] [pid 7396:tid 20028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:43:39.175881 2021] [proxy_http:error] [pid 7396:tid 20028] [client 201.245.192.253:54205] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 01:53:37.858133 2021] [proxy:error] [pid 7396:tid 20028] (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 [Mon Mar 29 01:53:37.858133 2021] [proxy:error] [pid 7396:tid 20028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 01:53:37.858133 2021] [proxy_http:error] [pid 7396:tid 20028] [client 201.245.192.253:54457] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:01:40.164180 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 02:01:40.164180 2021] [proxy:error] [pid 7396:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:01:40.164180 2021] [proxy_http:error] [pid 7396:tid 20680] [client 201.245.192.253:52050] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:01:40.288980 2021] [proxy:error] [pid 7396:tid 20036] (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 [Mon Mar 29 02:01:40.288980 2021] [proxy_http:error] [pid 7396:tid 20036] [client 201.245.192.253:49632] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:02:01.520617 2021] [proxy:error] [pid 7396:tid 20036] (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 [Mon Mar 29 02:02:01.520617 2021] [proxy:error] [pid 7396:tid 20036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:02:01.520617 2021] [proxy_http:error] [pid 7396:tid 20036] [client 201.245.192.253:49636] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:03:39.488789 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 02:03:39.488789 2021] [proxy:error] [pid 7396:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:03:39.488789 2021] [proxy_http:error] [pid 7396:tid 20680] [client 201.245.192.253:35343] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:05:08.845746 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 02:11:40.312834 2021] [proxy:error] [pid 7396:tid 20876] (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 [Mon Mar 29 02:11:40.312834 2021] [proxy:error] [pid 7396:tid 20876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:11:40.312834 2021] [proxy_http:error] [pid 7396:tid 20876] [client 201.245.192.253:49668] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:11:40.515634 2021] [proxy:error] [pid 7396:tid 20876] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 02:11:40.624835 2021] [proxy:error] [pid 7396:tid 20504] (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 [Mon Mar 29 02:11:40.624835 2021] [proxy_http:error] [pid 7396:tid 20504] [client 201.245.192.253:52056] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:21:39.790687 2021] [proxy:error] [pid 7396:tid 20356] (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 [Mon Mar 29 02:21:39.790687 2021] [proxy:error] [pid 7396:tid 20356] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:21:39.790687 2021] [proxy_http:error] [pid 7396:tid 20356] [client 201.245.192.253:49718] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:21:39.993487 2021] [proxy:error] [pid 7396:tid 20356] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 02:21:40.149488 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 02:21:40.149488 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:52062] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:23:40.238498 2021] [proxy:error] [pid 7396:tid 20356] (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 [Mon Mar 29 02:23:40.238498 2021] [proxy:error] [pid 7396:tid 20356] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:23:40.238498 2021] [proxy_http:error] [pid 7396:tid 20356] [client 201.245.192.253:35217] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:28:56.856655 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 02:33:38.764750 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 02:33:38.764750 2021] [proxy:error] [pid 7396:tid 20476] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:33:38.764750 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:58661] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:43:38.398603 2021] [proxy:error] [pid 7396:tid 20720] (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 [Mon Mar 29 02:43:38.398603 2021] [proxy:error] [pid 7396:tid 20720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:43:38.398603 2021] [proxy_http:error] [pid 7396:tid 20720] [client 201.245.192.253:33863] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 02:53:37.299255 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 02:53:37.299255 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 02:53:37.299255 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:37371] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:01:39.839302 2021] [proxy:error] [pid 7396:tid 19956] (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 [Mon Mar 29 03:01:39.839302 2021] [proxy:error] [pid 7396:tid 19956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:01:39.839302 2021] [proxy_http:error] [pid 7396:tid 19956] [client 201.245.192.253:52070] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:01:40.603704 2021] [proxy:error] [pid 7396:tid 19876] (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 [Mon Mar 29 03:01:40.603704 2021] [proxy_http:error] [pid 7396:tid 19876] [client 201.245.192.253:49844] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:02:01.866541 2021] [proxy:error] [pid 7396:tid 19876] (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 [Mon Mar 29 03:02:01.866541 2021] [proxy:error] [pid 7396:tid 19876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:02:01.866541 2021] [proxy_http:error] [pid 7396:tid 19876] [client 201.245.192.253:49846] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:03:39.039112 2021] [proxy:error] [pid 7396:tid 20960] (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 [Mon Mar 29 03:03:39.039112 2021] [proxy:error] [pid 7396:tid 20960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:03:39.039112 2021] [proxy_http:error] [pid 7396:tid 20960] [client 201.245.192.253:38437] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:11:39.769556 2021] [proxy:error] [pid 7396:tid 20060] (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 [Mon Mar 29 03:11:39.769556 2021] [proxy:error] [pid 7396:tid 20060] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:11:39.769556 2021] [proxy_http:error] [pid 7396:tid 20060] [client 201.245.192.253:49882] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:11:39.972356 2021] [proxy:error] [pid 7396:tid 20060] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 03:11:40.284357 2021] [proxy:error] [pid 7396:tid 20264] (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 [Mon Mar 29 03:11:40.284357 2021] [proxy_http:error] [pid 7396:tid 20264] [client 201.245.192.253:52076] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:21:39.731010 2021] [proxy:error] [pid 7396:tid 20100] (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 [Mon Mar 29 03:21:39.731010 2021] [proxy:error] [pid 7396:tid 20100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:21:39.731010 2021] [proxy_http:error] [pid 7396:tid 20100] [client 201.245.192.253:52082] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:21:40.245811 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 03:21:40.245811 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:49914] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:22:01.477448 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 03:22:01.477448 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:22:01.477448 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:49916] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:23:37.433217 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 03:23:37.433217 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:23:37.433217 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:49905] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:33:38.361872 2021] [proxy:error] [pid 7396:tid 19964] (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 [Mon Mar 29 03:33:38.361872 2021] [proxy:error] [pid 7396:tid 19964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:33:38.361872 2021] [proxy_http:error] [pid 7396:tid 19964] [client 201.245.192.253:53623] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 03:52:36.461871 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 03:53:38.409580 2021] [proxy:error] [pid 7396:tid 20664] (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 [Mon Mar 29 03:53:38.409580 2021] [proxy:error] [pid 7396:tid 20664] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 03:53:38.409580 2021] [proxy_http:error] [pid 7396:tid 20664] [client 201.245.192.253:37337] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:01:39.530025 2021] [proxy:error] [pid 7396:tid 20704] (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 [Mon Mar 29 04:01:39.530025 2021] [proxy:error] [pid 7396:tid 20704] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:01:39.530025 2021] [proxy_http:error] [pid 7396:tid 20704] [client 201.245.192.253:50138] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:01:39.561225 2021] [proxy:error] [pid 7396:tid 20696] (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 [Mon Mar 29 04:01:39.561225 2021] [proxy_http:error] [pid 7396:tid 20696] [client 201.245.192.253:52088] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:02:00.761662 2021] [proxy:error] [pid 7396:tid 20704] (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 [Mon Mar 29 04:02:00.761662 2021] [proxy:error] [pid 7396:tid 20704] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:02:00.761662 2021] [proxy_http:error] [pid 7396:tid 20704] [client 201.245.192.253:50140] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:03:37.871833 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 04:03:37.871833 2021] [proxy:error] [pid 7396:tid 19972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:03:37.871833 2021] [proxy_http:error] [pid 7396:tid 19972] [client 201.245.192.253:56431] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:11:39.912679 2021] [proxy:error] [pid 7396:tid 20188] (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 [Mon Mar 29 04:11:39.912679 2021] [proxy:error] [pid 7396:tid 20188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:11:39.912679 2021] [proxy_http:error] [pid 7396:tid 20188] [client 201.245.192.253:50200] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:11:40.068680 2021] [proxy:error] [pid 7396:tid 19548] (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 [Mon Mar 29 04:11:40.068680 2021] [proxy_http:error] [pid 7396:tid 19548] [client 201.245.192.253:52094] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:12:01.144317 2021] [proxy:error] [pid 7396:tid 20188] (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 [Mon Mar 29 04:12:01.144317 2021] [proxy:error] [pid 7396:tid 20188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:12:01.144317 2021] [proxy_http:error] [pid 7396:tid 20188] [client 201.245.192.253:50202] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:21:39.624533 2021] [proxy:error] [pid 7396:tid 19996] (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 [Mon Mar 29 04:21:39.624533 2021] [proxy:error] [pid 7396:tid 19996] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:21:39.624533 2021] [proxy_http:error] [pid 7396:tid 19996] [client 201.245.192.253:52100] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:21:40.045733 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 04:21:40.045733 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:50304] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:22:01.277371 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 04:22:01.277371 2021] [proxy:error] [pid 7396:tid 20476] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:22:01.277371 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:50308] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:23:37.123939 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 04:23:37.123939 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:23:37.123939 2021] [proxy_http:error] [pid 7396:tid 20084] [client 201.245.192.253:40741] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:33:38.395795 2021] [proxy:error] [pid 7396:tid 20100] (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 [Mon Mar 29 04:33:38.395795 2021] [proxy:error] [pid 7396:tid 20100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:33:38.395795 2021] [proxy_http:error] [pid 7396:tid 20100] [client 201.245.192.253:37469] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 04:34:05.820643 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 04:43:38.341649 2021] [proxy:error] [pid 7396:tid 20600] (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 [Mon Mar 29 04:43:38.341649 2021] [proxy:error] [pid 7396:tid 20600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 04:43:38.341649 2021] [proxy_http:error] [pid 7396:tid 20600] [client 201.245.192.253:43873] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:01:39.501548 2021] [proxy:error] [pid 7396:tid 20520] (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 [Mon Mar 29 05:01:39.501548 2021] [proxy:error] [pid 7396:tid 20520] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:01:39.501548 2021] [proxy_http:error] [pid 7396:tid 20520] [client 201.245.192.253:52106] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:01:39.969549 2021] [proxy:error] [pid 7396:tid 20060] (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 [Mon Mar 29 05:01:39.969549 2021] [proxy_http:error] [pid 7396:tid 20060] [client 201.245.192.253:50464] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:02:01.201186 2021] [proxy:error] [pid 7396:tid 20060] (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 [Mon Mar 29 05:02:01.201186 2021] [proxy:error] [pid 7396:tid 20060] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:02:01.201186 2021] [proxy_http:error] [pid 7396:tid 20060] [client 201.245.192.253:50468] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:03:37.812156 2021] [proxy:error] [pid 7396:tid 20300] (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 [Mon Mar 29 05:03:37.812156 2021] [proxy:error] [pid 7396:tid 20300] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:03:37.812156 2021] [proxy_http:error] [pid 7396:tid 20300] [client 201.245.192.253:56191] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:04:43.394671 2021] [proxy:error] [pid 7396:tid 19752] (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 [Mon Mar 29 05:04:43.394671 2021] [proxy:error] [pid 7396:tid 19752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:04:43.394671 2021] [proxy_http:error] [pid 7396:tid 19752] [client 190.159.104.119:55416] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:06:59.130509 2021] [proxy:error] [pid 7396:tid 20944] (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 [Mon Mar 29 05:06:59.130509 2021] [proxy:error] [pid 7396:tid 20944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:06:59.130509 2021] [proxy_http:error] [pid 7396:tid 20944] [client 190.159.104.119:55674] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 05:11:39.946603 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 05:11:39.946603 2021] [proxy:error] [pid 7396:tid 19836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:11:39.946603 2021] [proxy_http:error] [pid 7396:tid 19836] [client 201.245.192.253:50514] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:11:39.993403 2021] [proxy:error] [pid 7396:tid 21032] (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 [Mon Mar 29 05:11:39.993403 2021] [proxy_http:error] [pid 7396:tid 21032] [client 201.245.192.253:52112] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:12:01.178240 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 05:12:01.178240 2021] [proxy:error] [pid 7396:tid 19836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:12:01.178240 2021] [proxy_http:error] [pid 7396:tid 19836] [client 201.245.192.253:50516] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:12:31.972694 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 05:15:17.239384 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 05:15:17.239384 2021] [proxy:error] [pid 7396:tid 19720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:15:17.239384 2021] [proxy_http:error] [pid 7396:tid 19720] [client 190.159.104.119:56062] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 05:15:19.173788 2021] [proxy:error] [pid 7396:tid 19720] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 05:21:39.237255 2021] [proxy:error] [pid 7396:tid 19868] (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 [Mon Mar 29 05:21:39.237255 2021] [proxy:error] [pid 7396:tid 19868] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:21:39.237255 2021] [proxy_http:error] [pid 7396:tid 19868] [client 201.245.192.253:50556] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:21:39.440055 2021] [proxy:error] [pid 7396:tid 19868] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 05:21:39.471256 2021] [proxy:error] [pid 7396:tid 20248] (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 [Mon Mar 29 05:21:39.471256 2021] [proxy_http:error] [pid 7396:tid 20248] [client 201.245.192.253:52118] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:23:37.953464 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 05:23:37.953464 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:23:37.953464 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:35641] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:33:38.102118 2021] [proxy:error] [pid 7396:tid 20984] (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 [Mon Mar 29 05:33:38.102118 2021] [proxy:error] [pid 7396:tid 20984] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:33:38.102118 2021] [proxy_http:error] [pid 7396:tid 20984] [client 201.245.192.253:56171] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 05:45:16.889745 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 05:53:38.181026 2021] [proxy:error] [pid 7396:tid 20028] (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 [Mon Mar 29 05:53:38.181026 2021] [proxy:error] [pid 7396:tid 20028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 05:53:38.181026 2021] [proxy_http:error] [pid 7396:tid 20028] [client 201.245.192.253:56373] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:01:39.285871 2021] [proxy:error] [pid 7396:tid 20076] (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 [Mon Mar 29 06:01:39.285871 2021] [proxy:error] [pid 7396:tid 20076] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:01:39.285871 2021] [proxy_http:error] [pid 7396:tid 20076] [client 201.245.192.253:50720] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:01:39.473071 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 06:01:39.473071 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:52124] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:02:00.533108 2021] [proxy:error] [pid 7396:tid 20076] (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 [Mon Mar 29 06:02:00.533108 2021] [proxy:error] [pid 7396:tid 20076] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:02:00.533108 2021] [proxy_http:error] [pid 7396:tid 20076] [client 201.245.192.253:50724] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:11:39.013324 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 06:11:39.013324 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:11:39.013324 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:52130] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:11:39.590525 2021] [proxy:error] [pid 7396:tid 20076] (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 [Mon Mar 29 06:11:39.590525 2021] [proxy_http:error] [pid 7396:tid 20076] [client 201.245.192.253:50756] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:12:00.806562 2021] [proxy:error] [pid 7396:tid 20076] (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 [Mon Mar 29 06:12:00.806562 2021] [proxy:error] [pid 7396:tid 20076] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:12:00.806562 2021] [proxy_http:error] [pid 7396:tid 20076] [client 201.245.192.253:50760] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:13:37.557932 2021] [proxy:error] [pid 7396:tid 20188] (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 [Mon Mar 29 06:13:37.557932 2021] [proxy:error] [pid 7396:tid 20188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:13:37.557932 2021] [proxy_http:error] [pid 7396:tid 20188] [client 201.245.192.253:47435] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:21:39.536379 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 06:21:39.536379 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:21:39.536379 2021] [proxy_http:error] [pid 7396:tid 20084] [client 201.245.192.253:52136] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:21:39.739179 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 06:21:39.739179 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:50804] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:22:00.970816 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 06:22:00.970816 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:22:00.970816 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:50808] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:33:38.479241 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 06:33:38.479241 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:33:38.479241 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:60369] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:36:11.749511 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 06:43:37.192693 2021] [proxy:error] [pid 7396:tid 20960] (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 [Mon Mar 29 06:43:37.192693 2021] [proxy:error] [pid 7396:tid 20960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 06:43:37.192693 2021] [proxy_http:error] [pid 7396:tid 20960] [client 201.245.192.253:43329] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 06:44:43.290009 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 07:01:39.132593 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 07:01:39.132593 2021] [proxy:error] [pid 7396:tid 20216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:01:39.132593 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:50972] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:01:39.335394 2021] [proxy:error] [pid 7396:tid 20216] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 07:01:39.475794 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 07:01:39.475794 2021] [proxy_http:error] [pid 7396:tid 19720] [client 201.245.192.253:52142] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:03:39.190404 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 07:03:39.190404 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:03:39.190404 2021] [proxy_http:error] [pid 7396:tid 20084] [client 201.245.192.253:46911] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:11:39.000447 2021] [proxy:error] [pid 7396:tid 20952] (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 [Mon Mar 29 07:11:39.000447 2021] [proxy:error] [pid 7396:tid 20952] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:11:39.000447 2021] [proxy_http:error] [pid 7396:tid 20952] [client 201.245.192.253:52148] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:11:39.390448 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 07:11:39.390448 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:51162] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:12:00.622085 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 07:12:00.622085 2021] [proxy:error] [pid 7396:tid 20216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:12:00.622085 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:51170] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:14:15.421922 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 07:21:39.554702 2021] [proxy:error] [pid 7396:tid 20536] (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 [Mon Mar 29 07:21:39.554702 2021] [proxy:error] [pid 7396:tid 20536] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:21:39.554702 2021] [proxy_http:error] [pid 7396:tid 20536] [client 201.245.192.253:52154] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:21:39.663902 2021] [proxy:error] [pid 7396:tid 21032] (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 [Mon Mar 29 07:21:39.663902 2021] [proxy_http:error] [pid 7396:tid 21032] [client 201.245.192.253:51220] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:22:00.895539 2021] [proxy:error] [pid 7396:tid 21032] (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 [Mon Mar 29 07:22:00.895539 2021] [proxy:error] [pid 7396:tid 21032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:22:00.895539 2021] [proxy_http:error] [pid 7396:tid 21032] [client 201.245.192.253:51222] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:23:38.473711 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 07:23:38.473711 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:23:38.473711 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:52603] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:41:06.109151 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 07:41:06.109151 2021] [proxy:error] [pid 7396:tid 20860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:41:06.109151 2021] [proxy_http:error] [pid 7396:tid 20860] [client 201.245.192.253:62367] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:41:12.723562 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 07:43:37.367016 2021] [proxy:error] [pid 7396:tid 20036] (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 [Mon Mar 29 07:43:37.367016 2021] [proxy:error] [pid 7396:tid 20036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:43:37.367016 2021] [proxy_http:error] [pid 7396:tid 20036] [client 201.245.192.253:47001] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:53:04.240812 2021] [proxy:error] [pid 7396:tid 20608] (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 [Mon Mar 29 07:53:04.240812 2021] [proxy:error] [pid 7396:tid 20608] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 07:53:04.240812 2021] [proxy_http:error] [pid 7396:tid 20608] [client 186.84.22.9:32058] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:53:07.095617 2021] [proxy:error] [pid 7396:tid 20696] (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 [Mon Mar 29 07:53:07.095617 2021] [proxy_http:error] [pid 7396:tid 20696] [client 186.84.22.9:32059] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 07:53:08.671220 2021] [proxy:error] [pid 7396:tid 20664] (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 [Mon Mar 29 07:53:08.671220 2021] [proxy_http:error] [pid 7396:tid 20664] [client 186.84.22.9:32029] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:01:39.478517 2021] [proxy:error] [pid 7396:tid 19924] (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 [Mon Mar 29 08:01:39.478517 2021] [proxy:error] [pid 7396:tid 19924] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:01:39.478517 2021] [proxy_http:error] [pid 7396:tid 19924] [client 201.245.192.253:51372] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:01:39.650117 2021] [proxy:error] [pid 7396:tid 20116] (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 [Mon Mar 29 08:01:39.650117 2021] [proxy_http:error] [pid 7396:tid 20116] [client 201.245.192.253:52160] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:02:00.710154 2021] [proxy:error] [pid 7396:tid 19924] (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 [Mon Mar 29 08:02:00.710154 2021] [proxy:error] [pid 7396:tid 19924] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:02:00.710154 2021] [proxy_http:error] [pid 7396:tid 19924] [client 201.245.192.253:51374] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:03:38.132325 2021] [proxy:error] [pid 7396:tid 20460] (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 [Mon Mar 29 08:03:38.132325 2021] [proxy:error] [pid 7396:tid 20460] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:03:38.132325 2021] [proxy_http:error] [pid 7396:tid 20460] [client 201.245.192.253:47047] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:10:02.064600 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 08:10:02.064600 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:10:02.064600 2021] [proxy_http:error] [pid 7396:tid 20828] [client 181.61.202.119:52152] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:10:10.738215 2021] [proxy:error] [pid 7396:tid 19940] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 08:10:12.719419 2021] [proxy:error] [pid 7396:tid 20672] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 08:10:13.577420 2021] [proxy:error] [pid 7396:tid 19940] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 08:10:59.285500 2021] [proxy:error] [pid 7396:tid 21096] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 08:11:23.293942 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 08:11:23.293942 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:11:23.293942 2021] [proxy_http:error] [pid 7396:tid 20828] [client 181.61.202.119:52181] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:11:39.081170 2021] [proxy:error] [pid 7396:tid 19940] (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 [Mon Mar 29 08:11:39.081170 2021] [proxy_http:error] [pid 7396:tid 19940] [client 201.245.192.253:52166] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:11:39.564771 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 08:11:39.564771 2021] [proxy_http:error] [pid 7396:tid 20860] [client 201.245.192.253:51504] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:11:43.620778 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 08:11:43.620778 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:11:43.620778 2021] [proxy_http:error] [pid 7396:tid 21096] [client 181.61.202.119:52184] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:12:00.796408 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 08:12:00.796408 2021] [proxy_http:error] [pid 7396:tid 20860] [client 201.245.192.253:51506] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:14:56.499517 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 08:14:56.499517 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:14:56.499517 2021] [proxy_http:error] [pid 7396:tid 20828] [client 54.71.187.124:49240] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:56.499517 2021] [proxy:error] [pid 7396:tid 19612] (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 [Mon Mar 29 08:14:56.499517 2021] [proxy_http:error] [pid 7396:tid 19612] [client 54.71.187.124:24336] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:56.530717 2021] [proxy:error] [pid 7396:tid 20592] (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 [Mon Mar 29 08:14:56.530717 2021] [proxy_http:error] [pid 7396:tid 20592] [client 54.71.187.124:60675] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:57.575919 2021] [proxy:error] [pid 7396:tid 21036] (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 [Mon Mar 29 08:14:57.575919 2021] [proxy_http:error] [pid 7396:tid 21036] [client 52.34.76.65:2991] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:57.685119 2021] [proxy:error] [pid 7396:tid 20420] (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 [Mon Mar 29 08:14:57.685119 2021] [proxy_http:error] [pid 7396:tid 20420] [client 54.70.53.60:30976] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:57.685119 2021] [proxy:error] [pid 7396:tid 20952] (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 [Mon Mar 29 08:14:57.685119 2021] [proxy_http:error] [pid 7396:tid 20952] [client 52.34.76.65:27521] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:14:57.716319 2021] [proxy:error] [pid 7396:tid 19876] (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 [Mon Mar 29 08:14:57.716319 2021] [proxy_http:error] [pid 7396:tid 19876] [client 52.34.76.65:29151] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:15:15.983951 2021] [proxy:error] [pid 7396:tid 20616] (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 [Mon Mar 29 08:15:15.983951 2021] [proxy_http:error] [pid 7396:tid 20616] [client 54.70.53.60:11148] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:15:16.249152 2021] [proxy:error] [pid 7396:tid 19996] (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 [Mon Mar 29 08:15:16.249152 2021] [proxy_http:error] [pid 7396:tid 19996] [client 54.70.53.60:59821] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:17:34.746195 2021] [proxy:error] [pid 7396:tid 19940] (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 [Mon Mar 29 08:17:34.746195 2021] [proxy:error] [pid 7396:tid 19940] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:17:34.746195 2021] [proxy_http:error] [pid 7396:tid 19940] [client 38.79.221.10:44062] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:17:35.853797 2021] [proxy:error] [pid 7396:tid 20592] (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 [Mon Mar 29 08:17:35.853797 2021] [proxy_http:error] [pid 7396:tid 20592] [client 198.46.180.141:9253] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:17:40.923806 2021] [proxy:error] [pid 7396:tid 21036] (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 [Mon Mar 29 08:17:40.923806 2021] [proxy_http:error] [pid 7396:tid 21036] [client 38.79.221.103:47801] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:17:44.465012 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 08:17:44.465012 2021] [proxy_http:error] [pid 7396:tid 20404] [client 45.61.183.7:47941] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:17:46.305815 2021] [proxy:error] [pid 7396:tid 19924] (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 [Mon Mar 29 08:17:46.305815 2021] [proxy_http:error] [pid 7396:tid 19924] [client 104.164.201.38:12981] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:18:31.109094 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 08:18:31.109094 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:18:31.109094 2021] [proxy_http:error] [pid 7396:tid 20828] [client 172.84.98.239:12075] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:18:34.166699 2021] [proxy:error] [pid 7396:tid 19996] (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 [Mon Mar 29 08:18:34.166699 2021] [proxy_http:error] [pid 7396:tid 19996] [client 192.30.83.30:5857] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:19:19.047978 2021] [proxy:error] [pid 7396:tid 20420] (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 [Mon Mar 29 08:19:19.047978 2021] [proxy:error] [pid 7396:tid 20420] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:19:19.047978 2021] [proxy_http:error] [pid 7396:tid 20420] [client 198.46.180.141:21321] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:21:38.605823 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 08:21:38.605823 2021] [proxy:error] [pid 7396:tid 19972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:21:38.605823 2021] [proxy_http:error] [pid 7396:tid 19972] [client 201.245.192.253:52172] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:21:38.886624 2021] [proxy:error] [pid 7396:tid 20616] (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 [Mon Mar 29 08:21:38.886624 2021] [proxy_http:error] [pid 7396:tid 20616] [client 201.245.192.253:51586] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:22:00.118261 2021] [proxy:error] [pid 7396:tid 20616] (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 [Mon Mar 29 08:22:00.118261 2021] [proxy:error] [pid 7396:tid 20616] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:22:00.118261 2021] [proxy_http:error] [pid 7396:tid 20616] [client 201.245.192.253:51588] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:23:38.616834 2021] [proxy:error] [pid 7396:tid 20616] (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 [Mon Mar 29 08:23:38.616834 2021] [proxy:error] [pid 7396:tid 20616] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:23:38.616834 2021] [proxy_http:error] [pid 7396:tid 20616] [client 201.245.192.253:46789] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:25:15.493004 2021] [core:error] [pid 7396:tid 19940] (20024)The given path is misformatted or contained invalid characters: [client 46.4.72.213:59938] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Mon Mar 29 08:31:04.652817 2021] [proxy:error] [pid 7396:tid 20460] (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 [Mon Mar 29 08:31:04.652817 2021] [proxy:error] [pid 7396:tid 20460] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:31:04.652817 2021] [proxy_http:error] [pid 7396:tid 20460] [client 181.61.202.119:52353] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:37:32.875099 2021] [proxy:error] [pid 7396:tid 19604] (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 [Mon Mar 29 08:37:32.875099 2021] [proxy:error] [pid 7396:tid 19604] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:37:32.875099 2021] [proxy_http:error] [pid 7396:tid 19604] [client 201.245.192.253:57764] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 08:37:37.102707 2021] [proxy:error] [pid 7396:tid 20664] (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 [Mon Mar 29 08:37:37.102707 2021] [proxy_http:error] [pid 7396:tid 20664] [client 201.245.192.253:57765] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 08:43:38.555342 2021] [proxy:error] [pid 7396:tid 19604] (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 [Mon Mar 29 08:43:38.555342 2021] [proxy:error] [pid 7396:tid 19604] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:43:38.555342 2021] [proxy_http:error] [pid 7396:tid 19604] [client 201.245.192.253:49995] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:47:05.255705 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 08:47:05.255705 2021] [proxy:error] [pid 7396:tid 19852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:47:05.255705 2021] [proxy_http:error] [pid 7396:tid 19852] [client 196.16.66.169:15298] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:47:11.729716 2021] [proxy:error] [pid 7396:tid 20116] AH00940: HTTP: disabled connection for (172.22.1.31) [Mon Mar 29 08:47:13.695319 2021] [proxy:error] [pid 7396:tid 19748] (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 [Mon Mar 29 08:47:13.695319 2021] [proxy_http:error] [pid 7396:tid 19748] [client 196.16.66.154:36416] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:48:23.255842 2021] [proxy:error] [pid 7396:tid 20664] (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 [Mon Mar 29 08:48:23.255842 2021] [proxy:error] [pid 7396:tid 20664] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:48:23.255842 2021] [proxy_http:error] [pid 7396:tid 20664] [client 196.16.66.137:52549] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:48:23.255842 2021] [proxy:error] [pid 7396:tid 20276] (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 [Mon Mar 29 08:48:23.255842 2021] [proxy_http:error] [pid 7396:tid 20276] [client 196.16.66.137:7083] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:50:18.945645 2021] [proxy:error] [pid 7396:tid 20408] (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 [Mon Mar 29 08:50:18.945645 2021] [proxy:error] [pid 7396:tid 20408] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 08:50:18.945645 2021] [proxy_http:error] [pid 7396:tid 20408] [client 196.16.66.90:50128] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 08:50:50.738501 2021] [proxy:error] [pid 7396:tid 20840] AH00940: HTTP: disabled connection for (172.22.1.31) [Mon Mar 29 08:50:58.959715 2021] [proxy:error] [pid 7396:tid 20444] AH00940: HTTP: disabled connection for (172.22.1.31) [Mon Mar 29 08:51:10.300935 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 08:53:48.641213 2021] [proxy:error] [pid 7396:tid 20688] (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 [Mon Mar 29 08:53:48.641213 2021] [proxy:error] [pid 7396:tid 20688] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 08:53:48.641213 2021] [proxy_http:error] [pid 7396:tid 20688] [client 181.61.202.119:52574] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 08:56:33.580303 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 09:01:38.623239 2021] [proxy:error] [pid 7396:tid 20408] (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 [Mon Mar 29 09:01:38.623239 2021] [proxy:error] [pid 7396:tid 20408] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:01:38.623239 2021] [proxy_http:error] [pid 7396:tid 20408] [client 201.245.192.253:52178] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:01:39.294040 2021] [proxy:error] [pid 7396:tid 20176] (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 [Mon Mar 29 09:01:39.294040 2021] [proxy_http:error] [pid 7396:tid 20176] [client 201.245.192.253:51822] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:02:00.525677 2021] [proxy:error] [pid 7396:tid 20176] (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 [Mon Mar 29 09:02:00.525677 2021] [proxy:error] [pid 7396:tid 20176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:02:00.525677 2021] [proxy_http:error] [pid 7396:tid 20176] [client 201.245.192.253:51826] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:02:44.049754 2021] [proxy:error] [pid 7396:tid 20664] (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 [Mon Mar 29 09:02:44.049754 2021] [proxy:error] [pid 7396:tid 20664] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:02:44.049754 2021] [proxy_http:error] [pid 7396:tid 20664] [client 201.245.192.253:57093] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:02:44.720555 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 09:02:44.720555 2021] [proxy_http:error] [pid 7396:tid 20680] [client 190.84.172.244:62214] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:03:11.412202 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 09:03:11.412202 2021] [proxy:error] [pid 7396:tid 20860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 09:03:11.412202 2021] [proxy_http:error] [pid 7396:tid 20860] [client 45.92.0.188:42877] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:03:11.833402 2021] [proxy:error] [pid 7396:tid 20076] (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 [Mon Mar 29 09:03:11.833402 2021] [proxy_http:error] [pid 7396:tid 20076] [client 45.92.0.220:5473] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:03:26.091827 2021] [proxy:error] [pid 7396:tid 20248] (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 [Mon Mar 29 09:03:26.091827 2021] [proxy:error] [pid 7396:tid 20248] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:03:26.091827 2021] [proxy_http:error] [pid 7396:tid 20248] [client 190.84.172.244:62217] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:03:37.963448 2021] [proxy:error] [pid 7396:tid 20520] (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 [Mon Mar 29 09:03:37.963448 2021] [proxy:error] [pid 7396:tid 20520] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:03:37.963448 2021] [proxy_http:error] [pid 7396:tid 20520] [client 201.245.192.253:53087] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:03:49.991069 2021] [proxy:error] [pid 7396:tid 20248] (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 [Mon Mar 29 09:03:49.991069 2021] [proxy:error] [pid 7396:tid 20248] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 09:03:49.991069 2021] [proxy_http:error] [pid 7396:tid 20248] [client 45.92.0.28:59697] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:04:19.693522 2021] [proxy:error] [pid 7396:tid 20944] AH00940: HTTP: disabled connection for (172.22.1.31) [Mon Mar 29 09:04:24.498330 2021] [proxy:error] [pid 7396:tid 19780] AH00940: HTTP: disabled connection for (172.22.1.31) [Mon Mar 29 09:05:47.490476 2021] [proxy:error] [pid 7396:tid 20792] (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 [Mon Mar 29 09:05:47.490476 2021] [proxy:error] [pid 7396:tid 20792] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:05:47.490476 2021] [proxy_http:error] [pid 7396:tid 20792] [client 190.157.162.202:50640] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:05:58.394895 2021] [proxy:error] [pid 7396:tid 20372] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:06:01.936101 2021] [proxy:error] [pid 7396:tid 20116] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:06:03.262103 2021] [proxy:error] [pid 7396:tid 20932] (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 [Mon Mar 29 09:06:03.262103 2021] [proxy:error] [pid 7396:tid 20932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 09:06:03.262103 2021] [proxy_http:error] [pid 7396:tid 20932] [client 45.92.0.188:20153] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:06:03.574104 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 09:06:03.574104 2021] [proxy_http:error] [pid 7396:tid 20860] [client 190.157.162.202:50645] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:06:24.790141 2021] [proxy:error] [pid 7396:tid 20860] (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 [Mon Mar 29 09:06:24.790141 2021] [proxy:error] [pid 7396:tid 20860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:06:24.790141 2021] [proxy_http:error] [pid 7396:tid 20860] [client 190.157.162.202:50702] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:06:25.570143 2021] [proxy:error] [pid 7396:tid 19780] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:06:34.618159 2021] [proxy:error] [pid 7396:tid 20860] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:07:09.203419 2021] [proxy:error] [pid 7396:tid 19852] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:07:20.638239 2021] [proxy:error] [pid 7396:tid 19748] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:07:28.453853 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 09:09:22.271653 2021] [proxy:error] [pid 7396:tid 19748] (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 [Mon Mar 29 09:09:22.271653 2021] [proxy:error] [pid 7396:tid 19748] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Mon Mar 29 09:09:22.271653 2021] [proxy_http:error] [pid 7396:tid 19748] [client 45.92.0.60:36513] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:09:25.797259 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 09:09:25.797259 2021] [proxy_http:error] [pid 7396:tid 20828] [client 45.92.0.188:31459] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:09:35.094876 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 09:09:35.094876 2021] [proxy_http:error] [pid 7396:tid 19852] [client 45.92.0.141:61071] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Mon Mar 29 09:09:38.495681 2021] [proxy:error] [pid 7396:tid 19612] (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 [Mon Mar 29 09:09:38.495681 2021] [proxy:error] [pid 7396:tid 19612] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:09:38.495681 2021] [proxy_http:error] [pid 7396:tid 19612] [client 200.122.193.26:53583] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:09:46.794896 2021] [proxy:error] [pid 7396:tid 20840] (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 [Mon Mar 29 09:09:46.794896 2021] [proxy_http:error] [pid 7396:tid 20840] [client 200.122.193.26:53582] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:09:53.658908 2021] [proxy:error] [pid 7396:tid 20116] (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 [Mon Mar 29 09:09:53.658908 2021] [proxy_http:error] [pid 7396:tid 20116] [client 191.156.62.180:51512] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:10:49.491406 2021] [proxy:error] [pid 7396:tid 19876] (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 [Mon Mar 29 09:10:49.491406 2021] [proxy:error] [pid 7396:tid 19876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:10:49.491406 2021] [proxy_http:error] [pid 7396:tid 19876] [client 181.53.12.180:18461] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:10:55.388217 2021] [proxy:error] [pid 7396:tid 20100] (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 [Mon Mar 29 09:10:55.388217 2021] [proxy_http:error] [pid 7396:tid 20100] [client 201.245.192.253:58817] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:11:38.647093 2021] [proxy:error] [pid 7396:tid 20372] (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 [Mon Mar 29 09:11:38.647093 2021] [proxy:error] [pid 7396:tid 20372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:11:38.647093 2021] [proxy_http:error] [pid 7396:tid 20372] [client 201.245.192.253:51860] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:11:38.849893 2021] [proxy:error] [pid 7396:tid 20372] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:11:39.177493 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 09:11:39.177493 2021] [proxy_http:error] [pid 7396:tid 20828] [client 201.245.192.253:52184] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:12:38.894398 2021] [proxy:error] [pid 7396:tid 19780] (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 [Mon Mar 29 09:12:38.894398 2021] [proxy:error] [pid 7396:tid 19780] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:12:38.894398 2021] [proxy_http:error] [pid 7396:tid 19780] [client 181.53.12.180:10179] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:20:44.102051 2021] [proxy:error] [pid 7396:tid 20976] (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 [Mon Mar 29 09:20:44.102051 2021] [proxy:error] [pid 7396:tid 20976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:20:44.102051 2021] [proxy_http:error] [pid 7396:tid 20976] [client 186.154.173.71:49683] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:20:46.520055 2021] [proxy:error] [pid 7396:tid 20520] (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 [Mon Mar 29 09:20:46.520055 2021] [proxy_http:error] [pid 7396:tid 20520] [client 200.122.193.26:53666] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:21:38.686546 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 09:21:38.686546 2021] [proxy:error] [pid 7396:tid 19852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:21:38.686546 2021] [proxy_http:error] [pid 7396:tid 19852] [client 201.245.192.253:52190] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:21:39.123347 2021] [proxy:error] [pid 7396:tid 20944] (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 [Mon Mar 29 09:21:39.123347 2021] [proxy_http:error] [pid 7396:tid 20944] [client 201.245.192.253:51890] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:22:00.339384 2021] [proxy:error] [pid 7396:tid 20944] (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 [Mon Mar 29 09:22:00.339384 2021] [proxy:error] [pid 7396:tid 20944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:22:00.339384 2021] [proxy_http:error] [pid 7396:tid 20944] [client 201.245.192.253:51916] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:22:09.200200 2021] [proxy:error] [pid 7396:tid 20976] (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 [Mon Mar 29 09:22:09.200200 2021] [proxy:error] [pid 7396:tid 20976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:22:09.200200 2021] [proxy_http:error] [pid 7396:tid 20976] [client 201.245.192.253:49934] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:22:39.667054 2021] [proxy:error] [pid 7396:tid 20084] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:22:57.482285 2021] [proxy:error] [pid 7396:tid 19964] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:23:05.251098 2021] [proxy:error] [pid 7396:tid 19860] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:23:38.603957 2021] [proxy:error] [pid 7396:tid 20752] (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 [Mon Mar 29 09:23:38.603957 2021] [proxy:error] [pid 7396:tid 20752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:23:38.603957 2021] [proxy_http:error] [pid 7396:tid 20752] [client 201.245.192.253:41285] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:23:52.659582 2021] [proxy:error] [pid 7396:tid 19788] (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 [Mon Mar 29 09:23:52.659582 2021] [proxy:error] [pid 7396:tid 19788] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:23:52.659582 2021] [proxy_http:error] [pid 7396:tid 19788] [client 201.245.192.253:49942] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:26:02.389410 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 09:26:02.389410 2021] [proxy:error] [pid 7396:tid 19836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:26:02.389410 2021] [proxy_http:error] [pid 7396:tid 19836] [client 190.157.162.202:50810] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:26:03.762212 2021] [proxy:error] [pid 7396:tid 20372] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:26:47.021088 2021] [proxy:error] [pid 7396:tid 20276] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:27:48.063995 2021] [proxy:error] [pid 7396:tid 20248] (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 [Mon Mar 29 09:27:48.063995 2021] [proxy:error] [pid 7396:tid 20248] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:27:48.063995 2021] [proxy_http:error] [pid 7396:tid 20248] [client 201.245.192.253:49992] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:28:25.238861 2021] [proxy:error] [pid 7396:tid 19780] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:32:48.317723 2021] [proxy:error] [pid 7396:tid 19932] (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 [Mon Mar 29 09:32:48.317723 2021] [proxy:error] [pid 7396:tid 19932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:32:48.317723 2021] [proxy_http:error] [pid 7396:tid 19932] [client 200.122.193.26:53744] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 09:32:56.367337 2021] [proxy:error] [pid 7396:tid 20976] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:33:08.738158 2021] [proxy:error] [pid 7396:tid 20408] (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 [Mon Mar 29 09:33:08.738158 2021] [proxy_http:error] [pid 7396:tid 20408] [client 201.245.192.253:53940] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:34:26.675895 2021] [proxy:error] [pid 7396:tid 20408] (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 [Mon Mar 29 09:34:26.675895 2021] [proxy:error] [pid 7396:tid 20408] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:34:26.675895 2021] [proxy_http:error] [pid 7396:tid 20408] [client 190.84.172.244:62507] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:35:17.063984 2021] [proxy:error] [pid 7396:tid 21072] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:42:54.753188 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 09:43:36.888862 2021] [proxy:error] [pid 7396:tid 20116] (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 [Mon Mar 29 09:43:36.888862 2021] [proxy:error] [pid 7396:tid 20116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:43:36.888862 2021] [proxy_http:error] [pid 7396:tid 20116] [client 201.245.192.253:40011] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:47:08.581234 2021] [proxy:error] [pid 7396:tid 19964] (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 [Mon Mar 29 09:47:08.581234 2021] [proxy:error] [pid 7396:tid 19964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:47:08.581234 2021] [proxy_http:error] [pid 7396:tid 19964] [client 190.84.172.244:62662] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 09:47:44.554897 2021] [proxy:error] [pid 7396:tid 19548] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:47:49.952506 2021] [proxy:error] [pid 7396:tid 20036] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:48:00.092524 2021] [proxy:error] [pid 7396:tid 20944] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:48:06.332535 2021] [proxy:error] [pid 7396:tid 20264] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 09:52:17.040575 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 09:52:17.040575 2021] [proxy:error] [pid 7396:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:52:17.040575 2021] [proxy_http:error] [pid 7396:tid 20680] [client 190.84.172.244:62694] 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 [Mon Mar 29 09:53:37.599117 2021] [proxy:error] [pid 7396:tid 19964] (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 [Mon Mar 29 09:53:37.599117 2021] [proxy:error] [pid 7396:tid 19964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 09:53:37.599117 2021] [proxy_http:error] [pid 7396:tid 19964] [client 201.245.192.253:53705] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:00:13.808613 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 10:01:38.657162 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 10:01:38.657162 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:01:38.657162 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:52082] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:01:38.719562 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 10:01:38.719562 2021] [proxy_http:error] [pid 7396:tid 19836] [client 201.245.192.253:52196] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:01:59.888799 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 10:01:59.888799 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:01:59.888799 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:52094] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:02:38.748467 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 10:03:38.012971 2021] [proxy:error] [pid 7396:tid 20276] (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 [Mon Mar 29 10:03:38.012971 2021] [proxy:error] [pid 7396:tid 20276] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:03:38.012971 2021] [proxy_http:error] [pid 7396:tid 20276] [client 201.245.192.253:51131] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:09:34.426797 2021] [proxy:error] [pid 7396:tid 20828] (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 [Mon Mar 29 10:09:34.426797 2021] [proxy:error] [pid 7396:tid 20828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:09:34.426797 2021] [proxy_http:error] [pid 7396:tid 20828] [client 201.245.192.253:64497] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:09:37.359603 2021] [proxy:error] [pid 7396:tid 19804] (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 [Mon Mar 29 10:09:37.359603 2021] [proxy_http:error] [pid 7396:tid 19804] [client 201.245.192.253:64498] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:09:43.896014 2021] [proxy:error] [pid 7396:tid 20420] (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 [Mon Mar 29 10:09:43.896014 2021] [proxy_http:error] [pid 7396:tid 20420] [client 201.245.192.253:64501] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:10:04.940451 2021] [proxy:error] [pid 7396:tid 19836] (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 [Mon Mar 29 10:10:04.940451 2021] [proxy:error] [pid 7396:tid 19836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:10:04.940451 2021] [proxy_http:error] [pid 7396:tid 19836] [client 201.245.192.253:64502] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:11:38.977416 2021] [proxy:error] [pid 7396:tid 20624] (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 [Mon Mar 29 10:11:38.977416 2021] [proxy:error] [pid 7396:tid 20624] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:11:38.977416 2021] [proxy_http:error] [pid 7396:tid 20624] [client 201.245.192.253:52182] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:11:39.180217 2021] [proxy:error] [pid 7396:tid 20624] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:11:39.211417 2021] [proxy:error] [pid 7396:tid 19548] (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 [Mon Mar 29 10:11:39.211417 2021] [proxy_http:error] [pid 7396:tid 19548] [client 201.245.192.253:52202] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:11:50.147036 2021] [proxy:error] [pid 7396:tid 20632] (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 [Mon Mar 29 10:11:50.147036 2021] [proxy:error] [pid 7396:tid 20632] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Mon Mar 29 10:11:50.147036 2021] [proxy_http:error] [pid 7396:tid 20632] [client 152.61.192.232:52170] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Mon Mar 29 10:11:50.381036 2021] [proxy:error] [pid 7396:tid 20632] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 10:11:50.615037 2021] [proxy:error] [pid 7396:tid 20632] AH00940: HTTP: disabled connection for (172.22.1.51) [Mon Mar 29 10:13:38.068025 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 10:13:38.068025 2021] [proxy:error] [pid 7396:tid 20216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:13:38.068025 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:57553] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:18:18.384918 2021] [proxy:error] [pid 7396:tid 20276] (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 [Mon Mar 29 10:18:18.384918 2021] [proxy:error] [pid 7396:tid 20276] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:18:18.384918 2021] [proxy_http:error] [pid 7396:tid 20276] [client 201.245.192.253:63917] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:21:38.361669 2021] [proxy:error] [pid 7396:tid 19748] (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 [Mon Mar 29 10:21:38.361669 2021] [proxy:error] [pid 7396:tid 19748] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:21:38.361669 2021] [proxy_http:error] [pid 7396:tid 19748] [client 201.245.192.253:52266] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:21:38.564469 2021] [proxy:error] [pid 7396:tid 19748] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:21:38.720470 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 10:21:38.720470 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:52208] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:22:30.044560 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 10:22:30.044560 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:22:30.044560 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:63945] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:22:38.780575 2021] [proxy:error] [pid 7396:tid 20264] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:40.402978 2021] [proxy:error] [pid 7396:tid 20932] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:41.401380 2021] [proxy:error] [pid 7396:tid 20404] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:42.274981 2021] [proxy:error] [pid 7396:tid 20932] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:46.221788 2021] [proxy:error] [pid 7396:tid 20404] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:46.970589 2021] [proxy:error] [pid 7396:tid 20944] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:51.525797 2021] [proxy:error] [pid 7396:tid 20792] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:52.430599 2021] [proxy:error] [pid 7396:tid 21096] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:56.237006 2021] [proxy:error] [pid 7396:tid 20600] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:56.985807 2021] [proxy:error] [pid 7396:tid 19752] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:57.516208 2021] [proxy:error] [pid 7396:tid 20600] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:57.984209 2021] [proxy:error] [pid 7396:tid 19752] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:22:58.467810 2021] [proxy:error] [pid 7396:tid 19876] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:23:38.076279 2021] [proxy:error] [pid 7396:tid 20624] (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 [Mon Mar 29 10:23:38.076279 2021] [proxy:error] [pid 7396:tid 20624] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:23:38.076279 2021] [proxy_http:error] [pid 7396:tid 20624] [client 201.245.192.253:43549] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:23:56.109911 2021] [proxy:error] [pid 7396:tid 19932] (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 [Mon Mar 29 10:23:56.109911 2021] [proxy:error] [pid 7396:tid 19932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:23:56.109911 2021] [proxy_http:error] [pid 7396:tid 19932] [client 201.245.192.253:63965] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:24:28.105567 2021] [proxy:error] [pid 7396:tid 19868] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:30:05.237759 2021] [proxy:error] [pid 7396:tid 20408] (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 [Mon Mar 29 10:30:05.237759 2021] [proxy:error] [pid 7396:tid 20408] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:30:05.237759 2021] [proxy_http:error] [pid 7396:tid 20408] [client 201.245.192.253:64072] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:33:37.928533 2021] [proxy:error] [pid 7396:tid 20688] (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 [Mon Mar 29 10:33:37.928533 2021] [proxy:error] [pid 7396:tid 20688] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:33:37.928533 2021] [proxy_http:error] [pid 7396:tid 20688] [client 201.245.192.253:52671] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:39:39.724368 2021] [proxy:error] [pid 7396:tid 20680] (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 [Mon Mar 29 10:39:39.724368 2021] [proxy:error] [pid 7396:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:39:39.724368 2021] [proxy_http:error] [pid 7396:tid 20680] [client 201.245.192.253:50737] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:39:40.582370 2021] [proxy:error] [pid 7396:tid 20300] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 10:39:43.702375 2021] [proxy:error] [pid 7396:tid 20228] (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 [Mon Mar 29 10:39:43.702375 2021] [proxy_http:error] [pid 7396:tid 20228] [client 201.245.192.253:50738] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:39:45.964379 2021] [proxy:error] [pid 7396:tid 20804] (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 [Mon Mar 29 10:39:45.964379 2021] [proxy_http:error] [pid 7396:tid 20804] [client 201.245.192.253:52213] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:39:53.811193 2021] [proxy:error] [pid 7396:tid 20792] (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 [Mon Mar 29 10:39:53.811193 2021] [proxy_http:error] [pid 7396:tid 20792] [client 201.245.192.253:50739] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:43:26.891967 2021] [proxy:error] [pid 7396:tid 20960] (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 [Mon Mar 29 10:43:26.891967 2021] [proxy:error] [pid 7396:tid 20960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:43:26.891967 2021] [proxy_http:error] [pid 7396:tid 20960] [client 201.245.192.253:50627] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:43:40.198791 2021] [proxy:error] [pid 7396:tid 19796] (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 [Mon Mar 29 10:43:40.198791 2021] [proxy_http:error] [pid 7396:tid 19796] [client 201.245.192.253:52261] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:52:21.395706 2021] [proxy:error] [pid 7396:tid 20156] (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 [Mon Mar 29 10:52:21.395706 2021] [proxy:error] [pid 7396:tid 20156] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:52:21.395706 2021] [proxy_http:error] [pid 7396:tid 20156] [client 201.245.192.253:52317] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:52:27.386117 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 10:52:27.386117 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:50067] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:53:38.257041 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 10:53:38.257041 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:53:38.257041 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:59035] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:53:46.712256 2021] [proxy:error] [pid 7396:tid 20476] (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 [Mon Mar 29 10:53:46.712256 2021] [proxy:error] [pid 7396:tid 20476] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:53:46.712256 2021] [proxy_http:error] [pid 7396:tid 20476] [client 201.245.192.253:50073] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 10:57:48.668681 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 10:57:48.668681 2021] [proxy:error] [pid 7396:tid 19720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:57:48.668681 2021] [proxy_http:error] [pid 7396:tid 19720] [client 201.245.192.253:56396] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:57:52.677888 2021] [proxy:error] [pid 7396:tid 20444] (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 [Mon Mar 29 10:57:52.677888 2021] [proxy_http:error] [pid 7396:tid 20444] [client 201.245.192.253:56426] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 10:58:25.281945 2021] [proxy:error] [pid 7396:tid 20444] (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 [Mon Mar 29 10:58:25.281945 2021] [proxy:error] [pid 7396:tid 20444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 10:58:25.281945 2021] [proxy_http:error] [pid 7396:tid 20444] [client 201.245.192.253:56430] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:00:03.967719 2021] [proxy:error] [pid 7396:tid 20868] (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 [Mon Mar 29 11:00:03.967719 2021] [proxy:error] [pid 7396:tid 20868] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:00:03.967719 2021] [proxy_http:error] [pid 7396:tid 20868] [client 201.245.192.253:56457] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:01:38.831485 2021] [proxy:error] [pid 7396:tid 20544] (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 [Mon Mar 29 11:01:38.831485 2021] [proxy:error] [pid 7396:tid 20544] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:01:38.831485 2021] [proxy_http:error] [pid 7396:tid 20544] [client 201.245.192.253:52214] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:01:38.862685 2021] [proxy:error] [pid 7396:tid 19520] (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 [Mon Mar 29 11:01:38.862685 2021] [proxy_http:error] [pid 7396:tid 19520] [client 201.245.192.253:52546] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:02:00.078722 2021] [proxy:error] [pid 7396:tid 19520] (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 [Mon Mar 29 11:02:00.078722 2021] [proxy:error] [pid 7396:tid 19520] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:02:00.078722 2021] [proxy_http:error] [pid 7396:tid 19520] [client 201.245.192.253:52548] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:03:37.828494 2021] [proxy:error] [pid 7396:tid 19712] (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 [Mon Mar 29 11:03:37.828494 2021] [proxy:error] [pid 7396:tid 19712] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:03:37.828494 2021] [proxy_http:error] [pid 7396:tid 19712] [client 201.245.192.253:40111] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:09:54.740756 2021] [proxy:error] [pid 7396:tid 20444] (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 [Mon Mar 29 11:09:54.740756 2021] [proxy:error] [pid 7396:tid 20444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:09:54.740756 2021] [proxy_http:error] [pid 7396:tid 20444] [client 201.245.192.253:65188] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:11:38.402938 2021] [proxy:error] [pid 7396:tid 20804] (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 [Mon Mar 29 11:11:38.402938 2021] [proxy:error] [pid 7396:tid 20804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:11:38.402938 2021] [proxy_http:error] [pid 7396:tid 20804] [client 201.245.192.253:52220] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:11:38.980139 2021] [proxy:error] [pid 7396:tid 20124] (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 [Mon Mar 29 11:11:38.980139 2021] [proxy_http:error] [pid 7396:tid 20124] [client 201.245.192.253:52650] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:12:00.211777 2021] [proxy:error] [pid 7396:tid 20124] (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 [Mon Mar 29 11:12:00.211777 2021] [proxy:error] [pid 7396:tid 20124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:12:00.211777 2021] [proxy_http:error] [pid 7396:tid 20124] [client 201.245.192.253:52672] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:13:09.959499 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 11:13:09.959499 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:13:09.959499 2021] [proxy_http:error] [pid 7396:tid 21096] [client 201.245.192.253:54604] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:13:37.243947 2021] [proxy:error] [pid 7396:tid 19860] (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 [Mon Mar 29 11:13:37.243947 2021] [proxy:error] [pid 7396:tid 19860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:13:37.243947 2021] [proxy_http:error] [pid 7396:tid 19860] [client 201.245.192.253:50085] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:16:19.063031 2021] [proxy:error] [pid 7396:tid 20800] (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 [Mon Mar 29 11:16:19.063031 2021] [proxy:error] [pid 7396:tid 20800] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:16:19.063031 2021] [proxy_http:error] [pid 7396:tid 20800] [client 201.245.192.253:50808] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:19:48.961400 2021] [proxy:error] [pid 7396:tid 20720] (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 [Mon Mar 29 11:19:48.961400 2021] [proxy:error] [pid 7396:tid 20720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:19:48.961400 2021] [proxy_http:error] [pid 7396:tid 20720] [client 201.245.192.253:52450] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:20:31.970675 2021] [proxy:error] [pid 7396:tid 20156] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 11:20:33.546278 2021] [proxy:error] [pid 7396:tid 19612] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 11:21:38.301992 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 11:21:38.301992 2021] [proxy:error] [pid 7396:tid 19972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:21:38.301992 2021] [proxy_http:error] [pid 7396:tid 19972] [client 201.245.192.253:52916] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:21:38.504792 2021] [proxy:error] [pid 7396:tid 19972] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 11:21:38.925993 2021] [proxy:error] [pid 7396:tid 20156] (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 [Mon Mar 29 11:21:38.925993 2021] [proxy_http:error] [pid 7396:tid 20156] [client 201.245.192.253:52226] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:23:39.295804 2021] [proxy:error] [pid 7396:tid 19860] (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 [Mon Mar 29 11:23:39.295804 2021] [proxy:error] [pid 7396:tid 19860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:23:39.295804 2021] [proxy_http:error] [pid 7396:tid 19860] [client 201.245.192.253:52605] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:25:18.823979 2021] [proxy:error] [pid 7396:tid 19712] (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 [Mon Mar 29 11:25:18.823979 2021] [proxy:error] [pid 7396:tid 19712] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:25:18.823979 2021] [proxy_http:error] [pid 7396:tid 19712] [client 201.245.192.253:52483] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:25:31.584802 2021] [proxy:error] [pid 7396:tid 19648] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 11:30:33.336132 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 11:30:33.336132 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:30:33.336132 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:50998] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:36.237737 2021] [proxy:error] [pid 7396:tid 20720] (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 [Mon Mar 29 11:30:36.237737 2021] [proxy_http:error] [pid 7396:tid 20720] [client 201.245.192.253:50999] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:36.471737 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 11:30:36.471737 2021] [proxy_http:error] [pid 7396:tid 19720] [client 201.245.192.253:51000] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:40.122144 2021] [proxy:error] [pid 7396:tid 19712] (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 [Mon Mar 29 11:30:40.122144 2021] [proxy_http:error] [pid 7396:tid 19712] [client 201.245.192.253:51001] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:40.356144 2021] [proxy:error] [pid 7396:tid 20696] (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 [Mon Mar 29 11:30:40.356144 2021] [proxy_http:error] [pid 7396:tid 20696] [client 201.245.192.253:51002] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:42.306147 2021] [proxy:error] [pid 7396:tid 21032] (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 [Mon Mar 29 11:30:42.306147 2021] [proxy_http:error] [pid 7396:tid 21032] [client 201.245.192.253:51003] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:47.781757 2021] [proxy:error] [pid 7396:tid 20976] (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 [Mon Mar 29 11:30:47.781757 2021] [proxy_http:error] [pid 7396:tid 20976] [client 201.245.192.253:51006] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:47.968957 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 11:30:47.968957 2021] [proxy_http:error] [pid 7396:tid 19972] [client 201.245.192.253:51007] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:30:48.218558 2021] [proxy:error] [pid 7396:tid 20892] (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 [Mon Mar 29 11:30:48.218558 2021] [proxy_http:error] [pid 7396:tid 20892] [client 201.245.192.253:51008] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:33:04.032396 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 11:33:23.298430 2021] [proxy:error] [pid 7396:tid 19768] (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 [Mon Mar 29 11:33:23.298430 2021] [proxy:error] [pid 7396:tid 19768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:33:23.298430 2021] [proxy_http:error] [pid 7396:tid 19768] [client 201.245.192.253:52506] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:33:37.042054 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 11:33:37.042054 2021] [proxy:error] [pid 7396:tid 19972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:33:37.042054 2021] [proxy_http:error] [pid 7396:tid 19972] [client 201.245.192.253:59631] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:36:03.838312 2021] [proxy:error] [pid 7396:tid 20804] (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 [Mon Mar 29 11:36:03.838312 2021] [proxy:error] [pid 7396:tid 20804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:36:03.838312 2021] [proxy_http:error] [pid 7396:tid 20804] [client 201.245.192.253:56179] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:36:05.491915 2021] [proxy:error] [pid 7396:tid 19804] (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 [Mon Mar 29 11:36:05.491915 2021] [proxy_http:error] [pid 7396:tid 19804] [client 201.245.192.253:56178] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:37:31.463666 2021] [proxy:error] [pid 7396:tid 20804] (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 [Mon Mar 29 11:37:31.463666 2021] [proxy:error] [pid 7396:tid 20804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:37:31.463666 2021] [proxy_http:error] [pid 7396:tid 20804] [client 201.245.192.253:52521] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:41:59.066536 2021] [proxy:error] [pid 7396:tid 20004] (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 [Mon Mar 29 11:41:59.066536 2021] [proxy:error] [pid 7396:tid 20004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:41:59.066536 2021] [proxy_http:error] [pid 7396:tid 20004] [client 190.157.162.202:62503] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:42:05.852548 2021] [proxy:error] [pid 7396:tid 20100] (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 [Mon Mar 29 11:42:05.852548 2021] [proxy_http:error] [pid 7396:tid 20100] [client 190.157.162.202:62508] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:42:27.583386 2021] [proxy:error] [pid 7396:tid 20100] (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 [Mon Mar 29 11:42:27.583386 2021] [proxy:error] [pid 7396:tid 20100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:42:27.583386 2021] [proxy_http:error] [pid 7396:tid 20100] [client 190.157.162.202:62517] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:43:38.204710 2021] [proxy:error] [pid 7396:tid 20300] (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 [Mon Mar 29 11:43:38.204710 2021] [proxy:error] [pid 7396:tid 20300] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:43:38.204710 2021] [proxy_http:error] [pid 7396:tid 20300] [client 201.245.192.253:53289] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 11:44:25.878394 2021] [proxy:error] [pid 7396:tid 19612] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 11:44:36.751613 2021] [proxy:error] [pid 7396:tid 20840] (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 [Mon Mar 29 11:44:36.751613 2021] [proxy:error] [pid 7396:tid 20840] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:44:36.751613 2021] [proxy_http:error] [pid 7396:tid 20840] [client 201.245.192.253:55020] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:44:48.904034 2021] [proxy:error] [pid 7396:tid 20608] (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 [Mon Mar 29 11:44:48.904034 2021] [proxy_http:error] [pid 7396:tid 20608] [client 190.157.162.202:62599] 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 [Mon Mar 29 11:48:36.633234 2021] [proxy:error] [pid 7396:tid 21096] (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 [Mon Mar 29 11:48:36.633234 2021] [proxy:error] [pid 7396:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:48:36.633234 2021] [proxy_http:error] [pid 7396:tid 21096] [client 181.59.170.186:52302] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:48:38.676838 2021] [proxy:error] [pid 7396:tid 19804] (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 [Mon Mar 29 11:48:38.676838 2021] [proxy_http:error] [pid 7396:tid 19804] [client 181.59.170.186:52306] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:48:41.375643 2021] [proxy:error] [pid 7396:tid 19956] (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 [Mon Mar 29 11:48:41.375643 2021] [proxy_http:error] [pid 7396:tid 19956] [client 181.59.170.186:52307] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:48:42.904445 2021] [proxy:error] [pid 7396:tid 20372] (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 [Mon Mar 29 11:48:42.904445 2021] [proxy_http:error] [pid 7396:tid 20372] [client 181.59.170.186:52308] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:48:53.528064 2021] [proxy:error] [pid 7396:tid 20028] (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 [Mon Mar 29 11:48:53.528064 2021] [proxy_http:error] [pid 7396:tid 20028] [client 181.59.170.186:52311] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 11:55:57.318408 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 11:55:57.318408 2021] [proxy:error] [pid 7396:tid 19720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 11:55:57.318408 2021] [proxy_http:error] [pid 7396:tid 19720] [client 181.59.170.186:63585] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 12:00:32.502892 2021] [proxy:error] [pid 7396:tid 20176] (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 [Mon Mar 29 12:00:32.502892 2021] [proxy:error] [pid 7396:tid 20176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:00:32.502892 2021] [proxy_http:error] [pid 7396:tid 20176] [client 201.245.192.253:55129] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 12:01:38.023007 2021] [proxy:error] [pid 7396:tid 19720] (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 [Mon Mar 29 12:01:38.023007 2021] [proxy:error] [pid 7396:tid 19720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:01:38.023007 2021] [proxy_http:error] [pid 7396:tid 19720] [client 201.245.192.253:52232] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:01:38.413007 2021] [proxy:error] [pid 7396:tid 19956] (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 [Mon Mar 29 12:01:38.413007 2021] [proxy_http:error] [pid 7396:tid 19956] [client 201.245.192.253:53174] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:01:59.629045 2021] [proxy:error] [pid 7396:tid 19956] (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 [Mon Mar 29 12:01:59.629045 2021] [proxy:error] [pid 7396:tid 19956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:01:59.629045 2021] [proxy_http:error] [pid 7396:tid 19956] [client 201.245.192.253:53176] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:03:38.299218 2021] [proxy:error] [pid 7396:tid 20804] (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 [Mon Mar 29 12:03:38.299218 2021] [proxy:error] [pid 7396:tid 20804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:03:38.299218 2021] [proxy_http:error] [pid 7396:tid 20804] [client 201.245.192.253:45919] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:04:13.602080 2021] [proxy:error] [pid 7396:tid 20020] (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 [Mon Mar 29 12:04:13.602080 2021] [proxy:error] [pid 7396:tid 20020] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:04:13.602080 2021] [proxy_http:error] [pid 7396:tid 20020] [client 201.245.192.253:63669] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:07:04.188380 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 12:10:23.884330 2021] [proxy_http:error] [pid 7396:tid 20460] (70008)Partial results are valid but processing is incomplete: [client 190.14.238.29:50419] AH02609: read request body failed to 172.22.1.61:8080 (172.22.1.61) from 190.14.238.29 (), referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Mon Mar 29 12:10:23.884330 2021] [proxy_http:error] [pid 7396:tid 20460] [client 190.14.238.29:50419] AH01097: pass request body failed to 172.22.1.61:8080 (172.22.1.61) from 190.14.238.29 (), referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Mon Mar 29 12:11:38.421261 2021] [proxy:error] [pid 7396:tid 20536] (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 [Mon Mar 29 12:11:38.421261 2021] [proxy:error] [pid 7396:tid 20536] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:11:38.421261 2021] [proxy_http:error] [pid 7396:tid 20536] [client 201.245.192.253:53224] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:11:38.546062 2021] [proxy:error] [pid 7396:tid 20772] (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 [Mon Mar 29 12:11:38.546062 2021] [proxy_http:error] [pid 7396:tid 20772] [client 201.245.192.253:52238] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:11:59.668499 2021] [proxy:error] [pid 7396:tid 20536] (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 [Mon Mar 29 12:11:59.668499 2021] [proxy:error] [pid 7396:tid 20536] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:11:59.668499 2021] [proxy_http:error] [pid 7396:tid 20536] [client 201.245.192.253:53226] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:12:10.323317 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 12:21:38.070715 2021] [proxy:error] [pid 7396:tid 19876] (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 [Mon Mar 29 12:21:38.070715 2021] [proxy:error] [pid 7396:tid 19876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:21:38.070715 2021] [proxy_http:error] [pid 7396:tid 19876] [client 201.245.192.253:52244] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:21:38.710316 2021] [proxy:error] [pid 7396:tid 19780] (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 [Mon Mar 29 12:21:38.710316 2021] [proxy_http:error] [pid 7396:tid 19780] [client 201.245.192.253:53260] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:21:59.941953 2021] [proxy:error] [pid 7396:tid 19780] (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 [Mon Mar 29 12:21:59.941953 2021] [proxy:error] [pid 7396:tid 19780] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:21:59.941953 2021] [proxy_http:error] [pid 7396:tid 19780] [client 201.245.192.253:53262] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:23:38.924127 2021] [proxy:error] [pid 7396:tid 20892] (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 [Mon Mar 29 12:23:38.924127 2021] [proxy:error] [pid 7396:tid 20892] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:23:38.924127 2021] [proxy_http:error] [pid 7396:tid 20892] [client 201.245.192.253:48391] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:43:37.645832 2021] [proxy:error] [pid 7396:tid 19908] (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 [Mon Mar 29 12:43:37.645832 2021] [proxy:error] [pid 7396:tid 19908] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:43:37.645832 2021] [proxy_http:error] [pid 7396:tid 19908] [client 201.245.192.253:33561] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:45:46.564459 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 12:46:19.418116 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 12:53:38.012887 2021] [proxy:error] [pid 7396:tid 20672] (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 [Mon Mar 29 12:53:38.012887 2021] [proxy:error] [pid 7396:tid 20672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 12:53:38.012887 2021] [proxy_http:error] [pid 7396:tid 20672] [client 201.245.192.253:37791] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 12:55:28.913482 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 13:01:05.515273 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 13:01:38.197330 2021] [proxy:error] [pid 7396:tid 20228] (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 [Mon Mar 29 13:01:38.197330 2021] [proxy:error] [pid 7396:tid 20228] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:01:38.197330 2021] [proxy_http:error] [pid 7396:tid 20228] [client 201.245.192.253:52250] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:01:38.415731 2021] [proxy:error] [pid 7396:tid 19548] (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 [Mon Mar 29 13:01:38.415731 2021] [proxy_http:error] [pid 7396:tid 19548] [client 201.245.192.253:53442] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:01:59.709768 2021] [proxy:error] [pid 7396:tid 19548] (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 [Mon Mar 29 13:01:59.709768 2021] [proxy:error] [pid 7396:tid 19548] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:01:59.709768 2021] [proxy_http:error] [pid 7396:tid 19548] [client 201.245.192.253:53444] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:03:37.958740 2021] [proxy:error] [pid 7396:tid 21016] (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 [Mon Mar 29 13:03:37.958740 2021] [proxy:error] [pid 7396:tid 21016] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:03:37.958740 2021] [proxy_http:error] [pid 7396:tid 21016] [client 201.245.192.253:45093] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:04:34.774040 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 13:11:37.628383 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 13:11:37.628383 2021] [proxy:error] [pid 7396:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:11:37.628383 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:53502] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:11:37.659583 2021] [proxy:error] [pid 7396:tid 19996] (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 [Mon Mar 29 13:11:37.659583 2021] [proxy_http:error] [pid 7396:tid 19996] [client 201.245.192.253:52256] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:11:58.875620 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 13:11:58.875620 2021] [proxy:error] [pid 7396:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:11:58.875620 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:53504] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:13:37.920194 2021] [proxy:error] [pid 7396:tid 20840] (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 [Mon Mar 29 13:13:37.920194 2021] [proxy:error] [pid 7396:tid 20840] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:13:37.920194 2021] [proxy_http:error] [pid 7396:tid 20840] [client 201.245.192.253:43909] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:21:37.948637 2021] [proxy:error] [pid 7396:tid 19916] (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 [Mon Mar 29 13:21:37.948637 2021] [proxy:error] [pid 7396:tid 19916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:21:37.948637 2021] [proxy_http:error] [pid 7396:tid 19916] [client 201.245.192.253:53608] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:21:38.167038 2021] [proxy:error] [pid 7396:tid 19916] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 13:21:38.291838 2021] [proxy:error] [pid 7396:tid 19596] (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 [Mon Mar 29 13:21:38.291838 2021] [proxy_http:error] [pid 7396:tid 19596] [client 201.245.192.253:52262] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:23:37.413647 2021] [proxy:error] [pid 7396:tid 20092] (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 [Mon Mar 29 13:23:37.413647 2021] [proxy:error] [pid 7396:tid 20092] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:23:37.413647 2021] [proxy_http:error] [pid 7396:tid 20092] [client 201.245.192.253:33717] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:26:13.133121 2021] [proxy:error] [pid 7396:tid 19752] (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 [Mon Mar 29 13:26:13.133121 2021] [proxy:error] [pid 7396:tid 19752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:26:13.133121 2021] [proxy_http:error] [pid 7396:tid 19752] [client 191.97.14.230:38849] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 13:28:06.482920 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 13:28:06.482920 2021] [proxy:error] [pid 7396:tid 19972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:28:06.482920 2021] [proxy_http:error] [pid 7396:tid 19972] [client 191.97.14.230:49175] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:29:48.600699 2021] [proxy:error] [pid 7396:tid 19796] (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 [Mon Mar 29 13:29:48.600699 2021] [proxy:error] [pid 7396:tid 19796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:29:48.600699 2021] [proxy_http:error] [pid 7396:tid 19796] [client 191.97.14.230:49228] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:30:08.709135 2021] [proxy:error] [pid 7396:tid 19972] (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 [Mon Mar 29 13:30:08.709135 2021] [proxy_http:error] [pid 7396:tid 19972] [client 191.97.14.230:49236] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:32:17.939761 2021] [proxy:error] [pid 7396:tid 19604] (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 [Mon Mar 29 13:32:17.939761 2021] [proxy:error] [pid 7396:tid 19604] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:32:17.939761 2021] [proxy_http:error] [pid 7396:tid 19604] [client 190.84.172.244:64079] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:33:36.657500 2021] [proxy:error] [pid 7396:tid 19916] (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 [Mon Mar 29 13:33:36.657500 2021] [proxy:error] [pid 7396:tid 19916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:33:36.657500 2021] [proxy_http:error] [pid 7396:tid 19916] [client 201.245.192.253:36981] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:33:50.666324 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 13:40:10.916992 2021] [proxy:error] [pid 7396:tid 19596] (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 [Mon Mar 29 13:40:10.916992 2021] [proxy:error] [pid 7396:tid 19596] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:40:10.916992 2021] [proxy_http:error] [pid 7396:tid 19596] [client 181.61.205.206:4388] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 13:40:14.458198 2021] [proxy:error] [pid 7396:tid 20792] (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 [Mon Mar 29 13:40:14.458198 2021] [proxy_http:error] [pid 7396:tid 20792] [client 181.61.205.206:4404] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 13:43:03.375295 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 13:43:38.709357 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 13:43:38.709357 2021] [proxy:error] [pid 7396:tid 19852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:43:38.709357 2021] [proxy_http:error] [pid 7396:tid 19852] [client 201.245.192.253:34033] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 13:44:19.597029 2021] [proxy:error] [pid 7396:tid 19604] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 13:44:23.029035 2021] [proxy:error] [pid 7396:tid 20752] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 13:53:04.756351 2021] [proxy:error] [pid 7396:tid 20720] (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 [Mon Mar 29 13:53:04.756351 2021] [proxy:error] [pid 7396:tid 20720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 13:53:04.756351 2021] [proxy_http:error] [pid 7396:tid 20720] [client 181.59.170.186:64479] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:01:37.529252 2021] [proxy:error] [pid 7396:tid 20320] (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 [Mon Mar 29 14:01:37.529252 2021] [proxy:error] [pid 7396:tid 20320] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:01:37.529252 2021] [proxy_http:error] [pid 7396:tid 20320] [client 201.245.192.253:52268] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:01:38.184453 2021] [proxy:error] [pid 7396:tid 19604] (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 [Mon Mar 29 14:01:38.184453 2021] [proxy_http:error] [pid 7396:tid 19604] [client 201.245.192.253:54024] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:01:59.416090 2021] [proxy:error] [pid 7396:tid 19604] (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 [Mon Mar 29 14:01:59.416090 2021] [proxy:error] [pid 7396:tid 19604] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:01:59.416090 2021] [proxy_http:error] [pid 7396:tid 19604] [client 201.245.192.253:54028] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:03:08.227811 2021] [proxy:error] [pid 7396:tid 20044] (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 [Mon Mar 29 14:03:08.227811 2021] [proxy:error] [pid 7396:tid 20044] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:03:08.227811 2021] [proxy_http:error] [pid 7396:tid 20044] [client 186.29.59.237:52165] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 14:03:37.493463 2021] [proxy:error] [pid 7396:tid 20320] (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 [Mon Mar 29 14:03:37.493463 2021] [proxy:error] [pid 7396:tid 20320] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:03:37.493463 2021] [proxy_http:error] [pid 7396:tid 20320] [client 201.245.192.253:45947] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:08:24.377967 2021] [proxy:error] [pid 7396:tid 21016] (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 [Mon Mar 29 14:08:24.377967 2021] [proxy:error] [pid 7396:tid 21016] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:08:24.377967 2021] [proxy_http:error] [pid 7396:tid 21016] [client 186.29.59.237:52360] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 14:09:14.719255 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 14:09:14.719255 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:09:14.719255 2021] [proxy_http:error] [pid 7396:tid 20084] [client 191.97.14.230:55060] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:11:38.067907 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 14:11:38.067907 2021] [proxy:error] [pid 7396:tid 20216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:11:38.067907 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:52274] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:11:38.099107 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 14:11:38.099107 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:54106] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:11:59.346344 2021] [proxy:error] [pid 7396:tid 20404] (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 [Mon Mar 29 14:11:59.346344 2021] [proxy:error] [pid 7396:tid 20404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:11:59.346344 2021] [proxy_http:error] [pid 7396:tid 20404] [client 201.245.192.253:54110] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:12:05.009154 2021] [proxy:error] [pid 7396:tid 19520] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 14:12:24.509188 2021] [proxy:error] [pid 7396:tid 20116] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 14:12:33.962805 2021] [proxy:error] [pid 7396:tid 19924] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 14:13:31.963707 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 14:13:47.501334 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 14:13:47.501334 2021] [proxy:error] [pid 7396:tid 19852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:13:47.501334 2021] [proxy_http:error] [pid 7396:tid 19852] [client 201.245.192.253:53828] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:18:15.244604 2021] [proxy:error] [pid 7396:tid 20156] (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 [Mon Mar 29 14:18:15.244604 2021] [proxy:error] [pid 7396:tid 20156] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:18:15.244604 2021] [proxy_http:error] [pid 7396:tid 20156] [client 191.106.175.134:45118] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:18:53.761072 2021] [proxy:error] [pid 7396:tid 21016] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 14:19:02.809088 2021] [proxy:error] [pid 7396:tid 20736] (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 [Mon Mar 29 14:19:02.809088 2021] [proxy:error] [pid 7396:tid 20736] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:19:02.809088 2021] [proxy_http:error] [pid 7396:tid 20736] [client 186.29.59.237:52740] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 14:19:11.139503 2021] [proxy:error] [pid 7396:tid 19924] (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 [Mon Mar 29 14:19:11.139503 2021] [proxy:error] [pid 7396:tid 19924] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:19:11.139503 2021] [proxy_http:error] [pid 7396:tid 19924] [client 201.245.192.253:63777] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:19:15.242310 2021] [proxy:error] [pid 7396:tid 21016] (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 [Mon Mar 29 14:19:15.242310 2021] [proxy_http:error] [pid 7396:tid 21016] [client 186.29.59.237:52762] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 14:21:37.608160 2021] [proxy:error] [pid 7396:tid 19852] (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 [Mon Mar 29 14:21:37.608160 2021] [proxy:error] [pid 7396:tid 19852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:21:37.608160 2021] [proxy_http:error] [pid 7396:tid 19852] [client 201.245.192.253:52280] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:21:38.372561 2021] [proxy:error] [pid 7396:tid 19860] (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 [Mon Mar 29 14:21:38.372561 2021] [proxy_http:error] [pid 7396:tid 19860] [client 201.245.192.253:54218] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:21:59.604199 2021] [proxy:error] [pid 7396:tid 19860] (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 [Mon Mar 29 14:21:59.604199 2021] [proxy:error] [pid 7396:tid 19860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:21:59.604199 2021] [proxy_http:error] [pid 7396:tid 19860] [client 201.245.192.253:54222] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:23:36.667569 2021] [proxy:error] [pid 7396:tid 20372] (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 [Mon Mar 29 14:23:36.667569 2021] [proxy:error] [pid 7396:tid 20372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:23:36.667569 2021] [proxy_http:error] [pid 7396:tid 20372] [client 201.245.192.253:35981] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:29:21.131774 2021] [proxy:error] [pid 7396:tid 20116] (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 [Mon Mar 29 14:29:21.131774 2021] [proxy:error] [pid 7396:tid 20116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:29:21.131774 2021] [proxy_http:error] [pid 7396:tid 20116] [client 186.84.20.108:29641] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:30:21.379080 2021] [proxy:error] [pid 7396:tid 20116] (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 [Mon Mar 29 14:30:21.379080 2021] [proxy:error] [pid 7396:tid 20116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:30:21.379080 2021] [proxy_http:error] [pid 7396:tid 20116] [client 201.245.192.253:50563] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:33:36.769423 2021] [proxy:error] [pid 7396:tid 20084] (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 [Mon Mar 29 14:33:36.769423 2021] [proxy:error] [pid 7396:tid 20084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:33:36.769423 2021] [proxy_http:error] [pid 7396:tid 20084] [client 201.245.192.253:49111] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:35:09.511586 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 14:39:06.242002 2021] [proxy:error] [pid 7396:tid 19752] (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 [Mon Mar 29 14:39:06.242002 2021] [proxy:error] [pid 7396:tid 19752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:39:06.242002 2021] [proxy_http:error] [pid 7396:tid 19752] [client 201.245.192.253:54003] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:43:36.606077 2021] [proxy:error] [pid 7396:tid 20216] (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 [Mon Mar 29 14:43:36.606077 2021] [proxy:error] [pid 7396:tid 20216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:43:36.606077 2021] [proxy_http:error] [pid 7396:tid 20216] [client 201.245.192.253:34539] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:46:15.507956 2021] [proxy:error] [pid 7396:tid 20720] (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 [Mon Mar 29 14:46:15.507956 2021] [proxy:error] [pid 7396:tid 20720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:46:15.507956 2021] [proxy_http:error] [pid 7396:tid 20720] [client 179.18.46.226:55416] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:46:30.218781 2021] [proxy:error] [pid 7396:tid 20468] (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 [Mon Mar 29 14:46:30.218781 2021] [proxy_http:error] [pid 7396:tid 20468] [client 179.18.46.226:55388] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:48:10.324157 2021] [proxy:error] [pid 7396:tid 20600] (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 [Mon Mar 29 14:48:10.324157 2021] [proxy:error] [pid 7396:tid 20600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:48:10.324157 2021] [proxy_http:error] [pid 7396:tid 20600] [client 179.18.46.226:55373] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 14:53:35.896729 2021] [proxy:error] [pid 7396:tid 20688] (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 [Mon Mar 29 14:53:35.896729 2021] [proxy:error] [pid 7396:tid 20688] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 14:53:35.896729 2021] [proxy_http:error] [pid 7396:tid 20688] [client 201.245.192.253:43665] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 14:59:44.993377 2021] [cgi:error] [pid 7396:tid 19916] [client 117.194.167.212:50531] script not found or unable to stat: E:/nuevo/htdocs/setup.cgi [Mon Mar 29 15:01:37.641175 2021] [proxy:error] [pid 7396:tid 19916] (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 [Mon Mar 29 15:01:37.641175 2021] [proxy:error] [pid 7396:tid 19916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:01:37.641175 2021] [proxy_http:error] [pid 7396:tid 19916] [client 201.245.192.253:52286] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:01:38.062376 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 15:01:38.062376 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:54430] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:01:44.286787 2021] [mpm_winnt:warn] [pid 7396:tid 21672] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 15:01:59.294013 2021] [proxy:error] [pid 7396:tid 20760] (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 [Mon Mar 29 15:01:59.294013 2021] [proxy:error] [pid 7396:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:01:59.294013 2021] [proxy_http:error] [pid 7396:tid 20760] [client 201.245.192.253:54432] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:03:39.024989 2021] [proxy:error] [pid 7396:tid 19712] (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 [Mon Mar 29 15:03:39.024989 2021] [proxy:error] [pid 7396:tid 19712] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:03:39.024989 2021] [proxy_http:error] [pid 7396:tid 19712] [client 201.245.192.253:41653] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:03:50.288208 2021] [mpm_winnt:warn] [pid 12724:tid 468] AH00445: ThreadsPerChild of 2500 exceeds ThreadLimit of 1920, decreasing to match [Mon Mar 29 15:03:50.335008 2021] [core:warn] [pid 12724:tid 468] AH00098: pid file E:/nuevo/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Mon Mar 29 15:03:50.335008 2021] [auth_digest:notice] [pid 12724:tid 468] AH01757: generating secret for digest authentication ... [Mon Mar 29 15:03:50.522209 2021] [mpm_winnt:notice] [pid 12724:tid 468] AH00455: Apache/2.4.10 (Win32) OpenSSL/1.0.1i configured -- resuming normal operations [Mon Mar 29 15:03:50.522209 2021] [mpm_winnt:notice] [pid 12724:tid 468] AH00456: Apache Lounge VC11 Server built: Jul 17 2014 11:50:08 [Mon Mar 29 15:03:50.522209 2021] [core:notice] [pid 12724:tid 468] AH00094: Command line: 'e:\\nuevo\\apache\\bin\\httpd.exe -d E:/nuevo/apache' [Mon Mar 29 15:03:50.522209 2021] [mpm_winnt:notice] [pid 12724:tid 468] AH00418: Parent: Created child process 5508 AH00548: NameVirtualHost has no effect and will be removed in the next release E:/nuevo/apache/conf/extra/httpd-vhosts.conf:44 [Mon Mar 29 15:03:51.208610 2021] [auth_digest:notice] [pid 5508:tid 480] AH01757: generating secret for digest authentication ... [Mon Mar 29 15:03:51.458210 2021] [mpm_winnt:notice] [pid 5508:tid 480] AH00354: Child: Starting 1920 worker threads. [Mon Mar 29 15:04:26.839072 2021] [proxy:error] [pid 5508:tid 21032] (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 [Mon Mar 29 15:04:26.839072 2021] [proxy:error] [pid 5508:tid 21032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:04:26.839072 2021] [proxy_http:error] [pid 5508:tid 21032] [client 201.245.192.253:54257] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:05:45.900011 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 15:11:38.055030 2021] [proxy:error] [pid 5508:tid 21056] (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 [Mon Mar 29 15:11:38.055030 2021] [proxy:error] [pid 5508:tid 21056] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:11:38.055030 2021] [proxy_http:error] [pid 5508:tid 21056] [client 201.245.192.253:54466] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:11:38.086230 2021] [proxy:error] [pid 5508:tid 21032] (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 [Mon Mar 29 15:11:38.086230 2021] [proxy_http:error] [pid 5508:tid 21032] [client 201.245.192.253:52292] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:11:59.271067 2021] [proxy:error] [pid 5508:tid 21056] (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 [Mon Mar 29 15:11:59.271067 2021] [proxy:error] [pid 5508:tid 21056] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:11:59.271067 2021] [proxy_http:error] [pid 5508:tid 21056] [client 201.245.192.253:54468] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:12:24.184311 2021] [proxy:error] [pid 5508:tid 20808] (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 [Mon Mar 29 15:12:24.184311 2021] [proxy:error] [pid 5508:tid 20808] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:12:24.184311 2021] [proxy_http:error] [pid 5508:tid 20808] [client 190.84.172.244:64476] 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 [Mon Mar 29 15:13:35.944437 2021] [proxy:error] [pid 5508:tid 21080] (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 [Mon Mar 29 15:13:35.944437 2021] [proxy:error] [pid 5508:tid 21080] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:13:35.944437 2021] [proxy_http:error] [pid 5508:tid 21080] [client 201.245.192.253:60747] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:13:46.895656 2021] [proxy:error] [pid 5508:tid 20916] (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 [Mon Mar 29 15:13:46.895656 2021] [proxy:error] [pid 5508:tid 20916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:13:46.895656 2021] [proxy_http:error] [pid 5508:tid 20916] [client 200.122.193.26:54090] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:13:50.873663 2021] [proxy:error] [pid 5508:tid 20800] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:14:28.953330 2021] [proxy:error] [pid 5508:tid 20912] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:15:15.878212 2021] [proxy:error] [pid 5508:tid 21064] (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 [Mon Mar 29 15:15:15.878212 2021] [proxy:error] [pid 5508:tid 21064] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:15:15.878212 2021] [proxy_http:error] [pid 5508:tid 21064] [client 200.122.193.26:54136] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:17:56.964095 2021] [proxy:error] [pid 5508:tid 20912] (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 [Mon Mar 29 15:17:56.964095 2021] [proxy:error] [pid 5508:tid 20912] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:17:56.964095 2021] [proxy_http:error] [pid 5508:tid 20912] [client 200.122.193.26:54170] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:18:44.122978 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 15:21:37.657683 2021] [proxy:error] [pid 5508:tid 20800] (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 [Mon Mar 29 15:21:37.657683 2021] [proxy:error] [pid 5508:tid 20800] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:21:37.657683 2021] [proxy_http:error] [pid 5508:tid 20800] [client 201.245.192.253:52298] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:21:38.188084 2021] [proxy:error] [pid 5508:tid 20936] (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 [Mon Mar 29 15:21:38.188084 2021] [proxy_http:error] [pid 5508:tid 20936] [client 201.245.192.253:54560] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:21:59.419721 2021] [proxy:error] [pid 5508:tid 20936] (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 [Mon Mar 29 15:21:59.419721 2021] [proxy:error] [pid 5508:tid 20936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:21:59.419721 2021] [proxy_http:error] [pid 5508:tid 20936] [client 201.245.192.253:54562] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:23:36.888692 2021] [proxy:error] [pid 5508:tid 20736] (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 [Mon Mar 29 15:23:36.888692 2021] [proxy:error] [pid 5508:tid 20736] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:23:36.888692 2021] [proxy_http:error] [pid 5508:tid 20736] [client 201.245.192.253:48401] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:25:20.301274 2021] [proxy:error] [pid 5508:tid 20992] (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 [Mon Mar 29 15:25:20.301274 2021] [proxy:error] [pid 5508:tid 20992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:25:20.301274 2021] [proxy_http:error] [pid 5508:tid 20992] [client 200.122.193.26:54240] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:25:32.718896 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:25:51.064528 2021] [proxy:error] [pid 5508:tid 20916] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:26:00.923745 2021] [proxy:error] [pid 5508:tid 20872] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:26:42.482218 2021] [proxy:error] [pid 5508:tid 21096] (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 [Mon Mar 29 15:26:42.482218 2021] [proxy:error] [pid 5508:tid 21096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:26:42.482218 2021] [proxy_http:error] [pid 5508:tid 21096] [client 190.130.85.109:13090] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:26:42.841019 2021] [proxy:error] [pid 5508:tid 21096] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:26:52.778237 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:27:02.341053 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:27:06.553061 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:27:10.172267 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:27:22.043888 2021] [proxy:error] [pid 5508:tid 20744] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:27:41.372322 2021] [proxy:error] [pid 5508:tid 20680] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:28:11.480375 2021] [proxy:error] [pid 5508:tid 20680] (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 [Mon Mar 29 15:28:11.480375 2021] [proxy:error] [pid 5508:tid 20680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:28:11.480375 2021] [proxy_http:error] [pid 5508:tid 20680] [client 190.130.85.109:13110] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:28:21.869993 2021] [proxy:error] [pid 5508:tid 20736] (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 [Mon Mar 29 15:28:21.869993 2021] [proxy_http:error] [pid 5508:tid 20736] [client 190.130.85.109:13100] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:29:05.643670 2021] [proxy:error] [pid 5508:tid 20736] (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 [Mon Mar 29 15:29:05.643670 2021] [proxy:error] [pid 5508:tid 20736] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:29:05.643670 2021] [proxy_http:error] [pid 5508:tid 20736] [client 190.130.85.109:13050] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:29:50.088148 2021] [proxy:error] [pid 5508:tid 20712] (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 [Mon Mar 29 15:29:50.088148 2021] [proxy:error] [pid 5508:tid 20712] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:29:50.088148 2021] [proxy_http:error] [pid 5508:tid 20712] [client 186.29.59.237:55388] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 15:32:43.622853 2021] [proxy:error] [pid 5508:tid 20992] (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 [Mon Mar 29 15:32:43.622853 2021] [proxy:error] [pid 5508:tid 20992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:32:43.622853 2021] [proxy_http:error] [pid 5508:tid 20992] [client 190.130.85.109:13098] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:33:36.319745 2021] [proxy:error] [pid 5508:tid 20760] (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 [Mon Mar 29 15:33:36.319745 2021] [proxy:error] [pid 5508:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:33:36.319745 2021] [proxy_http:error] [pid 5508:tid 20760] [client 201.245.192.253:55089] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:34:33.603046 2021] [proxy:error] [pid 5508:tid 20860] (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 [Mon Mar 29 15:34:33.603046 2021] [proxy:error] [pid 5508:tid 20860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:34:33.603046 2021] [proxy_http:error] [pid 5508:tid 20860] [client 186.29.59.237:55575] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 15:37:46.122984 2021] [proxy:error] [pid 5508:tid 20860] (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 [Mon Mar 29 15:37:46.122984 2021] [proxy:error] [pid 5508:tid 20860] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:37:46.122984 2021] [proxy_http:error] [pid 5508:tid 20860] [client 186.154.97.255:51379] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:41:07.098137 2021] [proxy:error] [pid 5508:tid 20712] (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 [Mon Mar 29 15:41:07.098137 2021] [proxy:error] [pid 5508:tid 20712] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:41:07.098137 2021] [proxy_http:error] [pid 5508:tid 20712] [client 190.130.85.109:13086] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:41:20.498561 2021] [proxy:error] [pid 5508:tid 20552] (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 [Mon Mar 29 15:41:20.498561 2021] [proxy_http:error] [pid 5508:tid 20552] [client 190.130.85.109:13100] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:41:26.707371 2021] [proxy:error] [pid 5508:tid 20768] (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 [Mon Mar 29 15:41:26.707371 2021] [proxy_http:error] [pid 5508:tid 20768] [client 190.130.85.109:13064] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:42:05.067839 2021] [proxy:error] [pid 5508:tid 20768] (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 [Mon Mar 29 15:42:05.067839 2021] [proxy:error] [pid 5508:tid 20768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:42:05.067839 2021] [proxy_http:error] [pid 5508:tid 20768] [client 190.130.85.109:13090] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:42:14.037855 2021] [proxy:error] [pid 5508:tid 20660] (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 [Mon Mar 29 15:42:14.037855 2021] [proxy_http:error] [pid 5508:tid 20660] [client 190.130.85.109:13108] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:42:41.431503 2021] [proxy:error] [pid 5508:tid 20760] (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 [Mon Mar 29 15:42:41.431503 2021] [proxy:error] [pid 5508:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:42:41.431503 2021] [proxy_http:error] [pid 5508:tid 20760] [client 190.130.85.109:13058] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:42:58.482333 2021] [proxy:error] [pid 5508:tid 20660] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:43:38.278003 2021] [proxy:error] [pid 5508:tid 20936] (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 [Mon Mar 29 15:43:38.278003 2021] [proxy:error] [pid 5508:tid 20936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:43:38.278003 2021] [proxy_http:error] [pid 5508:tid 20936] [client 201.245.192.253:34113] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:44:12.535663 2021] [proxy:error] [pid 5508:tid 20760] (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 [Mon Mar 29 15:44:12.535663 2021] [proxy:error] [pid 5508:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:44:12.535663 2021] [proxy_http:error] [pid 5508:tid 20760] [client 190.130.85.109:13026] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:44:14.938067 2021] [proxy:error] [pid 5508:tid 20696] (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 [Mon Mar 29 15:44:14.938067 2021] [proxy_http:error] [pid 5508:tid 20696] [client 190.130.85.109:13118] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 15:45:40.597817 2021] [proxy:error] [pid 5508:tid 20752] (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 [Mon Mar 29 15:45:40.597817 2021] [proxy:error] [pid 5508:tid 20752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:45:40.597817 2021] [proxy_http:error] [pid 5508:tid 20752] [client 186.29.59.237:56114] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://localhost:3000/ [Mon Mar 29 15:51:06.841190 2021] [proxy:error] [pid 5508:tid 20616] (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 [Mon Mar 29 15:51:06.841190 2021] [proxy:error] [pid 5508:tid 20616] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:51:06.841190 2021] [proxy_http:error] [pid 5508:tid 20616] [client 201.245.192.253:63036] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:52:04.795292 2021] [proxy:error] [pid 5508:tid 20784] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 15:53:37.116254 2021] [proxy:error] [pid 5508:tid 20936] (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 [Mon Mar 29 15:53:37.116254 2021] [proxy:error] [pid 5508:tid 20936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:53:37.116254 2021] [proxy_http:error] [pid 5508:tid 20936] [client 201.245.192.253:55219] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 15:55:31.823256 2021] [proxy:error] [pid 5508:tid 20760] (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 [Mon Mar 29 15:55:31.823256 2021] [proxy:error] [pid 5508:tid 20760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 15:55:31.823256 2021] [proxy_http:error] [pid 5508:tid 20760] [client 201.245.192.253:51233] AH01114: HTTP: failed to make connection to backend: 172.22.1.16, referer: http://www.ambientebogota.gov.co/ [Mon Mar 29 16:01:37.394298 2021] [proxy:error] [pid 5508:tid 20512] (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 [Mon Mar 29 16:01:37.394298 2021] [proxy:error] [pid 5508:tid 20512] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 16:01:37.394298 2021] [proxy_http:error] [pid 5508:tid 20512] [client 201.245.192.253:54922] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:01:37.597098 2021] [proxy:error] [pid 5508:tid 20512] AH00940: HTTP: disabled connection for (172.22.1.16) [Mon Mar 29 16:01:37.831099 2021] [proxy:error] [pid 5508:tid 20760] (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 [Mon Mar 29 16:01:37.831099 2021] [proxy_http:error] [pid 5508:tid 20760] [client 201.245.192.253:52304] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:02:22.415977 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 16:03:46.266124 2021] [proxy:error] [pid 5508:tid 21072] (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 [Mon Mar 29 16:03:46.266124 2021] [proxy:error] [pid 5508:tid 21072] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 16:03:46.266124 2021] [proxy_http:error] [pid 5508:tid 21072] [client 186.84.20.108:37047] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:11:37.324552 2021] [proxy:error] [pid 5508:tid 20720] (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 [Mon Mar 29 16:11:37.324552 2021] [proxy:error] [pid 5508:tid 20720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 16:11:37.324552 2021] [proxy_http:error] [pid 5508:tid 20720] [client 201.245.192.253:52310] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:11:37.854953 2021] [proxy:error] [pid 5508:tid 20540] (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 [Mon Mar 29 16:11:37.854953 2021] [proxy_http:error] [pid 5508:tid 20540] [client 201.245.192.253:55004] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:11:59.086590 2021] [proxy:error] [pid 5508:tid 20540] (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 [Mon Mar 29 16:11:59.086590 2021] [proxy:error] [pid 5508:tid 20540] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 16:11:59.086590 2021] [proxy_http:error] [pid 5508:tid 20540] [client 201.245.192.253:55006] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:13:35.697560 2021] [proxy:error] [pid 5508:tid 20488] (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 [Mon Mar 29 16:13:35.697560 2021] [proxy:error] [pid 5508:tid 20488] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s [Mon Mar 29 16:13:35.697560 2021] [proxy_http:error] [pid 5508:tid 20488] [client 201.245.192.253:59099] AH01114: HTTP: failed to make connection to backend: 172.22.1.16 [Mon Mar 29 16:20:34.636295 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 17:00:46.150931 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 17:15:24.073673 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 17:48:06.042319 2021] [cgi:error] [pid 5508:tid 20380] [client 117.222.170.14:38641] script not found or unable to stat: E:/nuevo/htdocs/setup.cgi [Mon Mar 29 17:53:20.476471 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 18:01:08.212093 2021] [proxy_http:error] [pid 5508:tid 20648] (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. : [client 186.29.59.237:57370] AH01102: error reading status line from remote server 172.22.1.16:18080, referer: http://localhost:3000/ [Mon Mar 29 18:01:08.212093 2021] [proxy:error] [pid 5508:tid 20648] [client 186.29.59.237:57370] AH00898: Error reading from remote server returned by /kwssiamovil/sm/des/cjson/pre, referer: http://localhost:3000/ [Mon Mar 29 18:01:08.227693 2021] [proxy_http:error] [pid 5508:tid 20316] (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. : [client 186.29.59.237:57373] AH01102: error reading status line from remote server 172.22.1.16:18080, referer: http://localhost:3000/ [Mon Mar 29 18:01:08.227693 2021] [proxy:error] [pid 5508:tid 20316] [client 186.29.59.237:57373] AH00898: Error reading from remote server returned by /kwssiamovil/sm/des/cjson/pre, referer: http://localhost:3000/ [Mon Mar 29 18:01:08.227693 2021] [proxy_http:error] [pid 5508:tid 20680] (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. : [client 186.29.59.237:57372] AH01102: error reading status line from remote server 172.22.1.16:18080, referer: http://localhost:3000/ [Mon Mar 29 18:01:08.227693 2021] [proxy:error] [pid 5508:tid 20680] [client 186.29.59.237:57372] AH00898: Error reading from remote server returned by /kwssiamovil/sm/des/cjson/pre, referer: http://localhost:3000/ [Mon Mar 29 18:01:16.682908 2021] [proxy_http:error] [pid 5508:tid 20372] (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. : [client 201.245.192.253:55036] AH01102: error reading status line from remote server 172.22.1.16:18080 [Mon Mar 29 18:01:16.682908 2021] [proxy:error] [pid 5508:tid 20372] [client 201.245.192.253:55036] AH00898: Error reading from remote server returned by /kwsrmcab/Wsrmcab [Mon Mar 29 18:01:17.447309 2021] [proxy_http:error] [pid 5508:tid 20324] (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. : [client 201.245.192.253:52318] AH01102: error reading status line from remote server 172.22.1.16:18080 [Mon Mar 29 18:01:17.447309 2021] [proxy:error] [pid 5508:tid 20324] [client 201.245.192.253:52318] AH00898: Error reading from remote server returned by /kwsrmcab/Wsrmcab [Mon Mar 29 18:01:44.965757 2021] [proxy_http:error] [pid 5508:tid 20900] (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. : [client 186.29.59.237:57352] AH01102: error reading status line from remote server 172.22.1.16:18080, referer: http://localhost:3000/ [Mon Mar 29 18:01:44.965757 2021] [proxy:error] [pid 5508:tid 20900] [client 186.29.59.237:57352] AH00898: Error reading from remote server returned by /kwssiamovil/sm/des/cjson/pre, referer: http://localhost:3000/ [Mon Mar 29 18:26:24.409956 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 18:29:18.475062 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 18:46:24.754064 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 19:19:49.419985 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 19:30:51.266748 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 19:36:01.020892 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 20:02:10.102848 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 20:14:37.921361 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 21:07:09.236096 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 21:17:02.645538 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 22:01:57.971472 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 22:38:21.366907 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 22:47:59.909524 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 22:48:58.721627 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 23:00:57.414889 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 23:03:04.243112 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Mon Mar 29 23:24:33.772577 2021] [mpm_winnt:warn] [pid 5508:tid 21368] (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.0468 ]-- |