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 Nov 25 00:01:09.968564 2015] [cgi:error] [pid 19336:tid 9860] [client 115.230.124.164:1069] script not found or unable to stat: E:/nuevo/cgi-bin/common [Wed Nov 25 01:06:45.107676 2015] [proxy:error] [pid 19336:tid 9968] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:06:45.107676 2015] [proxy:error] [pid 19336:tid 9968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:06:45.107676 2015] [proxy_http:error] [pid 19336:tid 9968] [client 152.61.192.232:51923] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:06:45.326076 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:06:45.560076 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:06:45.794077 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:06:46.012477 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:08:32.389064 2015] [proxy:error] [pid 19336:tid 9380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:08:32.389064 2015] [proxy:error] [pid 19336:tid 9380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:08:32.389064 2015] [proxy_http:error] [pid 19336:tid 9380] [client 152.61.192.232:61968] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:08:32.607464 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:08:32.825865 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:08:33.059865 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:08:33.293866 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:08:33.512266 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:17:44.115233 2015] [proxy:error] [pid 19336:tid 9380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:17:44.115233 2015] [proxy:error] [pid 19336:tid 9380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:17:44.115233 2015] [proxy_http:error] [pid 19336:tid 9380] [client 152.61.193.99:2624] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:17:44.333633 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:17:44.552034 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:17:44.770434 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:17:45.004435 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:17:45.222835 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:18:02.866466 2015] [proxy:error] [pid 19336:tid 9968] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:18:02.866466 2015] [proxy_http:error] [pid 19336:tid 9968] [client 152.61.128.66:34586] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:18:24.130303 2015] [proxy:error] [pid 19336:tid 9968] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:18:24.130303 2015] [proxy:error] [pid 19336:tid 9968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:18:24.130303 2015] [proxy_http:error] [pid 19336:tid 9968] [client 152.61.128.66:35208] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:18:24.348704 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:18:24.567104 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:18:24.801105 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:18:25.019505 2015] [proxy:error] [pid 19336:tid 9968] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:20:52.798565 2015] [proxy:error] [pid 19336:tid 9032] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:20:52.798565 2015] [proxy:error] [pid 19336:tid 9032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:20:52.798565 2015] [proxy_http:error] [pid 19336:tid 9032] [client 152.61.128.66:38830] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:20:53.016965 2015] [proxy:error] [pid 19336:tid 9032] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:20:53.235365 2015] [proxy:error] [pid 19336:tid 9032] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:20:53.453766 2015] [proxy:error] [pid 19336:tid 9032] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:20:53.687766 2015] [proxy:error] [pid 19336:tid 9032] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:37:20.264699 2015] [proxy:error] [pid 19336:tid 9732] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:37:20.264699 2015] [proxy:error] [pid 19336:tid 9732] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:37:20.264699 2015] [proxy_http:error] [pid 19336:tid 9732] [client 152.61.193.99:52878] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:37:20.483099 2015] [proxy:error] [pid 19336:tid 9732] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:37:20.701500 2015] [proxy:error] [pid 19336:tid 9732] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:37:20.919900 2015] [proxy:error] [pid 19336:tid 9732] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:37:21.153900 2015] [proxy:error] [pid 19336:tid 9732] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:48:55.713920 2015] [proxy:error] [pid 19336:tid 10352] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:48:55.713920 2015] [proxy:error] [pid 19336:tid 10352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:48:55.713920 2015] [proxy_http:error] [pid 19336:tid 10352] [client 190.60.94.206:56977] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 01:48:57.429923 2015] [proxy:error] [pid 19336:tid 10352] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:49:10.237546 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:49:11.859949 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:49:55.196825 2015] [proxy:error] [pid 19336:tid 9732] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 01:50:17.832465 2015] [proxy:error] [pid 19336:tid 9732] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 01:50:17.832465 2015] [proxy:error] [pid 19336:tid 9732] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 01:50:17.832465 2015] [proxy_http:error] [pid 19336:tid 9732] [client 190.60.94.206:65472] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 04:42:10.810779 2015] [cgi:error] [pid 19336:tid 10308] [client 115.230.124.164:2303] script not found or unable to stat: E:/nuevo/cgi-bin/common [Wed Nov 25 04:55:04.946538 2015] [mpm_winnt:warn] [pid 19336:tid 17824] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Nov 25 05:00:19.974492 2015] [mpm_winnt:warn] [pid 19336:tid 17824] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Nov 25 06:06:15.939640 2015] [cgi:error] [pid 19336:tid 9732] [client 77.236.96.52:33527] script not found or unable to stat: E:/nuevo/cgi-bin/test-cgi [Wed Nov 25 07:00:21.697941 2015] [proxy:error] [pid 19336:tid 11452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 07:00:21.697941 2015] [proxy:error] [pid 19336:tid 11452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 07:00:21.697941 2015] [proxy_http:error] [pid 19336:tid 11452] [client 152.61.192.232:8496] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 07:00:21.916341 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:00:22.150342 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:00:22.384342 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:00:22.633943 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:02:25.250158 2015] [proxy:error] [pid 19336:tid 8752] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 07:02:25.250158 2015] [proxy:error] [pid 19336:tid 8752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 07:02:25.250158 2015] [proxy_http:error] [pid 19336:tid 8752] [client 152.61.192.232:56007] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 07:02:25.468558 2015] [proxy:error] [pid 19336:tid 8752] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:02:25.702559 2015] [proxy:error] [pid 19336:tid 8752] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:02:25.952159 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:02:26.186160 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:02:26.435760 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:00.356641 2015] [proxy:error] [pid 19336:tid 10384] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 07:07:00.356641 2015] [proxy:error] [pid 19336:tid 10384] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 07:07:00.356641 2015] [proxy_http:error] [pid 19336:tid 10384] [client 152.61.128.66:48467] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 07:07:00.590642 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:00.840242 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:01.058642 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:01.292643 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:01.526643 2015] [proxy:error] [pid 19336:tid 10384] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:27.687889 2015] [proxy:error] [pid 19336:tid 9860] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:27.921890 2015] [proxy:error] [pid 19336:tid 9860] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:28.155890 2015] [proxy:error] [pid 19336:tid 9860] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:28.389890 2015] [proxy:error] [pid 19336:tid 9860] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 07:07:28.623891 2015] [proxy:error] [pid 19336:tid 9860] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 08:03:13.816766 2015] [proxy_http:error] [pid 19336:tid 8672] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:26093] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 08:03:13.816766 2015] [proxy:error] [pid 19336:tid 8672] [client 201.245.192.253:26093] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 08:23:44.705728 2015] [proxy_http:error] [pid 19336:tid 9924] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:30523] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 08:23:44.705728 2015] [proxy:error] [pid 19336:tid 9924] [client 201.245.192.253:30523] AH00898: Error reading from remote server returned by /isolucionsda/FrameSetGeneral.asp, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 08:23:45.797730 2015] [proxy_http:error] [pid 19336:tid 10448] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:30526] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 08:23:45.797730 2015] [proxy:error] [pid 19336:tid 10448] [client 201.245.192.253:30526] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 08:58:40.289609 2015] [proxy_http:error] [pid 19336:tid 9788] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:42217] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=55495453536757564567 [Wed Nov 25 08:59:12.846866 2015] [proxy:error] [pid 19336:tid 8700] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 08:59:12.846866 2015] [proxy:error] [pid 19336:tid 8700] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 08:59:12.846866 2015] [proxy_http:error] [pid 19336:tid 8700] [client 190.144.114.156:63709] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 09:09:58.235600 2015] [proxy:error] [pid 19336:tid 9032] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 09:09:58.235600 2015] [proxy:error] [pid 19336:tid 9032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 09:09:58.235600 2015] [proxy_http:error] [pid 19336:tid 9032] [client 190.147.12.144:53457] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://ideca.proyectospixel.com/en/services/services-directory [Wed Nov 25 09:10:04.850011 2015] [proxy:error] [pid 19336:tid 10156] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:10:05.084012 2015] [proxy:error] [pid 19336:tid 10344] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:10:05.318012 2015] [proxy:error] [pid 19336:tid 10344] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:10:05.552013 2015] [proxy:error] [pid 19336:tid 10344] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:10:05.770413 2015] [proxy:error] [pid 19336:tid 10344] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:10:06.004413 2015] [proxy:error] [pid 19336:tid 10344] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:15:17.412160 2015] [proxy_http:error] [pid 19336:tid 10156] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:12802] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 09:15:17.412160 2015] [proxy:error] [pid 19336:tid 10156] [client 201.245.192.253:12802] AH00898: Error reading from remote server returned by /IsolucionSDA/BarraFavoritos.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 09:15:18.878563 2015] [proxy_http:error] [pid 19336:tid 9860] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:12804] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=7 [Wed Nov 25 09:15:18.878563 2015] [proxy:error] [pid 19336:tid 9860] [client 201.245.192.253:12804] AH00898: Error reading from remote server returned by /IsolucionSDA/Menu.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=7 [Wed Nov 25 09:33:41.286699 2015] [proxy:error] [pid 19336:tid 11452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 09:33:41.286699 2015] [proxy:error] [pid 19336:tid 11452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 09:33:41.286699 2015] [proxy_http:error] [pid 19336:tid 11452] [client 152.61.192.232:56937] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 09:33:41.505100 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:33:41.739100 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:33:41.957501 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 09:33:42.191501 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 10:41:14.861219 2015] [proxy:error] [pid 19336:tid 8648] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 10:41:14.861219 2015] [proxy:error] [pid 19336:tid 8648] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 10:41:14.861219 2015] [proxy_http:error] [pid 19336:tid 8648] [client 190.9.201.86:39388] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 10:41:31.771649 2015] [proxy:error] [pid 19336:tid 14188] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 11:18:46.725174 2015] [proxy:error] [pid 19336:tid 8688] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 11:18:46.725174 2015] [proxy:error] [pid 19336:tid 8688] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 11:18:46.725174 2015] [proxy_http:error] [pid 19336:tid 8688] [client 208.30.41.59:35584] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://10.35.100.66:82/portalmapas35/ [Wed Nov 25 12:01:04.023831 2015] [proxy_http:error] [pid 19336:tid 8624] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:49296] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 12:01:04.023831 2015] [proxy:error] [pid 19336:tid 8624] [client 201.245.192.253:49296] AH00898: Error reading from remote server returned by /IsolucionSDA/BarraFavoritos.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 12:01:05.724234 2015] [proxy_http:error] [pid 19336:tid 8636] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:49294] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 13:00:23.841883 2015] [proxy:error] [pid 19336:tid 9380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:00:23.841883 2015] [proxy:error] [pid 19336:tid 9380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:00:23.841883 2015] [proxy_http:error] [pid 19336:tid 9380] [client 152.61.192.232:4105] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:00:24.060284 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:00:24.294284 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:00:24.528285 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:00:24.762285 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:02:05.522862 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:02:05.522862 2015] [proxy:error] [pid 19336:tid 12672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:02:05.522862 2015] [proxy_http:error] [pid 19336:tid 12672] [client 152.61.192.232:12668] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:02:05.741262 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:02:05.975263 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:02:06.209263 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:02:06.443264 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:02:06.661664 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:08:04.120692 2015] [proxy:error] [pid 19336:tid 10308] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:08:04.120692 2015] [proxy:error] [pid 19336:tid 10308] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:08:04.120692 2015] [proxy_http:error] [pid 19336:tid 10308] [client 152.61.128.66:33082] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:08:04.354692 2015] [proxy:error] [pid 19336:tid 10308] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:08:04.588693 2015] [proxy:error] [pid 19336:tid 9252] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:08:04.807093 2015] [proxy:error] [pid 19336:tid 10000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:08:05.041093 2015] [proxy:error] [pid 19336:tid 10000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:08:05.275094 2015] [proxy:error] [pid 19336:tid 10000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:09:35.536852 2015] [proxy:error] [pid 19336:tid 9572] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:09:35.536852 2015] [proxy:error] [pid 19336:tid 9572] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:09:35.536852 2015] [proxy_http:error] [pid 19336:tid 9572] [client 152.61.128.66:35163] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:09:35.755253 2015] [proxy:error] [pid 19336:tid 9572] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:09:35.989253 2015] [proxy:error] [pid 19336:tid 9572] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:09:36.223254 2015] [proxy:error] [pid 19336:tid 9572] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:09:36.457254 2015] [proxy:error] [pid 19336:tid 9572] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:12:18.932539 2015] [proxy:error] [pid 19336:tid 8700] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:12:18.932539 2015] [proxy:error] [pid 19336:tid 8700] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:12:18.932539 2015] [proxy_http:error] [pid 19336:tid 8700] [client 152.61.193.99:56012] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:12:19.150940 2015] [proxy:error] [pid 19336:tid 8700] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:12:19.384940 2015] [proxy:error] [pid 19336:tid 8700] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:12:19.634541 2015] [proxy:error] [pid 19336:tid 8700] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:12:19.852941 2015] [proxy:error] [pid 19336:tid 8700] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:12:20.086942 2015] [proxy:error] [pid 19336:tid 8700] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:31:38.529376 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 13:31:38.529376 2015] [proxy:error] [pid 19336:tid 8796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 13:31:38.529376 2015] [proxy_http:error] [pid 19336:tid 8796] [client 152.61.193.99:6883] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 13:31:38.747777 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:31:38.981777 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:31:39.200177 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:31:39.434178 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 13:48:13.483524 2015] [proxy_http:error] [pid 19336:tid 9780] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:36618] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/BarraTitulos.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Wed Nov 25 14:08:33.625067 2015] [proxy_http:error] [pid 19336:tid 9444] (OS 10054)An existing connection was forcibly closed by the remote host. : [client 201.245.192.253:29258] AH02609: read request body failed to 172.22.1.31:80 (172.22.1.31) from 201.245.192.253 (), referer: http://190.27.245.106/ISOlucionSDA//Administracion/Upload/Upload.asp?Id_Articulo=9374&UPLDQuerystring=Id_Articulo=9374&UPLDMODO=SubirArchivoADocumento&UPLDRuta=E:\\Isolucion\\Web\\BancoConocimiento\\R\\Resolucion631de2015\\&UPLDAtras=http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp&UPLDAdelante=http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp [Wed Nov 25 14:08:33.625067 2015] [proxy_http:error] [pid 19336:tid 9444] [client 201.245.192.253:29258] AH01097: pass request body failed to 172.22.1.31:80 (172.22.1.31) from 201.245.192.253 (), referer: http://190.27.245.106/ISOlucionSDA//Administracion/Upload/Upload.asp?Id_Articulo=9374&UPLDQuerystring=Id_Articulo=9374&UPLDMODO=SubirArchivoADocumento&UPLDRuta=E:\\Isolucion\\Web\\BancoConocimiento\\R\\Resolucion631de2015\\&UPLDAtras=http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp&UPLDAdelante=http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp [Wed Nov 25 14:28:20.943152 2015] [proxy:error] [pid 19336:tid 10116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 14:28:20.943152 2015] [proxy:error] [pid 19336:tid 10116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 14:28:20.943152 2015] [proxy_http:error] [pid 19336:tid 10116] [client 168.176.55.116:40352] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/?maptoload=Salud&widgettoopen=Otros%20Mapas [Wed Nov 25 14:42:08.150205 2015] [mpm_winnt:warn] [pid 19336:tid 17824] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Nov 25 14:58:16.818307 2015] [proxy_http:error] [pid 19336:tid 11844] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:37949] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 14:58:16.818307 2015] [proxy:error] [pid 19336:tid 11844] [client 201.245.192.253:37949] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 15:05:17.037245 2015] [proxy_http:error] [pid 19336:tid 9252] (OS 10053)An established connection was aborted by the software in your host machine. : [client 190.24.223.132:21312] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 15:06:16.208149 2015] [proxy:error] [pid 19336:tid 9160] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.208149 2015] [proxy:error] [pid 19336:tid 9160] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 15:06:16.208149 2015] [proxy_http:error] [pid 19336:tid 9160] [client 201.245.192.253:48124] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:16.332949 2015] [proxy:error] [pid 19336:tid 9332] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.332949 2015] [proxy_http:error] [pid 19336:tid 9332] [client 201.245.192.253:48127] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:16.379749 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.379749 2015] [proxy_http:error] [pid 19336:tid 12672] [client 201.245.192.253:48133] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:16.629349 2015] [proxy:error] [pid 19336:tid 9252] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.629349 2015] [proxy_http:error] [pid 19336:tid 9252] [client 201.245.192.253:48145] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:16.660549 2015] [proxy:error] [pid 19336:tid 14188] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.660549 2015] [proxy_http:error] [pid 19336:tid 14188] [client 201.245.192.253:48148] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:16.707350 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:16.707350 2015] [proxy_http:error] [pid 19336:tid 8796] [client 201.245.192.253:48144] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:17.877352 2015] [proxy:error] [pid 19336:tid 10344] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:17.877352 2015] [proxy:error] [pid 19336:tid 10344] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 15:06:17.877352 2015] [proxy_http:error] [pid 19336:tid 10344] [client 201.245.192.253:48185] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:17.877352 2015] [proxy:error] [pid 19336:tid 12212] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:17.877352 2015] [proxy_http:error] [pid 19336:tid 12212] [client 201.245.192.253:48186] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:17.892952 2015] [proxy:error] [pid 19336:tid 8856] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:17.892952 2015] [proxy_http:error] [pid 19336:tid 8856] [client 201.245.192.253:48184] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:17.892952 2015] [proxy:error] [pid 19336:tid 8752] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:17.892952 2015] [proxy_http:error] [pid 19336:tid 8752] [client 201.245.192.253:48183] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:18.111352 2015] [proxy:error] [pid 19336:tid 9860] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:18.111352 2015] [proxy_http:error] [pid 19336:tid 9860] [client 201.245.192.253:48193] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:18.111352 2015] [proxy:error] [pid 19336:tid 14360] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:18.111352 2015] [proxy_http:error] [pid 19336:tid 14360] [client 201.245.192.253:48194] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/inicio? [Wed Nov 25 15:06:25.536965 2015] [proxy:error] [pid 19336:tid 8724] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.536965 2015] [proxy:error] [pid 19336:tid 8724] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 15:06:25.536965 2015] [proxy_http:error] [pid 19336:tid 8724] [client 201.245.192.253:48351] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:25.552565 2015] [proxy:error] [pid 19336:tid 9660] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.552565 2015] [proxy_http:error] [pid 19336:tid 9660] [client 201.245.192.253:48350] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:25.568165 2015] [proxy:error] [pid 19336:tid 9924] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.568165 2015] [proxy_http:error] [pid 19336:tid 9924] [client 201.245.192.253:48352] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:25.614965 2015] [proxy:error] [pid 19336:tid 8732] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.614965 2015] [proxy_http:error] [pid 19336:tid 8732] [client 201.245.192.253:48355] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:25.958166 2015] [proxy:error] [pid 19336:tid 9236] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.958166 2015] [proxy_http:error] [pid 19336:tid 9236] [client 201.245.192.253:48371] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:25.973766 2015] [proxy:error] [pid 19336:tid 8992] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:25.973766 2015] [proxy_http:error] [pid 19336:tid 8992] [client 201.245.192.253:48370] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.235770 2015] [proxy:error] [pid 19336:tid 9836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.235770 2015] [proxy_http:error] [pid 19336:tid 9836] [client 201.245.192.253:48419] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.235770 2015] [proxy:error] [pid 19336:tid 9968] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.235770 2015] [proxy_http:error] [pid 19336:tid 9968] [client 201.245.192.253:48420] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.235770 2015] [proxy:error] [pid 19336:tid 10256] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.235770 2015] [proxy_http:error] [pid 19336:tid 10256] [client 201.245.192.253:48418] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.251370 2015] [proxy:error] [pid 19336:tid 9008] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.251370 2015] [proxy_http:error] [pid 19336:tid 9008] [client 201.245.192.253:48421] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.719371 2015] [proxy:error] [pid 19336:tid 8672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.719371 2015] [proxy_http:error] [pid 19336:tid 8672] [client 201.245.192.253:48437] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.719371 2015] [proxy:error] [pid 19336:tid 9684] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.719371 2015] [proxy_http:error] [pid 19336:tid 9684] [client 201.245.192.253:48436] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.734971 2015] [proxy:error] [pid 19336:tid 9732] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.734971 2015] [proxy_http:error] [pid 19336:tid 9732] [client 201.245.192.253:48438] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:28.734971 2015] [proxy:error] [pid 19336:tid 9040] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:28.734971 2015] [proxy_http:error] [pid 19336:tid 9040] [client 201.245.192.253:48439] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.107773 2015] [proxy:error] [pid 19336:tid 9016] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.107773 2015] [proxy_http:error] [pid 19336:tid 9016] [client 201.245.192.253:48477] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.107773 2015] [proxy:error] [pid 19336:tid 9788] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.107773 2015] [proxy_http:error] [pid 19336:tid 9788] [client 201.245.192.253:48481] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.310573 2015] [proxy:error] [pid 19336:tid 9032] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.310573 2015] [proxy_http:error] [pid 19336:tid 9032] [client 201.245.192.253:48487] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.310573 2015] [proxy:error] [pid 19336:tid 11452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.310573 2015] [proxy_http:error] [pid 19336:tid 11452] [client 201.245.192.253:48488] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.310573 2015] [proxy:error] [pid 19336:tid 8948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.310573 2015] [proxy_http:error] [pid 19336:tid 8948] [client 201.245.192.253:48486] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.341773 2015] [proxy:error] [pid 19336:tid 9536] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.341773 2015] [proxy_http:error] [pid 19336:tid 9536] [client 201.245.192.253:48489] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.872174 2015] [proxy:error] [pid 19336:tid 9352] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.872174 2015] [proxy_http:error] [pid 19336:tid 9352] [client 201.245.192.253:48508] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.872174 2015] [proxy:error] [pid 19336:tid 9780] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.872174 2015] [proxy_http:error] [pid 19336:tid 9780] [client 201.245.192.253:48507] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.872174 2015] [proxy:error] [pid 19336:tid 8656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.872174 2015] [proxy_http:error] [pid 19336:tid 8656] [client 201.245.192.253:48510] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:30.872174 2015] [proxy:error] [pid 19336:tid 8836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:30.872174 2015] [proxy_http:error] [pid 19336:tid 8836] [client 201.245.192.253:48509] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.042176 2015] [proxy:error] [pid 19336:tid 10352] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.042176 2015] [proxy_http:error] [pid 19336:tid 10352] [client 201.245.192.253:48529] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.042176 2015] [proxy:error] [pid 19336:tid 10304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.042176 2015] [proxy_http:error] [pid 19336:tid 10304] [client 201.245.192.253:48530] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.806578 2015] [proxy:error] [pid 19336:tid 10316] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.806578 2015] [proxy_http:error] [pid 19336:tid 10316] [client 201.245.192.253:48557] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.806578 2015] [proxy:error] [pid 19336:tid 9572] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.806578 2015] [proxy_http:error] [pid 19336:tid 9572] [client 201.245.192.253:48556] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.806578 2015] [proxy:error] [pid 19336:tid 11836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.806578 2015] [proxy_http:error] [pid 19336:tid 11836] [client 201.245.192.253:48558] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:32.806578 2015] [proxy:error] [pid 19336:tid 8912] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:32.806578 2015] [proxy_http:error] [pid 19336:tid 8912] [client 201.245.192.253:48553] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:33.555379 2015] [proxy:error] [pid 19336:tid 9064] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:33.555379 2015] [proxy_http:error] [pid 19336:tid 9064] [client 201.245.192.253:48583] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:33.555379 2015] [proxy:error] [pid 19336:tid 9500] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:33.555379 2015] [proxy_http:error] [pid 19336:tid 9500] [client 201.245.192.253:48584] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:33.555379 2015] [proxy:error] [pid 19336:tid 8896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:33.555379 2015] [proxy_http:error] [pid 19336:tid 8896] [client 201.245.192.253:48585] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:33.555379 2015] [proxy:error] [pid 19336:tid 8624] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:33.555379 2015] [proxy_http:error] [pid 19336:tid 8624] [client 201.245.192.253:48586] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:34.226180 2015] [proxy:error] [pid 19336:tid 8920] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:34.226180 2015] [proxy_http:error] [pid 19336:tid 8920] [client 201.245.192.253:48600] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:34.226180 2015] [proxy:error] [pid 19336:tid 9364] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:34.226180 2015] [proxy_http:error] [pid 19336:tid 9364] [client 201.245.192.253:48604] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:35.801783 2015] [proxy:error] [pid 19336:tid 9128] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:35.801783 2015] [proxy_http:error] [pid 19336:tid 9128] [client 201.245.192.253:48613] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:35.801783 2015] [proxy:error] [pid 19336:tid 10084] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:35.801783 2015] [proxy_http:error] [pid 19336:tid 10084] [client 201.245.192.253:48612] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:35.817383 2015] [proxy:error] [pid 19336:tid 9000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:35.817383 2015] [proxy_http:error] [pid 19336:tid 9000] [client 201.245.192.253:48615] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:35.817383 2015] [proxy:error] [pid 19336:tid 8960] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:35.817383 2015] [proxy_http:error] [pid 19336:tid 8960] [client 201.245.192.253:48614] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:36.628585 2015] [proxy:error] [pid 19336:tid 15728] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:36.628585 2015] [proxy:error] [pid 19336:tid 9736] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:36.628585 2015] [proxy_http:error] [pid 19336:tid 15728] [client 201.245.192.253:48637] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:36.628585 2015] [proxy_http:error] [pid 19336:tid 9736] [client 201.245.192.253:48640] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:37.907787 2015] [proxy:error] [pid 19336:tid 10116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:37.907787 2015] [proxy:error] [pid 19336:tid 10456] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:37.907787 2015] [proxy_http:error] [pid 19336:tid 10456] [client 201.245.192.253:48661] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:37.907787 2015] [proxy_http:error] [pid 19336:tid 10116] [client 201.245.192.253:48662] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:37.923387 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:37.923387 2015] [proxy_http:error] [pid 19336:tid 8796] [client 201.245.192.253:48663] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:38.687788 2015] [proxy:error] [pid 19336:tid 14188] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:38.687788 2015] [proxy_http:error] [pid 19336:tid 14188] [client 201.245.192.253:48673] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:40.356991 2015] [proxy:error] [pid 19336:tid 14360] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:40.356991 2015] [proxy_http:error] [pid 19336:tid 14360] [client 201.245.192.253:48702] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:40.356991 2015] [proxy:error] [pid 19336:tid 9860] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:40.356991 2015] [proxy_http:error] [pid 19336:tid 9860] [client 201.245.192.253:48703] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:40.388191 2015] [proxy:error] [pid 19336:tid 9956] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:40.388191 2015] [proxy_http:error] [pid 19336:tid 9956] [client 201.245.192.253:48704] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:40.388191 2015] [proxy:error] [pid 19336:tid 8752] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:40.388191 2015] [proxy_http:error] [pid 19336:tid 8752] [client 201.245.192.253:48711] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:41.230593 2015] [proxy:error] [pid 19336:tid 8856] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:41.230593 2015] [proxy_http:error] [pid 19336:tid 8856] [client 201.245.192.253:48721] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 15:06:41.433393 2015] [proxy:error] [pid 19336:tid 10344] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 15:06:41.433393 2015] [proxy_http:error] [pid 19336:tid 10344] [client 201.245.192.253:48722] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/es/web/guest/home [Wed Nov 25 16:37:58.120412 2015] [proxy:error] [pid 19336:tid 9932] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 16:37:58.120412 2015] [proxy:error] [pid 19336:tid 9932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 16:37:58.120412 2015] [proxy_http:error] [pid 19336:tid 9932] [client 186.147.28.189:47041] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 17:59:26.203798 2015] [proxy_http:error] [pid 19336:tid 8752] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:56875] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 17:59:26.203798 2015] [proxy:error] [pid 19336:tid 8752] [client 201.245.192.253:56875] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 18:05:12.758407 2015] [proxy_http:error] [pid 19336:tid 10128] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:35475] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Wed Nov 25 18:24:33.634446 2015] [proxy:error] [pid 19336:tid 9000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:24:33.634446 2015] [proxy:error] [pid 19336:tid 9000] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:24:33.634446 2015] [proxy_http:error] [pid 19336:tid 9000] [client 181.130.218.12:63771] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:25:09.124508 2015] [proxy:error] [pid 19336:tid 10000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:26:24.254240 2015] [proxy:error] [pid 19336:tid 9444] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:26:24.254240 2015] [proxy:error] [pid 19336:tid 9444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:26:24.254240 2015] [proxy_http:error] [pid 19336:tid 9444] [client 181.130.218.12:63787] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:29:37.304579 2015] [proxy:error] [pid 19336:tid 9000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:29:37.304579 2015] [proxy:error] [pid 19336:tid 9000] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:29:37.304579 2015] [proxy_http:error] [pid 19336:tid 9000] [client 181.130.218.12:63851] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:29:40.440184 2015] [proxy:error] [pid 19336:tid 8896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:29:40.440184 2015] [proxy_http:error] [pid 19336:tid 8896] [client 181.130.218.12:63852] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:30:10.969438 2015] [proxy:error] [pid 19336:tid 10116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:30:10.969438 2015] [proxy:error] [pid 19336:tid 10116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:30:10.969438 2015] [proxy_http:error] [pid 19336:tid 10116] [client 181.130.218.12:63869] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:30:11.921040 2015] [proxy:error] [pid 19336:tid 9736] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:30:20.672655 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:30:20.672655 2015] [proxy_http:error] [pid 19336:tid 8796] [client 181.130.218.12:63870] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:30:49.454706 2015] [proxy:error] [pid 19336:tid 10116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:30:49.454706 2015] [proxy:error] [pid 19336:tid 10116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:30:49.454706 2015] [proxy_http:error] [pid 19336:tid 10116] [client 181.130.218.12:63887] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:30:58.315521 2015] [proxy:error] [pid 19336:tid 9000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:31:00.405925 2015] [proxy:error] [pid 19336:tid 9000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:31:04.383932 2015] [proxy:error] [pid 19336:tid 8636] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:31:04.383932 2015] [proxy_http:error] [pid 19336:tid 8636] [client 181.130.218.12:63888] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:31:26.036770 2015] [proxy:error] [pid 19336:tid 8636] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:31:26.036770 2015] [proxy:error] [pid 19336:tid 8636] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:31:26.036770 2015] [proxy_http:error] [pid 19336:tid 8636] [client 181.130.218.12:63893] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:31:31.574780 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:32:00.793631 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:32:04.615638 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:34:06.966653 2015] [proxy:error] [pid 19336:tid 9252] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:34:06.966653 2015] [proxy:error] [pid 19336:tid 9252] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:34:06.966653 2015] [proxy_http:error] [pid 19336:tid 9252] [client 181.130.218.12:63914] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:34:13.955465 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:34:13.955465 2015] [proxy_http:error] [pid 19336:tid 8796] [client 181.130.218.12:63915] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:34:44.032318 2015] [proxy:error] [pid 19336:tid 10116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:34:44.032318 2015] [proxy:error] [pid 19336:tid 10116] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:34:44.032318 2015] [proxy_http:error] [pid 19336:tid 10116] [client 181.130.218.12:63918] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:36:08.147665 2015] [proxy:error] [pid 19336:tid 8896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:36:08.147665 2015] [proxy:error] [pid 19336:tid 8896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:36:08.147665 2015] [proxy_http:error] [pid 19336:tid 8896] [client 181.130.218.12:63922] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:36:19.644886 2015] [proxy:error] [pid 19336:tid 15728] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:36:56.835351 2015] [proxy:error] [pid 19336:tid 9000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:42:19.288917 2015] [proxy:error] [pid 19336:tid 9736] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:42:19.288917 2015] [proxy:error] [pid 19336:tid 9736] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:42:19.288917 2015] [proxy_http:error] [pid 19336:tid 9736] [client 181.130.218.12:63946] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:47:09.184226 2015] [proxy:error] [pid 19336:tid 9380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:47:09.184226 2015] [proxy:error] [pid 19336:tid 9380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 18:47:09.184226 2015] [proxy_http:error] [pid 19336:tid 9380] [client 181.130.218.12:63952] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:47:09.979828 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:47:14.659836 2015] [proxy:error] [pid 19336:tid 9144] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:47:17.327441 2015] [proxy:error] [pid 19336:tid 9868] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:47:22.553450 2015] [proxy:error] [pid 19336:tid 9868] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 18:47:28.403460 2015] [proxy:error] [pid 19336:tid 10128] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 18:47:28.403460 2015] [proxy_http:error] [pid 19336:tid 10128] [client 181.130.218.12:63955] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 18:59:46.019556 2015] [proxy_http:error] [pid 19336:tid 9868] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:35645] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 18:59:46.019556 2015] [proxy:error] [pid 19336:tid 9868] [client 201.245.192.253:35645] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 19:00:20.994817 2015] [proxy:error] [pid 19336:tid 9252] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:00:20.994817 2015] [proxy:error] [pid 19336:tid 9252] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:00:20.994817 2015] [proxy_http:error] [pid 19336:tid 9252] [client 152.61.192.232:62988] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 19:00:21.306818 2015] [proxy:error] [pid 19336:tid 9252] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:00:21.603218 2015] [proxy:error] [pid 19336:tid 9252] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:00:21.915219 2015] [proxy:error] [pid 19336:tid 9252] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:00:22.227219 2015] [proxy:error] [pid 19336:tid 9252] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:13.533415 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:02:13.533415 2015] [proxy:error] [pid 19336:tid 12672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:02:13.533415 2015] [proxy_http:error] [pid 19336:tid 12672] [client 152.61.192.232:8471] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 19:02:13.829815 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:14.126216 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:14.422616 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:14.734617 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:15.046618 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:02:32.971049 2015] [proxy_http:error] [pid 19336:tid 9252] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:36439] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/BancoConocimiento/l/ley1437de2011/ley1437de2011.asp?IdArticulo=8129 [Wed Nov 25 19:02:58.383494 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:03:00.848298 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:03:06.183507 2015] [proxy:error] [pid 19336:tid 11452] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:03:09.943114 2015] [proxy:error] [pid 19336:tid 9144] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:03:40.753168 2015] [proxy:error] [pid 19336:tid 9064] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:03:40.753168 2015] [proxy:error] [pid 19336:tid 9064] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:03:40.753168 2015] [proxy_http:error] [pid 19336:tid 9064] [client 181.130.218.12:64079] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:03:41.423969 2015] [proxy:error] [pid 19336:tid 9064] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:03:50.939986 2015] [proxy:error] [pid 19336:tid 15728] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:04:14.542827 2015] [proxy:error] [pid 19336:tid 10840] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:05:58.610610 2015] [proxy_http:error] [pid 19336:tid 10156] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:37579] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 19:05:58.610610 2015] [proxy:error] [pid 19336:tid 10156] [client 201.245.192.253:37579] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Wed Nov 25 19:06:00.342213 2015] [proxy_http:error] [pid 19336:tid 10456] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:37585] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Wed Nov 25 19:06:00.342213 2015] [proxy:error] [pid 19336:tid 10456] [client 201.245.192.253:37585] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Wed Nov 25 19:07:55.564016 2015] [proxy:error] [pid 19336:tid 10448] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:07:55.564016 2015] [proxy:error] [pid 19336:tid 10448] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:07:55.564016 2015] [proxy_http:error] [pid 19336:tid 10448] [client 152.61.128.66:46203] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 19:07:55.876016 2015] [proxy:error] [pid 19336:tid 10448] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:07:56.188017 2015] [proxy:error] [pid 19336:tid 10448] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:07:56.500017 2015] [proxy:error] [pid 19336:tid 10448] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:07:56.796418 2015] [proxy:error] [pid 19336:tid 10448] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:08:00.634025 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:08:00.634025 2015] [proxy_http:error] [pid 19336:tid 8796] [client 152.61.128.66:46303] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 19:08:21.974862 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:08:21.974862 2015] [proxy:error] [pid 19336:tid 8796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:08:21.974862 2015] [proxy_http:error] [pid 19336:tid 8796] [client 152.61.128.66:46692] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Nov 25 19:08:22.286863 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:08:22.598863 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:08:22.910864 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:08:23.222864 2015] [proxy:error] [pid 19336:tid 8796] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:11:03.887546 2015] [proxy:error] [pid 19336:tid 10156] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:11:03.887546 2015] [proxy:error] [pid 19336:tid 10156] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:11:03.887546 2015] [proxy_http:error] [pid 19336:tid 10156] [client 181.130.218.12:64132] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:11:05.837550 2015] [proxy:error] [pid 19336:tid 11452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:11:05.837550 2015] [proxy_http:error] [pid 19336:tid 11452] [client 181.130.218.12:64135] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:11:30.391993 2015] [proxy:error] [pid 19336:tid 8624] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:11:30.391993 2015] [proxy:error] [pid 19336:tid 8624] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:11:30.391993 2015] [proxy_http:error] [pid 19336:tid 8624] [client 181.130.218.12:64154] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:11:49.174426 2015] [proxy:error] [pid 19336:tid 9200] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:11:49.174426 2015] [proxy_http:error] [pid 19336:tid 9200] [client 181.130.218.12:64155] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:12:18.486877 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:12:18.486877 2015] [proxy:error] [pid 19336:tid 12672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:12:18.486877 2015] [proxy_http:error] [pid 19336:tid 12672] [client 181.130.218.12:64164] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:12:18.986078 2015] [proxy:error] [pid 19336:tid 9736] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:12:18.986078 2015] [proxy_http:error] [pid 19336:tid 9736] [client 181.130.218.12:64165] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:12:29.016896 2015] [proxy:error] [pid 19336:tid 10840] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:12:29.016896 2015] [proxy_http:error] [pid 19336:tid 10840] [client 181.130.218.12:64170] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:14:42.677931 2015] [proxy:error] [pid 19336:tid 14360] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:14:42.677931 2015] [proxy:error] [pid 19336:tid 14360] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:14:42.677931 2015] [proxy_http:error] [pid 19336:tid 14360] [client 181.130.218.12:64175] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:14:45.548336 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:14:45.548336 2015] [proxy_http:error] [pid 19336:tid 8796] [client 181.130.218.12:64178] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:15:54.110456 2015] [proxy:error] [pid 19336:tid 9200] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:15:54.110456 2015] [proxy:error] [pid 19336:tid 9200] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:15:54.110456 2015] [proxy_http:error] [pid 19336:tid 9200] [client 181.130.218.12:64183] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:20:38.483356 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:20:38.483356 2015] [proxy:error] [pid 19336:tid 12672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:20:38.483356 2015] [proxy_http:error] [pid 19336:tid 12672] [client 181.130.218.12:64193] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:20:42.726563 2015] [proxy:error] [pid 19336:tid 9380] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:21:05.736603 2015] [proxy:error] [pid 19336:tid 8636] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:21:32.537451 2015] [proxy:error] [pid 19336:tid 12672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:22:12.629521 2015] [proxy:error] [pid 19336:tid 12672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:22:12.629521 2015] [proxy:error] [pid 19336:tid 12672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:22:12.629521 2015] [proxy_http:error] [pid 19336:tid 12672] [client 181.130.218.12:64205] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:22:21.053536 2015] [proxy:error] [pid 19336:tid 9000] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:23:03.360810 2015] [proxy:error] [pid 19336:tid 9200] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 19:25:29.361467 2015] [proxy:error] [pid 19336:tid 8796] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 19:25:29.361467 2015] [proxy:error] [pid 19336:tid 8796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 19:25:29.361467 2015] [proxy_http:error] [pid 19336:tid 8796] [client 181.130.218.12:64226] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 19:30:32.516799 2015] [proxy_http:error] [pid 19336:tid 8796] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:46565] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 19:30:32.516799 2015] [proxy:error] [pid 19336:tid 8796] [client 201.245.192.253:46565] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 20:43:07.157248 2015] [proxy:error] [pid 19336:tid 9064] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 20:43:07.157248 2015] [proxy:error] [pid 19336:tid 9064] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 20:43:07.157248 2015] [proxy_http:error] [pid 19336:tid 9064] [client 190.25.165.43:50782] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 20:47:58.378559 2015] [proxy_http:error] [pid 19336:tid 10084] (OS 10053)An established connection was aborted by the software in your host machine. : [client 186.144.176.206:49595] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Wed Nov 25 21:04:12.709470 2015] [proxy:error] [pid 19336:tid 8896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:04:12.709470 2015] [proxy:error] [pid 19336:tid 8896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 21:04:12.709470 2015] [proxy_http:error] [pid 19336:tid 8896] [client 192.222.214.151:57620] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:44:49.902751 2015] [proxy:error] [pid 19336:tid 9940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:44:49.902751 2015] [proxy:error] [pid 19336:tid 9940] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 21:44:49.902751 2015] [proxy_http:error] [pid 19336:tid 9940] [client 181.142.236.39:9232] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:02.772774 2015] [proxy:error] [pid 19336:tid 9836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:02.772774 2015] [proxy_http:error] [pid 19336:tid 9836] [client 181.142.236.39:9236] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:03.303175 2015] [proxy:error] [pid 19336:tid 9860] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:03.303175 2015] [proxy_http:error] [pid 19336:tid 9860] [client 181.142.236.39:9237] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:03.973976 2015] [proxy:error] [pid 19336:tid 11836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:03.973976 2015] [proxy_http:error] [pid 19336:tid 11836] [client 181.142.236.39:9244] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:04.566777 2015] [proxy:error] [pid 19336:tid 8920] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:04.566777 2015] [proxy_http:error] [pid 19336:tid 8920] [client 181.142.236.39:9252] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:07.671182 2015] [proxy:error] [pid 19336:tid 10304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:07.671182 2015] [proxy_http:error] [pid 19336:tid 10304] [client 181.142.236.39:9254] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:47.326452 2015] [proxy:error] [pid 19336:tid 8636] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:47.326452 2015] [proxy:error] [pid 19336:tid 8636] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 21:45:47.326452 2015] [proxy_http:error] [pid 19336:tid 8636] [client 181.142.236.39:9268] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:45:50.274857 2015] [proxy:error] [pid 19336:tid 8948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:45:50.274857 2015] [proxy_http:error] [pid 19336:tid 8948] [client 181.142.236.39:9276] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:15.874502 2015] [proxy:error] [pid 19336:tid 8636] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:15.874502 2015] [proxy:error] [pid 19336:tid 8636] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 21:46:15.874502 2015] [proxy_http:error] [pid 19336:tid 8636] [client 181.142.236.39:9279] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:18.339307 2015] [proxy:error] [pid 19336:tid 9332] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:18.339307 2015] [proxy_http:error] [pid 19336:tid 9332] [client 181.142.236.39:9281] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:20.819711 2015] [proxy:error] [pid 19336:tid 9032] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:20.819711 2015] [proxy_http:error] [pid 19336:tid 9032] [client 181.142.236.39:9282] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:28.370124 2015] [proxy:error] [pid 19336:tid 8948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:28.370124 2015] [proxy_http:error] [pid 19336:tid 8948] [client 181.142.236.39:9289] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:28.494924 2015] [proxy:error] [pid 19336:tid 9836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:28.494924 2015] [proxy:error] [pid 19336:tid 10448] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:46:28.494924 2015] [proxy_http:error] [pid 19336:tid 9836] [client 181.142.236.39:9294] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:46:28.494924 2015] [proxy_http:error] [pid 19336:tid 10448] [client 181.142.236.39:9295] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:47:41.815053 2015] [proxy:error] [pid 19336:tid 8948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:47:41.815053 2015] [proxy:error] [pid 19336:tid 8948] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Nov 25 21:47:41.815053 2015] [proxy_http:error] [pid 19336:tid 8948] [client 181.142.236.39:9324] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 21:47:51.955071 2015] [proxy:error] [pid 19336:tid 8672] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Nov 25 21:47:59.037483 2015] [proxy:error] [pid 19336:tid 10344] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Nov 25 21:47:59.037483 2015] [proxy_http:error] [pid 19336:tid 10344] [client 181.142.236.39:9325] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://mapas.bogota.gov.co/portalmapas/ [Wed Nov 25 22:11:10.591128 2015] [mpm_winnt:warn] [pid 19336:tid 17824] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Nov 25 22:11:10.606728 2015] [mpm_winnt:warn] [pid 19336:tid 17824] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0468 ]-- |