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: [Wed Feb 28 00:02:00.798419 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:02:31.798192 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:06:58.161427 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:07:29.161200 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:33:30.619510 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:42:21.078851 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:42:52.078624 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:45:54.779074 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:46:25.778847 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 00:54:47.075519 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:12:15.171467 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:12:46.171240 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:22:49.997777 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:27:24.811495 2018] [core:error] [pid 18456:tid 17312] (20024)The given path is misformatted or contained invalid characters: [client 54.36.148.69:50122] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Wed Feb 28 01:33:21.970924 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:33:52.970697 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 01:58:38.865685 2018] [proxy:error] [pid 18456:tid 16932] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 01:58:38.865685 2018] [proxy:error] [pid 18456:tid 16932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 01:58:38.865685 2018] [proxy_http:error] [pid 18456:tid 16932] [client 66.249.64.137:48816] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 02:08:35.398805 2018] [proxy:error] [pid 18456:tid 17376] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 02:08:35.398805 2018] [proxy:error] [pid 18456:tid 17376] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Feb 28 02:08:35.398805 2018] [proxy_http:error] [pid 18456:tid 17376] [client 152.61.128.50:60200] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Feb 28 02:08:35.655820 2018] [proxy:error] [pid 18456:tid 17376] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Feb 28 02:08:35.910834 2018] [proxy:error] [pid 18456:tid 17376] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Feb 28 02:12:00.270523 2018] [proxy:error] [pid 18456:tid 17376] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 02:12:00.270523 2018] [proxy:error] [pid 18456:tid 17376] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 02:12:00.270523 2018] [proxy_http:error] [pid 18456:tid 17376] [client 66.249.64.139:46262] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 02:29:20.993049 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 02:55:07.841524 2018] [core:error] [pid 18456:tid 18012] (20024)The given path is misformatted or contained invalid characters: [client 157.55.39.130:15771] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Wed Feb 28 03:02:42.780545 2018] [proxy:error] [pid 18456:tid 18012] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 03:02:42.780545 2018] [proxy:error] [pid 18456:tid 18012] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Feb 28 03:02:42.780545 2018] [proxy_http:error] [pid 18456:tid 18012] [client 152.61.192.232:36290] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Feb 28 03:02:43.083562 2018] [proxy:error] [pid 18456:tid 18012] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Feb 28 03:02:43.340577 2018] [proxy:error] [pid 18456:tid 18012] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Feb 28 03:22:47.071426 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:23:18.071199 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:29:22.668053 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:29:53.667826 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:32:12.681777 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:32:43.681550 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 03:34:55.208073 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:13:01.282829 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:13:32.282602 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:29:45.071243 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:30:16.072016 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:33:51.710350 2018] [proxy:error] [pid 18456:tid 18208] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 04:33:51.710350 2018] [proxy:error] [pid 18456:tid 18208] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 04:33:51.710350 2018] [proxy_http:error] [pid 18456:tid 18208] [client 66.249.64.141:55959] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 04:55:46.471550 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 04:56:17.471323 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 05:17:23.771751 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 05:17:54.771524 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 05:40:40.472638 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 05:41:11.472411 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 06:32:06.199131 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 06:32:37.198904 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:00:25.973353 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:16:53.186818 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:17:24.186591 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:22:36.387448 2018] [proxy:error] [pid 18456:tid 18012] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 07:22:36.387448 2018] [proxy:error] [pid 18456:tid 18012] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 07:22:36.387448 2018] [proxy_http:error] [pid 18456:tid 18012] [client 201.245.192.253:53321] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/ControlDeInicio.asp [Wed Feb 28 07:23:32.772673 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:28:30.801719 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:28:39.977244 2018] [proxy:error] [pid 18456:tid 16764] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 07:28:39.977244 2018] [proxy:error] [pid 18456:tid 16764] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 07:28:39.977244 2018] [proxy_http:error] [pid 18456:tid 16764] [client 201.245.192.253:56497] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 07:28:44.027476 2018] [proxy:error] [pid 18456:tid 16816] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 07:28:56.690200 2018] [proxy:error] [pid 18456:tid 16816] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 07:30:14.986678 2018] [proxy:error] [pid 18456:tid 18152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 07:30:14.986678 2018] [proxy:error] [pid 18456:tid 18152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 07:30:14.986678 2018] [proxy_http:error] [pid 18456:tid 18152] [client 201.245.192.253:56652] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 07:31:08.829758 2018] [proxy:error] [pid 18456:tid 18148] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 07:32:51.077606 2018] [proxy:error] [pid 18456:tid 17932] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 07:32:51.077606 2018] [proxy:error] [pid 18456:tid 17932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 07:32:51.077606 2018] [proxy_http:error] [pid 18456:tid 17932] [client 201.245.192.253:56721] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 07:33:43.098582 2018] [proxy:error] [pid 18456:tid 17816] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 07:45:43.698798 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 07:46:14.698571 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:00:28.098382 2018] [proxy:error] [pid 18456:tid 16864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:00:28.098382 2018] [proxy:error] [pid 18456:tid 16864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:00:28.098382 2018] [proxy_http:error] [pid 18456:tid 16864] [client 66.249.88.63:58574] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 08:02:04.972923 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:02:35.972696 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:05:15.277808 2018] [proxy:error] [pid 18456:tid 16896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:05:15.277808 2018] [proxy:error] [pid 18456:tid 16896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:05:15.277808 2018] [proxy_http:error] [pid 18456:tid 16896] [client 201.245.192.253:60220] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 08:06:36.335444 2018] [access_compat:error] [pid 18456:tid 17560] [client 66.118.142.167:42765] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/ [Wed Feb 28 08:07:52.172782 2018] [proxy:error] [pid 18456:tid 17560] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:07:52.172782 2018] [proxy:error] [pid 18456:tid 17560] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:07:52.172782 2018] [proxy_http:error] [pid 18456:tid 17560] [client 201.245.192.253:60350] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 08:08:59.889655 2018] [proxy:error] [pid 18456:tid 16756] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:08:59.889655 2018] [proxy:error] [pid 18456:tid 16756] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:08:59.889655 2018] [proxy_http:error] [pid 18456:tid 16756] [client 201.245.192.253:62253] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:12:02.372093 2018] [proxy:error] [pid 18456:tid 17236] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:12:02.372093 2018] [proxy:error] [pid 18456:tid 17236] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:12:02.372093 2018] [proxy_http:error] [pid 18456:tid 17236] [client 186.147.155.208:51694] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:21:16.972814 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:21:47.972587 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:23:31.498508 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:24:02.498281 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:28:07.117273 2018] [proxy:error] [pid 18456:tid 17236] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:28:07.117273 2018] [proxy:error] [pid 18456:tid 17236] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:28:07.117273 2018] [proxy_http:error] [pid 18456:tid 17236] [client 201.245.192.253:53550] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 08:31:11.016791 2018] [proxy:error] [pid 18456:tid 17348] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:31:11.016791 2018] [proxy:error] [pid 18456:tid 17348] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:31:11.016791 2018] [proxy_http:error] [pid 18456:tid 17348] [client 201.245.192.253:49383] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:31:24.030536 2018] [proxy:error] [pid 18456:tid 17348] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 08:33:09.179550 2018] [proxy:error] [pid 18456:tid 17456] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:33:09.179550 2018] [proxy:error] [pid 18456:tid 17456] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:33:09.179550 2018] [proxy_http:error] [pid 18456:tid 17456] [client 201.245.192.253:65078] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:33:12.691751 2018] [proxy:error] [pid 18456:tid 17720] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 08:33:25.698495 2018] [proxy:error] [pid 18456:tid 17312] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:33:25.698495 2018] [proxy:error] [pid 18456:tid 17312] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:33:25.698495 2018] [proxy_http:error] [pid 18456:tid 17312] [client 181.49.243.106:52242] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Wed Feb 28 08:33:25.779499 2018] [proxy:error] [pid 18456:tid 18208] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:33:25.779499 2018] [proxy_http:error] [pid 18456:tid 18208] [client 181.49.243.106:52241] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Wed Feb 28 08:33:58.192353 2018] [proxy:error] [pid 18456:tid 17684] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 08:45:16.880172 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:45:47.879945 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 08:50:09.317898 2018] [proxy:error] [pid 18456:tid 16980] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:50:09.317898 2018] [proxy:error] [pid 18456:tid 16980] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:50:09.317898 2018] [proxy_http:error] [pid 18456:tid 16980] [client 201.245.192.253:59537] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:50:30.204093 2018] [proxy:error] [pid 18456:tid 16900] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 08:55:15.472409 2018] [proxy:error] [pid 18456:tid 17568] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 08:55:15.472409 2018] [proxy:error] [pid 18456:tid 17568] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 08:55:15.472409 2018] [proxy_http:error] [pid 18456:tid 17568] [client 201.245.192.253:53624] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 08:55:24.251912 2018] [proxy:error] [pid 18456:tid 17332] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:02:21.598782 2018] [proxy:error] [pid 18456:tid 17572] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:02:21.598782 2018] [proxy:error] [pid 18456:tid 17572] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:02:21.598782 2018] [proxy_http:error] [pid 18456:tid 17572] [client 201.245.192.253:50155] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:02:34.087497 2018] [proxy:error] [pid 18456:tid 16720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:02:34.087497 2018] [proxy_http:error] [pid 18456:tid 16720] [client 190.27.98.27:53853] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:03:02.399116 2018] [proxy:error] [pid 18456:tid 17028] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:03:02.399116 2018] [proxy:error] [pid 18456:tid 17028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:03:02.399116 2018] [proxy_http:error] [pid 18456:tid 17028] [client 190.27.98.27:53857] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:03:03.203162 2018] [proxy:error] [pid 18456:tid 17024] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:03:08.418460 2018] [proxy:error] [pid 18456:tid 17028] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:03:15.072841 2018] [proxy:error] [pid 18456:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 09:03:15.072841 2018] [proxy_http:error] [pid 18456:tid 18080] [client 201.245.192.253:50201] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:04:08.172878 2018] [proxy:error] [pid 18456:tid 17496] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:04:08.172878 2018] [proxy:error] [pid 18456:tid 17496] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:04:08.172878 2018] [proxy_http:error] [pid 18456:tid 17496] [client 201.245.192.253:52738] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:04:11.874090 2018] [proxy:error] [pid 18456:tid 17496] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:04:13.368175 2018] [core:error] [pid 18456:tid 16960] (20024)The given path is misformatted or contained invalid characters: [client 27.47.232.187:1204] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Wed Feb 28 09:04:14.331230 2018] [core:error] [pid 18456:tid 17112] (20024)The given path is misformatted or contained invalid characters: [client 27.47.232.187:1249] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Wed Feb 28 09:04:15.750312 2018] [core:error] [pid 18456:tid 17112] (20024)The given path is misformatted or contained invalid characters: [client 27.47.232.187:1644] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Wed Feb 28 09:04:16.180336 2018] [proxy:error] [pid 18456:tid 17176] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:04:16.582359 2018] [core:error] [pid 18456:tid 17176] (20024)The given path is misformatted or contained invalid characters: [client 27.47.232.187:1387] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Wed Feb 28 09:04:28.952067 2018] [proxy:error] [pid 18456:tid 17496] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:04:50.224283 2018] [proxy:error] [pid 18456:tid 17888] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:12:12.801597 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 09:12:43.801370 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 09:14:32.775603 2018] [proxy:error] [pid 18456:tid 18148] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 09:14:32.775603 2018] [proxy:error] [pid 18456:tid 18148] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:14:32.775603 2018] [proxy_http:error] [pid 18456:tid 18148] [client 201.245.192.253:49702] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 09:17:28.801671 2018] [proxy:error] [pid 18456:tid 18152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:17:28.801671 2018] [proxy:error] [pid 18456:tid 18152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:17:28.801671 2018] [proxy_http:error] [pid 18456:tid 18152] [client 201.245.192.253:61082] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 09:24:20.501219 2018] [proxy:error] [pid 18456:tid 16816] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:24:20.501219 2018] [proxy:error] [pid 18456:tid 16816] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:24:20.501219 2018] [proxy_http:error] [pid 18456:tid 16816] [client 201.245.192.253:49669] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:24:55.633229 2018] [proxy:error] [pid 18456:tid 17880] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:31:59.897495 2018] [proxy:error] [pid 18456:tid 17112] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:31:59.897495 2018] [proxy:error] [pid 18456:tid 17112] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:31:59.897495 2018] [proxy_http:error] [pid 18456:tid 17112] [client 201.245.192.253:52713] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:32:36.133568 2018] [proxy:error] [pid 18456:tid 17176] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:33:44.998507 2018] [proxy:error] [pid 18456:tid 16720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:33:44.998507 2018] [proxy:error] [pid 18456:tid 16720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:33:44.998507 2018] [proxy_http:error] [pid 18456:tid 16720] [client 190.25.157.12:55536] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://ambientebogota.gov.co/bg/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Wed Feb 28 09:33:54.186032 2018] [proxy:error] [pid 18456:tid 18080] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:34:22.257638 2018] [proxy:error] [pid 18456:tid 17928] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 09:45:46.903797 2018] [proxy:error] [pid 18456:tid 18000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:45:46.903797 2018] [proxy:error] [pid 18456:tid 18000] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:45:46.903797 2018] [proxy_http:error] [pid 18456:tid 18000] [client 201.245.192.253:50072] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:45:52.603123 2018] [proxy:error] [pid 18456:tid 16936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:45:52.603123 2018] [proxy_http:error] [pid 18456:tid 16936] [client 201.245.192.253:57639] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 09:45:53.978202 2018] [proxy:error] [pid 18456:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:45:53.978202 2018] [proxy_http:error] [pid 18456:tid 17088] [client 201.245.192.253:57640] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 09:46:24.307937 2018] [proxy:error] [pid 18456:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:46:24.307937 2018] [proxy:error] [pid 18456:tid 17088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:46:24.307937 2018] [proxy_http:error] [pid 18456:tid 17088] [client 201.245.192.253:57642] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:48:04.242653 2018] [proxy:error] [pid 18456:tid 18000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:48:04.242653 2018] [proxy:error] [pid 18456:tid 18000] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:48:04.242653 2018] [proxy_http:error] [pid 18456:tid 18000] [client 201.245.192.253:57673] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:50:37.078394 2018] [proxy:error] [pid 18456:tid 17280] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:50:37.078394 2018] [proxy:error] [pid 18456:tid 17280] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:50:37.078394 2018] [proxy_http:error] [pid 18456:tid 17280] [client 108.59.10.153:40701] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:57:24.403692 2018] [proxy:error] [pid 18456:tid 16936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:57:24.403692 2018] [proxy:error] [pid 18456:tid 16936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:57:24.403692 2018] [proxy_http:error] [pid 18456:tid 16936] [client 201.245.192.253:49877] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 09:58:50.878638 2018] [proxy:error] [pid 18456:tid 16964] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 09:58:50.878638 2018] [proxy:error] [pid 18456:tid 16964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 09:58:50.878638 2018] [proxy_http:error] [pid 18456:tid 16964] [client 190.27.245.105:27956] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:00:15.215462 2018] [proxy:error] [pid 18456:tid 17368] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:00:15.215462 2018] [proxy:error] [pid 18456:tid 17368] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:00:15.215462 2018] [proxy_http:error] [pid 18456:tid 17368] [client 201.245.192.253:57808] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:01:46.104660 2018] [proxy:error] [pid 18456:tid 17552] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:01:46.104660 2018] [proxy:error] [pid 18456:tid 17552] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:01:46.104660 2018] [proxy_http:error] [pid 18456:tid 17552] [client 152.202.35.249:42655] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:01:46.251669 2018] [proxy:error] [pid 18456:tid 16900] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:01:46.251669 2018] [proxy:error] [pid 18456:tid 16900] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:01:46.251669 2018] [proxy_http:error] [pid 18456:tid 16900] [client 201.245.192.253:53859] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:01:46.286671 2018] [proxy:error] [pid 18456:tid 16900] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:02:00.412479 2018] [proxy:error] [pid 18456:tid 18000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:02:00.413479 2018] [proxy_http:error] [pid 18456:tid 18000] [client 190.27.245.105:28015] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:02:19.339561 2018] [proxy:error] [pid 18456:tid 17332] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:02:48.851249 2018] [proxy:error] [pid 18456:tid 17552] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:02:48.851249 2018] [proxy:error] [pid 18456:tid 17552] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:02:48.851249 2018] [proxy_http:error] [pid 18456:tid 17552] [client 201.245.192.253:58519] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:06:19.414293 2018] [proxy:error] [pid 18456:tid 17644] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:06:19.414293 2018] [proxy:error] [pid 18456:tid 17644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:06:19.414293 2018] [proxy_http:error] [pid 18456:tid 17644] [client 201.245.192.253:49972] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:06:26.618705 2018] [proxy:error] [pid 18456:tid 17628] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:06:47.914923 2018] [proxy:error] [pid 18456:tid 18028] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:07:59.817036 2018] [proxy:error] [pid 18456:tid 17828] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:07:59.817036 2018] [proxy:error] [pid 18456:tid 17828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:07:59.817036 2018] [proxy_http:error] [pid 18456:tid 17828] [client 190.27.245.105:28148] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:08:06.204401 2018] [proxy:error] [pid 18456:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:08:06.204401 2018] [proxy:error] [pid 18456:tid 17088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:08:06.204401 2018] [proxy_http:error] [pid 18456:tid 17088] [client 201.245.192.253:49891] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:08:10.661656 2018] [proxy:error] [pid 18456:tid 17464] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:14.924900 2018] [proxy:error] [pid 18456:tid 17280] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:30.785807 2018] [proxy:error] [pid 18456:tid 17260] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:43.964561 2018] [proxy:error] [pid 18456:tid 17136] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:46.046680 2018] [proxy:error] [pid 18456:tid 17720] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:46.649714 2018] [proxy:error] [pid 18456:tid 17952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:46.945731 2018] [proxy:error] [pid 18456:tid 18160] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:47.195746 2018] [proxy:error] [pid 18456:tid 17952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:47.545766 2018] [proxy:error] [pid 18456:tid 17720] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:08:49.513878 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:08:56.713290 2018] [proxy:error] [pid 18456:tid 17952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:09:20.514651 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:09:29.214149 2018] [proxy:error] [pid 18456:tid 16812] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:09:29.214149 2018] [proxy:error] [pid 18456:tid 16812] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:09:29.214149 2018] [proxy_http:error] [pid 18456:tid 16812] [client 152.201.34.19:54474] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:09:46.854158 2018] [proxy:error] [pid 18456:tid 17576] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:09:46.854158 2018] [proxy:error] [pid 18456:tid 17576] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:09:46.854158 2018] [proxy_http:error] [pid 18456:tid 17576] [client 190.27.245.105:28180] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:09:48.154232 2018] [proxy:error] [pid 18456:tid 17852] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:10:05.643232 2018] [proxy:error] [pid 18456:tid 17764] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:11:40.653667 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:12:11.653440 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:14:28.205250 2018] [proxy:error] [pid 18456:tid 17768] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:14:28.205250 2018] [proxy:error] [pid 18456:tid 17768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:14:28.205250 2018] [proxy_http:error] [pid 18456:tid 17768] [client 190.27.245.105:28244] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:15:43.514558 2018] [proxy:error] [pid 18456:tid 17332] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:15:43.514558 2018] [proxy:error] [pid 18456:tid 17332] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:15:43.514558 2018] [proxy_http:error] [pid 18456:tid 17332] [client 190.27.245.105:28290] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:16:02.653652 2018] [proxy:error] [pid 18456:tid 17504] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:16:02.653652 2018] [proxy_http:error] [pid 18456:tid 17504] [client 190.27.245.105:28298] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:16:36.904611 2018] [proxy:error] [pid 18456:tid 17628] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:16:36.904611 2018] [proxy:error] [pid 18456:tid 17628] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:16:36.904611 2018] [proxy_http:error] [pid 18456:tid 17628] [client 190.27.245.105:28312] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:17:09.518477 2018] [proxy:error] [pid 18456:tid 17692] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:17:09.518477 2018] [proxy:error] [pid 18456:tid 17692] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:17:09.518477 2018] [proxy_http:error] [pid 18456:tid 17692] [client 190.27.245.105:28319] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:17:09.702487 2018] [proxy:error] [pid 18456:tid 17532] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:17:18.901013 2018] [proxy:error] [pid 18456:tid 16872] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:20:07.315646 2018] [proxy:error] [pid 18456:tid 17980] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 10:20:07.315646 2018] [proxy:error] [pid 18456:tid 17980] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:20:07.315646 2018] [proxy_http:error] [pid 18456:tid 17980] [client 201.245.192.253:51672] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:20:13.588005 2018] [proxy:error] [pid 18456:tid 17092] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:20:21.704469 2018] [proxy:error] [pid 18456:tid 17644] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:20:21.704469 2018] [proxy_http:error] [pid 18456:tid 17644] [client 152.201.34.19:54967] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:20:43.214699 2018] [proxy:error] [pid 18456:tid 18044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 10:20:43.214699 2018] [proxy:error] [pid 18456:tid 18044] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:20:43.214699 2018] [proxy_http:error] [pid 18456:tid 18044] [client 190.27.245.105:28388] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:20:51.205156 2018] [proxy:error] [pid 18456:tid 17676] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:20:51.205156 2018] [proxy_http:error] [pid 18456:tid 17676] [client 201.245.192.253:51699] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:21:26.215159 2018] [proxy:error] [pid 18456:tid 17676] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:21:26.215159 2018] [proxy:error] [pid 18456:tid 17676] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:21:26.215159 2018] [proxy_http:error] [pid 18456:tid 17676] [client 201.245.192.253:51704] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:23:23.657876 2018] [proxy:error] [pid 18456:tid 17092] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:23:23.657876 2018] [proxy:error] [pid 18456:tid 17092] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:23:23.657876 2018] [proxy_http:error] [pid 18456:tid 17092] [client 201.245.192.253:51760] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:23:45.001097 2018] [proxy:error] [pid 18456:tid 17064] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:24:00.129962 2018] [proxy:error] [pid 18456:tid 16720] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:24:05.212253 2018] [proxy:error] [pid 18456:tid 17748] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:24:10.638563 2018] [proxy:error] [pid 18456:tid 16720] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:24:16.968926 2018] [proxy:error] [pid 18456:tid 17860] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:25:50.015247 2018] [proxy:error] [pid 18456:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 10:25:50.015247 2018] [proxy:error] [pid 18456:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:25:50.015247 2018] [proxy_http:error] [pid 18456:tid 17956] [client 190.27.245.105:28498] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:26:05.916157 2018] [proxy:error] [pid 18456:tid 17224] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:26:05.916157 2018] [proxy_http:error] [pid 18456:tid 17224] [client 201.245.192.253:60645] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:26:34.861813 2018] [proxy:error] [pid 18456:tid 17384] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:26:34.861813 2018] [proxy:error] [pid 18456:tid 17384] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:26:34.861813 2018] [proxy_http:error] [pid 18456:tid 17384] [client 201.245.192.253:60646] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:27:09.657803 2018] [proxy:error] [pid 18456:tid 17092] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:27:11.596914 2018] [proxy:error] [pid 18456:tid 18136] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:27:13.216006 2018] [proxy:error] [pid 18456:tid 17644] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:27:46.515911 2018] [proxy:error] [pid 18456:tid 16720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:27:46.515911 2018] [proxy:error] [pid 18456:tid 16720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:27:46.515911 2018] [proxy_http:error] [pid 18456:tid 16720] [client 201.245.192.253:60707] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:33:25.896322 2018] [proxy:error] [pid 18456:tid 16940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:33:25.896322 2018] [proxy:error] [pid 18456:tid 16940] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:33:25.896322 2018] [proxy_http:error] [pid 18456:tid 16940] [client 181.59.250.50:65179] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:33:39.949126 2018] [proxy:error] [pid 18456:tid 18160] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:34:52.907299 2018] [proxy:error] [pid 18456:tid 16940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:34:52.907299 2018] [proxy:error] [pid 18456:tid 16940] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:34:52.907299 2018] [proxy_http:error] [pid 18456:tid 16940] [client 190.27.245.105:28665] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:34:53.010305 2018] [proxy:error] [pid 18456:tid 18120] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:34:53.010305 2018] [proxy_http:error] [pid 18456:tid 18120] [client 190.27.245.105:28666] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:34:53.197316 2018] [proxy:error] [pid 18456:tid 16812] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:34:53.197316 2018] [proxy_http:error] [pid 18456:tid 16812] [client 190.27.245.105:28667] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:34:53.417328 2018] [proxy:error] [pid 18456:tid 17304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:34:53.417328 2018] [proxy_http:error] [pid 18456:tid 17304] [client 190.27.245.105:28668] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:35:37.879871 2018] [core:error] [pid 18456:tid 17404] (20024)The given path is misformatted or contained invalid characters: [client 190.27.245.105:28700] AH00127: Cannot map GET /isolucionsda:80:80/ HTTP/1.1 to file [Wed Feb 28 10:36:04.007366 2018] [proxy:error] [pid 18456:tid 17404] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:36:04.007366 2018] [proxy:error] [pid 18456:tid 17404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:36:04.007366 2018] [proxy_http:error] [pid 18456:tid 17404] [client 190.27.245.105:28700] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:37:50.096434 2018] [proxy:error] [pid 18456:tid 17500] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:37:50.096434 2018] [proxy:error] [pid 18456:tid 17500] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:37:50.096434 2018] [proxy_http:error] [pid 18456:tid 17500] [client 201.245.192.253:50629] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:38:43.260475 2018] [proxy:error] [pid 18456:tid 18172] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:39:19.796564 2018] [proxy:error] [pid 18456:tid 18172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:39:19.796564 2018] [proxy:error] [pid 18456:tid 18172] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:39:19.796564 2018] [proxy_http:error] [pid 18456:tid 18172] [client 190.27.245.105:28742] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:40:39.799140 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:41:10.722909 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:47:22.024146 2018] [proxy:error] [pid 18456:tid 18100] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:47:22.024146 2018] [proxy:error] [pid 18456:tid 18100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:47:22.024146 2018] [proxy_http:error] [pid 18456:tid 18100] [client 201.245.192.253:54458] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:47:22.061148 2018] [proxy:error] [pid 18456:tid 18100] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:49:01.319826 2018] [proxy:error] [pid 18456:tid 18088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:49:01.319826 2018] [proxy:error] [pid 18456:tid 18088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:49:01.319826 2018] [proxy_http:error] [pid 18456:tid 18088] [client 190.27.245.105:28927] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:49:07.924203 2018] [proxy:error] [pid 18456:tid 17060] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:49:07.924203 2018] [proxy_http:error] [pid 18456:tid 17060] [client 152.201.34.19:54601] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:49:09.224278 2018] [proxy:error] [pid 18456:tid 17792] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:49:09.224278 2018] [proxy_http:error] [pid 18456:tid 17792] [client 201.245.192.253:50095] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:49:11.024381 2018] [proxy:error] [pid 18456:tid 17948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:49:11.024381 2018] [proxy_http:error] [pid 18456:tid 17948] [client 201.245.192.253:60809] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:49:11.918432 2018] [proxy:error] [pid 18456:tid 16940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:49:11.918432 2018] [proxy_http:error] [pid 18456:tid 16940] [client 152.201.34.19:54600] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:50:51.809145 2018] [proxy:error] [pid 18456:tid 17760] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:50:51.809145 2018] [proxy:error] [pid 18456:tid 17760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:50:51.809145 2018] [proxy_http:error] [pid 18456:tid 17760] [client 190.27.245.105:28949] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:52:22.623339 2018] [proxy:error] [pid 18456:tid 17192] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:52:22.623339 2018] [proxy:error] [pid 18456:tid 17192] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:52:22.623339 2018] [proxy_http:error] [pid 18456:tid 17192] [client 201.245.192.253:58449] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 10:53:09.619027 2018] [proxy:error] [pid 18456:tid 16904] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:53:18.510536 2018] [proxy:error] [pid 18456:tid 18172] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:55:46.823019 2018] [proxy:error] [pid 18456:tid 17172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:55:46.823019 2018] [proxy:error] [pid 18456:tid 17172] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:55:46.823019 2018] [proxy_http:error] [pid 18456:tid 17172] [client 201.245.192.253:50393] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 10:55:55.429511 2018] [proxy:error] [pid 18456:tid 18144] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:56:19.422884 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 10:57:43.222677 2018] [proxy:error] [pid 18456:tid 17500] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 10:57:43.222677 2018] [proxy:error] [pid 18456:tid 17500] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 10:57:43.222677 2018] [proxy_http:error] [pid 18456:tid 17500] [client 201.245.192.253:50219] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Wed Feb 28 10:58:11.964321 2018] [proxy:error] [pid 18456:tid 18172] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 10:58:23.572985 2018] [proxy:error] [pid 18456:tid 18076] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:00:15.626394 2018] [proxy:error] [pid 18456:tid 17460] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:00:15.626394 2018] [proxy:error] [pid 18456:tid 17460] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:00:15.626394 2018] [proxy_http:error] [pid 18456:tid 17460] [client 201.245.192.253:54831] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:00:23.126823 2018] [proxy:error] [pid 18456:tid 17824] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:00:23.126823 2018] [proxy_http:error] [pid 18456:tid 17824] [client 201.245.192.253:54832] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:00:32.619366 2018] [proxy:error] [pid 18456:tid 16720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:00:32.619366 2018] [proxy_http:error] [pid 18456:tid 16720] [client 201.245.192.253:52009] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://192.168.175.10/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:00:45.368095 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 11:01:09.908498 2018] [proxy:error] [pid 18456:tid 17500] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:01:09.908498 2018] [proxy:error] [pid 18456:tid 17500] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:01:09.908498 2018] [proxy_http:error] [pid 18456:tid 17500] [client 201.245.192.253:52014] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://192.168.175.10/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:01:25.419386 2018] [proxy:error] [pid 18456:tid 17844] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:01:25.419386 2018] [proxy_http:error] [pid 18456:tid 17844] [client 201.245.192.253:54900] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:01:46.628599 2018] [proxy:error] [pid 18456:tid 17844] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:01:46.628599 2018] [proxy:error] [pid 18456:tid 17844] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:01:46.628599 2018] [proxy_http:error] [pid 18456:tid 17844] [client 201.245.192.253:54915] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:01:48.553709 2018] [proxy:error] [pid 18456:tid 18092] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:02:15.857270 2018] [proxy:error] [pid 18456:tid 17736] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:03:12.832529 2018] [proxy:error] [pid 18456:tid 17472] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:03:12.832529 2018] [proxy:error] [pid 18456:tid 17472] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:03:12.832529 2018] [proxy_http:error] [pid 18456:tid 17472] [client 201.245.192.253:63248] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:03:12.863531 2018] [proxy:error] [pid 18456:tid 17472] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:03:17.823815 2018] [proxy:error] [pid 18456:tid 18172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:03:17.823815 2018] [proxy_http:error] [pid 18456:tid 18172] [client 201.245.192.253:52056] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://192.168.175.10/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:03:48.932594 2018] [proxy:error] [pid 18456:tid 17256] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:03:48.932594 2018] [proxy:error] [pid 18456:tid 17256] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:03:48.932594 2018] [proxy_http:error] [pid 18456:tid 17256] [client 201.245.192.253:63253] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:05:55.532835 2018] [proxy:error] [pid 18456:tid 17836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:05:55.532835 2018] [proxy:error] [pid 18456:tid 17836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:05:55.532835 2018] [proxy_http:error] [pid 18456:tid 17836] [client 201.245.192.253:63295] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:07:09.424062 2018] [proxy:error] [pid 18456:tid 17720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:07:09.424062 2018] [proxy:error] [pid 18456:tid 17720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:07:09.424062 2018] [proxy_http:error] [pid 18456:tid 17720] [client 201.245.192.253:61538] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:07:25.032954 2018] [proxy:error] [pid 18456:tid 17848] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:08:27.534529 2018] [proxy:error] [pid 18456:tid 18144] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:08:27.534529 2018] [proxy:error] [pid 18456:tid 18144] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:08:27.534529 2018] [proxy_http:error] [pid 18456:tid 18144] [client 190.27.245.105:29220] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:08:44.235484 2018] [proxy:error] [pid 18456:tid 17744] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:08:44.235484 2018] [proxy_http:error] [pid 18456:tid 17744] [client 152.201.34.19:54909] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:16:52.599417 2018] [proxy:error] [pid 18456:tid 17948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:16:52.599417 2018] [proxy:error] [pid 18456:tid 17948] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:16:52.599417 2018] [proxy_http:error] [pid 18456:tid 17948] [client 190.27.245.105:29386] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:17:08.715339 2018] [proxy:error] [pid 18456:tid 17472] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:17:08.715339 2018] [proxy_http:error] [pid 18456:tid 17472] [client 207.244.79.138:49609] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:19:21.596939 2018] [proxy:error] [pid 18456:tid 17468] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:19:21.596939 2018] [proxy:error] [pid 18456:tid 17468] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:19:21.596939 2018] [proxy_http:error] [pid 18456:tid 17468] [client 190.27.245.105:29436] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:22:24.720413 2018] [proxy:error] [pid 18456:tid 18148] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 11:22:24.720413 2018] [proxy:error] [pid 18456:tid 18148] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:22:24.720413 2018] [proxy_http:error] [pid 18456:tid 18148] [client 201.245.192.253:54537] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:22:50.715900 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php [Wed Feb 28 11:22:50.891910 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php5 [Wed Feb 28 11:22:51.062920 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php-cgi [Wed Feb 28 11:22:51.233930 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php.cgi [Wed Feb 28 11:22:51.412940 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php4 [Wed Feb 28 11:22:51.588950 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/php5-cli [Wed Feb 28 11:22:51.760960 2018] [cgi:error] [pid 18456:tid 17672] [client 85.118.206.11:53748] script not found or unable to stat: E:/nuevo/cgi-bin/test.cgi [Wed Feb 28 11:24:10.827482 2018] [proxy:error] [pid 18456:tid 17376] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:24:10.827482 2018] [proxy:error] [pid 18456:tid 17376] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:24:10.827482 2018] [proxy_http:error] [pid 18456:tid 17376] [client 201.245.192.253:56542] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:25:45.027870 2018] [proxy:error] [pid 18456:tid 17816] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:25:45.027870 2018] [proxy:error] [pid 18456:tid 17816] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:25:45.027870 2018] [proxy_http:error] [pid 18456:tid 17816] [client 201.245.192.253:56991] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:25:46.039928 2018] [proxy:error] [pid 18456:tid 17480] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:25:46.039928 2018] [proxy_http:error] [pid 18456:tid 17480] [client 201.245.192.253:61120] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:27:25.743631 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 11:27:56.745404 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 11:31:02.303018 2018] [proxy:error] [pid 18456:tid 17756] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:31:02.303018 2018] [proxy:error] [pid 18456:tid 17756] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:31:02.303018 2018] [proxy_http:error] [pid 18456:tid 17756] [client 190.27.245.105:29733] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:35:17.022587 2018] [proxy:error] [pid 18456:tid 18160] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 11:35:17.022587 2018] [proxy:error] [pid 18456:tid 18160] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:35:17.022587 2018] [proxy_http:error] [pid 18456:tid 18160] [client 186.28.45.162:49576] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:36:02.249173 2018] [proxy:error] [pid 18456:tid 18156] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:37:42.928932 2018] [proxy:error] [pid 18456:tid 17492] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:37:42.928932 2018] [proxy:error] [pid 18456:tid 17492] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:37:42.928932 2018] [proxy_http:error] [pid 18456:tid 17492] [client 201.245.192.253:49718] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:37:49.860328 2018] [proxy:error] [pid 18456:tid 16920] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:38:26.030397 2018] [proxy:error] [pid 18456:tid 17884] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:39:09.650892 2018] [proxy:error] [pid 18456:tid 17096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:39:09.650892 2018] [proxy:error] [pid 18456:tid 17096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:39:09.650892 2018] [proxy_http:error] [pid 18456:tid 17096] [client 190.159.181.195:49920] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:40:00.076776 2018] [proxy:error] [pid 18456:tid 18192] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:40:03.198955 2018] [proxy:error] [pid 18456:tid 17824] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:40:04.426025 2018] [proxy:error] [pid 18456:tid 17824] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:40:05.580091 2018] [proxy:error] [pid 18456:tid 17276] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:40:05.900109 2018] [proxy:error] [pid 18456:tid 17276] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:40:37.928941 2018] [proxy:error] [pid 18456:tid 16816] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:40:37.928941 2018] [proxy:error] [pid 18456:tid 16816] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:40:37.928941 2018] [proxy_http:error] [pid 18456:tid 16816] [client 152.201.34.19:55285] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:42:12.103328 2018] [proxy:error] [pid 18456:tid 17736] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:42:12.103328 2018] [proxy:error] [pid 18456:tid 17736] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:42:12.103328 2018] [proxy_http:error] [pid 18456:tid 17736] [client 190.27.245.105:30110] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:43:38.629277 2018] [proxy:error] [pid 18456:tid 17776] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:43:38.629277 2018] [proxy:error] [pid 18456:tid 17776] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:43:38.629277 2018] [proxy_http:error] [pid 18456:tid 17776] [client 190.27.245.105:30155] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:46:05.303666 2018] [proxy:error] [pid 18456:tid 16920] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:46:05.303666 2018] [proxy:error] [pid 18456:tid 16920] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:46:05.303666 2018] [proxy_http:error] [pid 18456:tid 16920] [client 201.245.192.253:50474] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:46:10.528965 2018] [proxy:error] [pid 18456:tid 17816] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:46:10.528965 2018] [proxy_http:error] [pid 18456:tid 17816] [client 201.245.192.253:50480] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:46:10.603969 2018] [proxy:error] [pid 18456:tid 16980] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:46:10.603969 2018] [proxy_http:error] [pid 18456:tid 16980] [client 201.245.192.253:50479] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:47:00.955849 2018] [proxy:error] [pid 18456:tid 18140] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 11:47:00.955849 2018] [proxy:error] [pid 18456:tid 18140] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:47:00.955849 2018] [proxy_http:error] [pid 18456:tid 18140] [client 190.27.245.105:30245] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:47:01.803898 2018] [proxy:error] [pid 18456:tid 17108] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:47:01.803898 2018] [proxy:error] [pid 18456:tid 17108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:47:01.803898 2018] [proxy_http:error] [pid 18456:tid 17108] [client 201.245.192.253:50484] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:47:07.612230 2018] [proxy:error] [pid 18456:tid 18140] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:16.332729 2018] [proxy:error] [pid 18456:tid 18140] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:19.574914 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:20.315957 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:20.514968 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:21.262011 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:21.496024 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:25.080229 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:30.933564 2018] [proxy:error] [pid 18456:tid 17640] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:31.774612 2018] [proxy:error] [pid 18456:tid 16952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:47:51.122719 2018] [proxy:error] [pid 18456:tid 17672] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:48:58.423568 2018] [proxy:error] [pid 18456:tid 17140] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:48:58.423568 2018] [proxy:error] [pid 18456:tid 17140] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:48:58.423568 2018] [proxy_http:error] [pid 18456:tid 17140] [client 201.245.192.253:50493] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:52:03.265140 2018] [proxy:error] [pid 18456:tid 16928] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:52:03.265140 2018] [proxy:error] [pid 18456:tid 16928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:52:03.265140 2018] [proxy_http:error] [pid 18456:tid 16928] [client 201.245.192.253:50505] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:52:17.464953 2018] [proxy:error] [pid 18456:tid 18148] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 11:52:17.464953 2018] [proxy:error] [pid 18456:tid 18148] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:52:17.464953 2018] [proxy_http:error] [pid 18456:tid 18148] [client 186.28.45.162:49621] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:52:46.415608 2018] [proxy:error] [pid 18456:tid 16856] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:53:40.828721 2018] [proxy:error] [pid 18456:tid 17360] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:53:40.828721 2018] [proxy:error] [pid 18456:tid 17360] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:53:40.828721 2018] [proxy_http:error] [pid 18456:tid 17360] [client 186.28.45.162:49863] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 11:54:10.813436 2018] [proxy:error] [pid 18456:tid 16952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:54:13.413584 2018] [proxy:error] [pid 18456:tid 16952] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:54:23.591167 2018] [proxy:error] [pid 18456:tid 18208] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 11:56:48.367447 2018] [proxy:error] [pid 18456:tid 17140] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 11:56:48.367447 2018] [proxy:error] [pid 18456:tid 17140] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 11:56:48.367447 2018] [proxy_http:error] [pid 18456:tid 17140] [client 190.27.245.105:30471] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 11:59:01.847082 2018] [core:error] [pid 18456:tid 17320] (20025)The given path contained wildcard characters: [client 51.255.65.21:16456] AH00036: access to /Autoliquidacion/index.php?dir=Solicitud+de+Clasificaci%F3n+de+Impacto+Ambiental%2F failed (filesystem path 'E:/nuevo/htdocs/Autoliquidacion/index.php?dir=Solicitud+de+Clasificaci%F3n+de+Impacto+Ambiental%2F') [Wed Feb 28 12:00:40.223709 2018] [proxy:error] [pid 18456:tid 17460] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:00:40.223709 2018] [proxy:error] [pid 18456:tid 17460] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:00:40.223709 2018] [proxy_http:error] [pid 18456:tid 17460] [client 190.27.245.105:30561] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:01:26.387349 2018] [proxy:error] [pid 18456:tid 17520] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:02:05.198569 2018] [proxy:error] [pid 18456:tid 17820] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:02:05.198569 2018] [proxy:error] [pid 18456:tid 17820] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:02:05.198569 2018] [proxy_http:error] [pid 18456:tid 17820] [client 190.27.245.105:30596] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:03:01.645798 2018] [proxy:error] [pid 18456:tid 17776] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:03:13.636483 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:03:29.201374 2018] [proxy:error] [pid 18456:tid 16984] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:03:29.201374 2018] [proxy:error] [pid 18456:tid 16984] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:03:29.201374 2018] [proxy_http:error] [pid 18456:tid 16984] [client 201.245.192.253:60719] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:03:41.702089 2018] [proxy:error] [pid 18456:tid 17852] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:03:41.702089 2018] [proxy_http:error] [pid 18456:tid 17852] [client 201.245.192.253:50128] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 12:03:44.636257 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:04:12.528852 2018] [proxy:error] [pid 18456:tid 16756] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:04:12.528852 2018] [proxy:error] [pid 18456:tid 16756] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:04:12.528852 2018] [proxy_http:error] [pid 18456:tid 16756] [client 201.245.192.253:50130] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 12:04:19.802268 2018] [proxy:error] [pid 18456:tid 18028] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:04:19.802268 2018] [proxy_http:error] [pid 18456:tid 18028] [client 190.27.245.105:30640] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:05:04.018797 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:05:04.023797 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:08:43.436347 2018] [proxy:error] [pid 18456:tid 17140] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:08:43.436347 2018] [proxy:error] [pid 18456:tid 17140] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:08:43.436347 2018] [proxy_http:error] [pid 18456:tid 17140] [client 190.27.245.105:30784] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:13:48.528797 2018] [proxy:error] [pid 18456:tid 17776] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:13:48.528797 2018] [proxy:error] [pid 18456:tid 17776] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:13:48.528797 2018] [proxy_http:error] [pid 18456:tid 17776] [client 190.27.245.105:30923] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:16:53.624384 2018] [proxy:error] [pid 18456:tid 17864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:16:53.624384 2018] [proxy:error] [pid 18456:tid 17864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:16:53.624384 2018] [proxy_http:error] [pid 18456:tid 17864] [client 201.245.192.253:50546] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Wed Feb 28 12:18:53.037214 2018] [proxy:error] [pid 18456:tid 17904] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:18:53.037214 2018] [proxy:error] [pid 18456:tid 17904] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:18:53.037214 2018] [proxy_http:error] [pid 18456:tid 17904] [client 201.245.192.253:51344] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 12:20:40.737374 2018] [proxy:error] [pid 18456:tid 17464] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:20:40.737374 2018] [proxy:error] [pid 18456:tid 17464] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:20:40.737374 2018] [proxy_http:error] [pid 18456:tid 17464] [client 201.245.192.253:49437] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 12:20:56.077252 2018] [proxy:error] [pid 18456:tid 16896] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:21:08.738976 2018] [proxy:error] [pid 18456:tid 16924] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:21:14.837325 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:21:45.837098 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:24:28.329392 2018] [proxy:error] [pid 18456:tid 17904] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:24:28.329392 2018] [proxy:error] [pid 18456:tid 17904] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:24:28.329392 2018] [proxy_http:error] [pid 18456:tid 17904] [client 201.245.192.253:49885] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:26:55.909833 2018] [proxy:error] [pid 18456:tid 17696] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:26:55.909833 2018] [proxy:error] [pid 18456:tid 17696] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:26:55.909833 2018] [proxy_http:error] [pid 18456:tid 17696] [client 201.245.192.253:49939] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:27:21.273284 2018] [proxy:error] [pid 18456:tid 16724] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:27:27.603646 2018] [proxy:error] [pid 18456:tid 17904] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:27:55.451238 2018] [proxy:error] [pid 18456:tid 16960] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:29:52.531935 2018] [proxy:error] [pid 18456:tid 17288] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:29:52.531935 2018] [proxy:error] [pid 18456:tid 17288] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:29:52.531935 2018] [proxy_http:error] [pid 18456:tid 17288] [client 201.245.192.253:50950] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 12:31:22.832100 2018] [proxy:error] [pid 18456:tid 18108] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:31:22.832100 2018] [proxy:error] [pid 18456:tid 18108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:31:22.832100 2018] [proxy_http:error] [pid 18456:tid 18108] [client 201.245.192.253:60795] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:37:48.715171 2018] [proxy:error] [pid 18456:tid 16936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:37:48.715171 2018] [proxy:error] [pid 18456:tid 16936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:37:48.715171 2018] [proxy_http:error] [pid 18456:tid 16936] [client 190.27.245.105:31312] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:38:24.175199 2018] [proxy:error] [pid 18456:tid 17976] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:38:35.945873 2018] [proxy:error] [pid 18456:tid 16940] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:41:24.075489 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:41:54.976257 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 12:42:15.377423 2018] [proxy:error] [pid 18456:tid 17808] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:42:15.377423 2018] [proxy:error] [pid 18456:tid 17808] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:42:15.377423 2018] [proxy_http:error] [pid 18456:tid 17808] [client 201.245.192.253:50911] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:42:19.546662 2018] [proxy:error] [pid 18456:tid 17976] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 12:44:12.948148 2018] [proxy:error] [pid 18456:tid 17776] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:44:12.948148 2018] [proxy:error] [pid 18456:tid 17776] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:44:12.948148 2018] [proxy_http:error] [pid 18456:tid 17776] [client 190.27.245.105:31389] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 12:55:59.533562 2018] [proxy:error] [pid 18456:tid 17368] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 12:55:59.533562 2018] [proxy:error] [pid 18456:tid 17368] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 12:55:59.533562 2018] [proxy_http:error] [pid 18456:tid 17368] [client 66.249.88.33:49841] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 13:01:27.052295 2018] [proxy:error] [pid 18456:tid 17828] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 13:01:27.052295 2018] [proxy:error] [pid 18456:tid 17828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 13:01:27.053295 2018] [proxy_http:error] [pid 18456:tid 17828] [client 170.246.115.186:51616] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 13:15:06.052140 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 13:24:46.630347 2018] [proxy:error] [pid 18456:tid 17744] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 13:24:46.630347 2018] [proxy:error] [pid 18456:tid 17744] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 13:24:46.630347 2018] [proxy_http:error] [pid 18456:tid 17744] [client 201.245.192.253:53653] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 13:33:00.830613 2018] [proxy:error] [pid 18456:tid 17864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 13:33:00.830613 2018] [proxy:error] [pid 18456:tid 17864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 13:33:00.830613 2018] [proxy_http:error] [pid 18456:tid 17864] [client 201.245.192.253:55019] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 13:33:12.130260 2018] [proxy:error] [pid 18456:tid 17344] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 13:33:12.130260 2018] [proxy_http:error] [pid 18456:tid 17344] [client 201.245.192.253:55022] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 13:36:06.230218 2018] [proxy:error] [pid 18456:tid 18160] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 13:36:06.230218 2018] [proxy:error] [pid 18456:tid 18160] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 13:36:06.230218 2018] [proxy_http:error] [pid 18456:tid 18160] [client 201.245.192.253:55037] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 13:49:02.549621 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 13:49:33.550394 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 14:06:51.938786 2018] [proxy:error] [pid 18456:tid 17108] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:06:51.938786 2018] [proxy:error] [pid 18456:tid 17108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:06:51.938786 2018] [proxy_http:error] [pid 18456:tid 17108] [client 201.245.192.253:63665] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:06:59.779235 2018] [proxy:error] [pid 18456:tid 16768] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:07:36.725348 2018] [proxy:error] [pid 18456:tid 16864] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:08:22.638974 2018] [proxy:error] [pid 18456:tid 18132] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:08:22.638974 2018] [proxy:error] [pid 18456:tid 18132] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:08:22.638974 2018] [proxy_http:error] [pid 18456:tid 18132] [client 201.245.192.253:57346] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:08:41.894075 2018] [proxy:error] [pid 18456:tid 17108] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:08:53.083715 2018] [proxy:error] [pid 18456:tid 17744] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:09:04.925392 2018] [proxy:error] [pid 18456:tid 17088] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:09:44.630664 2018] [proxy:error] [pid 18456:tid 18188] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:09:44.630664 2018] [proxy:error] [pid 18456:tid 18188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:09:44.630664 2018] [proxy_http:error] [pid 18456:tid 18188] [client 201.245.192.253:57383] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:10:00.114549 2018] [proxy:error] [pid 18456:tid 17096] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:11:54.231076 2018] [proxy:error] [pid 18456:tid 17732] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:11:54.231076 2018] [proxy:error] [pid 18456:tid 17732] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:11:54.231076 2018] [proxy_http:error] [pid 18456:tid 17732] [client 201.245.192.253:60323] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://192.168.175.10/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:14:59.890695 2018] [proxy:error] [pid 18456:tid 18144] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:14:59.890695 2018] [proxy:error] [pid 18456:tid 18144] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:14:59.890695 2018] [proxy_http:error] [pid 18456:tid 18144] [client 201.245.192.253:54087] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:15:28.496331 2018] [proxy:error] [pid 18456:tid 17672] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:18:13.328759 2018] [proxy:error] [pid 18456:tid 18028] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:18:13.328759 2018] [proxy:error] [pid 18456:tid 18028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:18:13.328759 2018] [proxy_http:error] [pid 18456:tid 18028] [client 201.245.192.253:64078] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:20:41.747248 2018] [proxy:error] [pid 18456:tid 17064] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:20:41.747248 2018] [proxy:error] [pid 18456:tid 17064] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:20:41.747248 2018] [proxy_http:error] [pid 18456:tid 17064] [client 201.245.192.253:54230] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:25:18.000049 2018] [proxy:error] [pid 18456:tid 17304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:25:18.000049 2018] [proxy:error] [pid 18456:tid 17304] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:25:18.000049 2018] [proxy_http:error] [pid 18456:tid 17304] [client 190.27.245.105:32950] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 14:26:29.031112 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 14:27:00.032885 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 14:29:39.835025 2018] [proxy:error] [pid 18456:tid 17924] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:29:39.835025 2018] [proxy:error] [pid 18456:tid 17924] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:29:39.835025 2018] [proxy_http:error] [pid 18456:tid 17924] [client 201.245.192.253:54257] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:31:30.651364 2018] [proxy:error] [pid 18456:tid 17468] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:31:30.651364 2018] [proxy:error] [pid 18456:tid 17468] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:31:30.651364 2018] [proxy_http:error] [pid 18456:tid 17468] [client 201.245.192.253:60815] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:36:06.019114 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 14:36:37.018887 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 14:41:22.070191 2018] [proxy:error] [pid 18456:tid 18152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:41:22.070191 2018] [proxy:error] [pid 18456:tid 18152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:41:22.070191 2018] [proxy_http:error] [pid 18456:tid 18152] [client 201.245.192.253:61864] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:41:51.238859 2018] [proxy:error] [pid 18456:tid 17468] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:42:12.996104 2018] [proxy:error] [pid 18456:tid 17868] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:42:56.337583 2018] [proxy:error] [pid 18456:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:42:56.337583 2018] [proxy:error] [pid 18456:tid 17088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:42:56.337583 2018] [proxy_http:error] [pid 18456:tid 17088] [client 201.245.192.253:55439] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:43:10.270380 2018] [proxy:error] [pid 18456:tid 17176] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:43:10.270380 2018] [proxy_http:error] [pid 18456:tid 17176] [client 201.245.192.253:55446] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:43:13.237549 2018] [proxy:error] [pid 18456:tid 16764] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:43:13.237549 2018] [proxy_http:error] [pid 18456:tid 16764] [client 201.245.192.253:61870] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:43:39.670061 2018] [proxy:error] [pid 18456:tid 17348] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:43:39.670061 2018] [proxy:error] [pid 18456:tid 17348] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:43:39.670061 2018] [proxy_http:error] [pid 18456:tid 17348] [client 201.245.192.253:55447] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:43:51.067713 2018] [proxy:error] [pid 18456:tid 17116] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:43:53.234837 2018] [proxy:error] [pid 18456:tid 17844] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 14:46:14.614923 2018] [proxy:error] [pid 18456:tid 17176] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:46:14.614923 2018] [proxy:error] [pid 18456:tid 17176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:46:14.614923 2018] [proxy_http:error] [pid 18456:tid 17176] [client 201.245.192.253:55469] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:52:16.457620 2018] [proxy:error] [pid 18456:tid 17356] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:52:16.457620 2018] [proxy:error] [pid 18456:tid 17356] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:52:16.457620 2018] [proxy_http:error] [pid 18456:tid 17356] [client 201.245.192.253:61896] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:54:47.238244 2018] [proxy:error] [pid 18456:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 14:54:47.238244 2018] [proxy:error] [pid 18456:tid 17088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 14:54:47.238244 2018] [proxy_http:error] [pid 18456:tid 17088] [client 201.245.192.253:51644] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 14:55:03.024147 2018] [proxy:error] [pid 18456:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 14:55:03.024147 2018] [proxy_http:error] [pid 18456:tid 17956] [client 201.245.192.253:51645] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 15:01:37.429705 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:02:08.430479 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:05:13.159044 2018] [proxy:error] [pid 18456:tid 17108] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:05:13.159044 2018] [proxy:error] [pid 18456:tid 17108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:05:13.159044 2018] [proxy_http:error] [pid 18456:tid 17108] [client 201.245.192.253:60953] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 15:05:31.382087 2018] [proxy:error] [pid 18456:tid 17064] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 15:13:42.646185 2018] [proxy:error] [pid 18456:tid 16984] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:13:42.646185 2018] [proxy:error] [pid 18456:tid 16984] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:13:42.646185 2018] [proxy_http:error] [pid 18456:tid 16984] [client 201.245.192.253:50512] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 15:13:52.637757 2018] [proxy:error] [pid 18456:tid 16992] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:13:52.637757 2018] [proxy:error] [pid 18456:tid 16992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:13:52.637757 2018] [proxy_http:error] [pid 18456:tid 16992] [client 66.249.88.33:38111] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 15:13:58.346083 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:14:29.345857 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:23:14.162874 2018] [proxy:error] [pid 18456:tid 17968] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Feb 28 15:23:14.163874 2018] [proxy:error] [pid 18456:tid 17968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:23:14.163874 2018] [proxy_http:error] [pid 18456:tid 17968] [client 201.245.192.253:63079] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 15:24:05.253797 2018] [proxy:error] [pid 18456:tid 17052] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:24:05.253797 2018] [proxy:error] [pid 18456:tid 17052] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:24:05.253797 2018] [proxy_http:error] [pid 18456:tid 17052] [client 201.245.192.253:50565] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 15:32:16.063869 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:32:24.044326 2018] [proxy:error] [pid 18456:tid 16744] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:32:24.044326 2018] [proxy:error] [pid 18456:tid 16744] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:32:24.044326 2018] [proxy_http:error] [pid 18456:tid 16744] [client 201.245.192.253:51460] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Wed Feb 28 15:32:47.063642 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 15:47:28.420053 2018] [cgi:error] [pid 18456:tid 17480] [client 177.142.183.124:41727] script not found or unable to stat: E:/nuevo/htdocs/hndUnblock.cgi [Wed Feb 28 15:49:22.818596 2018] [proxy:error] [pid 18456:tid 18136] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 15:49:22.818596 2018] [proxy:error] [pid 18456:tid 18136] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 15:49:22.818596 2018] [proxy_http:error] [pid 18456:tid 18136] [client 186.29.248.72:57225] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 15:49:33.578212 2018] [proxy:error] [pid 18456:tid 17004] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 15:49:49.266109 2018] [proxy:error] [pid 18456:tid 17676] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 15:59:46.700280 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 16:14:52.946115 2018] [proxy:error] [pid 18456:tid 17696] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 16:14:52.946115 2018] [proxy:error] [pid 18456:tid 17696] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 16:14:52.946115 2018] [proxy_http:error] [pid 18456:tid 17696] [client 177.252.250.182:58233] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Feb 28 16:15:41.334882 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 16:20:41.236036 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 16:25:31.648646 2018] [proxy:error] [pid 18456:tid 17652] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 16:25:31.648646 2018] [proxy:error] [pid 18456:tid 17652] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 16:25:31.648646 2018] [proxy_http:error] [pid 18456:tid 17652] [client 152.201.51.210:43140] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 16:25:32.011667 2018] [proxy:error] [pid 18456:tid 17652] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 16:25:49.295656 2018] [proxy:error] [pid 18456:tid 17304] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 16:26:22.974582 2018] [proxy:error] [pid 18456:tid 16968] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 16:37:22.879326 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 16:51:26.846599 2018] [proxy:error] [pid 18456:tid 16956] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 16:51:26.846599 2018] [proxy:error] [pid 18456:tid 16956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 16:51:26.846599 2018] [proxy_http:error] [pid 18456:tid 16956] [client 66.249.69.150:61624] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:02:27.781402 2018] [proxy:error] [pid 18456:tid 16960] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed [Wed Feb 28 17:02:27.781402 2018] [proxy:error] [pid 18456:tid 16960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.32) for 60s [Wed Feb 28 17:02:27.781402 2018] [proxy_http:error] [pid 18456:tid 16960] [client 201.245.192.253:51223] AH01114: HTTP: failed to make connection to backend: 172.22.1.32 [Wed Feb 28 17:02:31.946640 2018] [proxy:error] [pid 18456:tid 18040] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed [Wed Feb 28 17:02:31.946640 2018] [proxy_http:error] [pid 18456:tid 18040] [client 201.245.192.253:51224] AH01114: HTTP: failed to make connection to backend: 172.22.1.32 [Wed Feb 28 17:06:52.646551 2018] [cgi:error] [pid 18456:tid 16724] (OS 10060)A connection attempt failed 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 192.168.171.68:51335] AH01224: Timeout during reading request entity data, referer: http://172.22.2.2/BLA/boletinlegal/ADMIN/actos/ingresar.php [Wed Feb 28 17:11:30.669453 2018] [cgi:error] [pid 18456:tid 17192] (OS 10060)A connection attempt failed 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 192.168.171.68:51350] AH01224: Timeout during reading request entity data, referer: http://172.22.2.2/BLA/boletinlegal/ADMIN/actos/ingresar.php [Wed Feb 28 17:11:41.844092 2018] [cgi:error] [pid 18456:tid 18184] (OS 10060)A connection attempt failed 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 192.168.171.68:51351] AH01224: Timeout during reading request entity data, referer: http://172.22.2.2/BLA/boletinlegal/ADMIN/actos/ingresar.php [Wed Feb 28 17:15:09.785986 2018] [proxy:error] [pid 18456:tid 16936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:15:09.785986 2018] [proxy:error] [pid 18456:tid 16936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 17:15:09.785986 2018] [proxy_http:error] [pid 18456:tid 16936] [client 66.249.88.63:47571] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:26:35.947232 2018] [proxy:error] [pid 18456:tid 17220] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:26:35.947232 2018] [proxy:error] [pid 18456:tid 17220] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 17:26:35.947232 2018] [proxy_http:error] [pid 18456:tid 17220] [client 190.60.224.146:45557] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:26:54.203276 2018] [proxy:error] [pid 18456:tid 18064] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 17:27:35.764654 2018] [proxy:error] [pid 18456:tid 17872] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Feb 28 17:53:07.184246 2018] [proxy:error] [pid 18456:tid 17928] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:53:07.184246 2018] [proxy:error] [pid 18456:tid 17928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 17:53:07.184246 2018] [proxy_http:error] [pid 18456:tid 17928] [client 201.245.192.253:51936] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:53:11.201475 2018] [proxy:error] [pid 18456:tid 17220] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:53:11.201475 2018] [proxy_http:error] [pid 18456:tid 17220] [client 201.245.192.253:51937] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:55:46.308347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.308347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.308347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.309347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.309347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.309347 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:55:46.318348 2018] [mpm_winnt:warn] [pid 18456:tid 18908] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 17:58:05.548311 2018] [proxy:error] [pid 18456:tid 18072] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:58:05.548311 2018] [proxy:error] [pid 18456:tid 18072] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 17:58:05.548311 2018] [proxy_http:error] [pid 18456:tid 18072] [client 201.245.192.253:54206] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 17:58:11.584656 2018] [proxy:warn] [pid 18696:tid 196] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Feb 28 17:58:11.589657 2018] [mpm_winnt:warn] [pid 18696:tid 196] AH00445: ThreadsPerChild of 2500 exceeds ThreadLimit of 1920, decreasing to match [Wed Feb 28 17:58:11.651660 2018] [core:warn] [pid 18696:tid 196] AH00098: pid file E:/nuevo/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Wed Feb 28 17:58:11.653660 2018] [auth_digest:notice] [pid 18696:tid 196] AH01757: generating secret for digest authentication ... [Wed Feb 28 17:58:11.862672 2018] [mpm_winnt:notice] [pid 18696:tid 196] AH00455: Apache/2.4.10 (Win32) OpenSSL/1.0.1i configured -- resuming normal operations [Wed Feb 28 17:58:11.862672 2018] [mpm_winnt:notice] [pid 18696:tid 196] AH00456: Apache Lounge VC11 Server built: Jul 17 2014 11:50:08 [Wed Feb 28 17:58:11.862672 2018] [core:notice] [pid 18696:tid 196] AH00094: Command line: 'e:\\nuevo\\apache\\bin\\httpd.exe -d E:/nuevo/apache' [Wed Feb 28 17:58:11.864672 2018] [mpm_winnt:notice] [pid 18696:tid 196] AH00418: Parent: Created child process 12904 AH00548: NameVirtualHost has no effect and will be removed in the next release E:/nuevo/apache/conf/extra/httpd-vhosts.conf:44 [Wed Feb 28 17:58:12.451706 2018] [proxy:warn] [pid 12904:tid 212] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Feb 28 17:58:12.639717 2018] [proxy:warn] [pid 12904:tid 212] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Feb 28 17:58:12.702720 2018] [auth_digest:notice] [pid 12904:tid 212] AH01757: generating secret for digest authentication ... [Wed Feb 28 17:58:12.924733 2018] [mpm_winnt:notice] [pid 12904:tid 212] AH00354: Child: Starting 1920 worker threads. [Wed Feb 28 17:58:42.903448 2018] [proxy:error] [pid 12904:tid 18304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 17:58:42.903448 2018] [proxy:error] [pid 12904:tid 18304] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 17:58:42.903448 2018] [proxy_http:error] [pid 12904:tid 18304] [client 201.245.192.253:54213] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Feb 28 18:33:10.287695 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/php5 [Wed Feb 28 18:33:10.511708 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/php-cgi [Wed Feb 28 18:33:10.730721 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/php.cgi [Wed Feb 28 18:33:10.948733 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/php4 [Wed Feb 28 18:33:11.163745 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/php5-cli [Wed Feb 28 18:33:11.377758 2018] [cgi:error] [pid 12904:tid 17780] [client 89.19.24.154:33245] script not found or unable to stat: E:/nuevo/cgi-bin/test.cgi [Wed Feb 28 19:05:41.744312 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 21:19:19.207885 2018] [proxy:error] [pid 12904:tid 17484] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Feb 28 21:19:19.207885 2018] [proxy:error] [pid 12904:tid 17484] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Feb 28 21:19:19.207885 2018] [proxy_http:error] [pid 12904:tid 17484] [client 186.28.105.202:25431] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: https://www.bing.com/ [Wed Feb 28 21:42:34.076667 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 21:42:34.077667 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 21:42:34.077667 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 22:25:48.139039 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Feb 28 22:41:28.432821 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (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.3744 ]-- |