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: [Fri May 13 00:22:15.419687 2016] [proxy:error] [pid 15364:tid 16320] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 00:22:15.419687 2016] [proxy:error] [pid 15364:tid 16320] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 00:22:15.419687 2016] [proxy_http:error] [pid 15364:tid 16320] [client 152.61.128.50:56045] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 00:22:15.638088 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:22:15.872088 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:22:16.106089 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:22:16.324489 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:51:06.305128 2016] [proxy:error] [pid 15364:tid 15576] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 00:51:06.305128 2016] [proxy:error] [pid 15364:tid 15576] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 00:51:06.305128 2016] [proxy_http:error] [pid 15364:tid 15576] [client 152.61.192.232:6510] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 00:51:06.523528 2016] [proxy:error] [pid 15364:tid 15576] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:51:06.757528 2016] [proxy:error] [pid 15364:tid 15576] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:51:06.991529 2016] [proxy:error] [pid 15364:tid 15576] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:51:07.225529 2016] [proxy:error] [pid 15364:tid 15576] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:53:25.769372 2016] [proxy:error] [pid 15364:tid 16320] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 00:53:25.769372 2016] [proxy:error] [pid 15364:tid 16320] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 00:53:25.769372 2016] [proxy_http:error] [pid 15364:tid 16320] [client 152.61.128.50:51472] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 00:53:25.987773 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:53:26.206173 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:53:26.440174 2016] [proxy:error] [pid 15364:tid 15316] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:53:26.674174 2016] [proxy:error] [pid 15364:tid 15316] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 00:53:26.892574 2016] [proxy:error] [pid 15364:tid 16320] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:16:42.330625 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 01:16:42.330625 2016] [proxy:error] [pid 15364:tid 14908] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 01:16:42.330625 2016] [proxy_http:error] [pid 15364:tid 14908] [client 152.61.192.232:53530] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 01:16:42.564626 2016] [proxy:error] [pid 15364:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:16:42.798626 2016] [proxy:error] [pid 15364:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:16:43.032627 2016] [proxy:error] [pid 15364:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:16:43.266627 2016] [proxy:error] [pid 15364:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:16:43.500627 2016] [proxy:error] [pid 15364:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 01:52:10.907564 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 05:15:54.371433 2016] [proxy:error] [pid 15364:tid 15004] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 05:15:54.371433 2016] [proxy:error] [pid 15364:tid 15004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 05:15:54.371433 2016] [proxy_http:error] [pid 15364:tid 15004] [client 152.61.128.50:52056] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 05:15:54.589834 2016] [proxy:error] [pid 15364:tid 15004] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 05:15:54.855034 2016] [proxy:error] [pid 15364:tid 15004] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 05:24:19.593921 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 05:24:19.593921 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 05:58:12.012291 2016] [proxy:error] [pid 15364:tid 15792] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 05:58:12.012291 2016] [proxy:error] [pid 15364:tid 15792] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 05:58:12.012291 2016] [proxy_http:error] [pid 15364:tid 15792] [client 152.61.128.50:47419] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 05:58:12.246291 2016] [proxy:error] [pid 15364:tid 15792] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 06:02:43.249967 2016] [proxy:error] [pid 15364:tid 15452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 06:02:43.249967 2016] [proxy:error] [pid 15364:tid 15452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 06:02:43.249967 2016] [proxy_http:error] [pid 15364:tid 15452] [client 152.61.192.232:2649] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 06:02:51.658382 2016] [proxy:error] [pid 15364:tid 15792] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 06:02:51.658382 2016] [proxy_http:error] [pid 15364:tid 15792] [client 152.61.192.232:2784] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 06:03:12.921219 2016] [proxy:error] [pid 15364:tid 15792] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 06:03:12.921219 2016] [proxy:error] [pid 15364:tid 15792] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 06:03:12.921219 2016] [proxy_http:error] [pid 15364:tid 15792] [client 152.61.192.232:2920] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 06:03:12.936819 2016] [proxy:error] [pid 15364:tid 15452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 06:03:12.936819 2016] [proxy_http:error] [pid 15364:tid 15452] [client 152.61.192.232:3031] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 06:03:34.184056 2016] [proxy:error] [pid 15364:tid 15452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 06:03:34.184056 2016] [proxy:error] [pid 15364:tid 15452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 06:03:34.184056 2016] [proxy_http:error] [pid 15364:tid 15452] [client 152.61.192.232:3268] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Fri May 13 07:28:58.340657 2016] [proxy_http:error] [pid 15364:tid 15576] (OS 10053)An established connection was aborted by the software in your host machine. : [client 200.26.149.197:55229] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Fri May 13 07:28:58.340657 2016] [proxy:error] [pid 15364:tid 15576] [client 200.26.149.197:55229] AH00898: Error reading from remote server returned by /isolucionsda/, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Fri May 13 07:43:15.000561 2016] [proxy_http:error] [pid 15364:tid 15316] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54862] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 07:43:15.031761 2016] [proxy_http:error] [pid 15364:tid 15152] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54860] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 07:43:15.031761 2016] [proxy_http:error] [pid 15364:tid 14564] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54861] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 07:43:16.638564 2016] [proxy_http:error] [pid 15364:tid 14884] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54863] 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& [Fri May 13 07:43:16.638564 2016] [proxy:error] [pid 15364:tid 14884] [client 201.245.192.253:54863] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 07:43:26.076581 2016] [proxy_http:error] [pid 15364:tid 15756] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54838] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/bancoconocimiento/m/mapadeprocesos__v4/mapadeprocesos__v4.asp [Fri May 13 07:43:26.092181 2016] [proxy_http:error] [pid 15364:tid 14708] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54977] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/bancoconocimiento/m/mapadeprocesos__v4/mapadeprocesos__v4.asp [Fri May 13 07:43:26.107781 2016] [proxy_http:error] [pid 15364:tid 15300] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:54968] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/bancoconocimiento/m/mapadeprocesos__v4/mapadeprocesos__v4.asp [Fri May 13 08:10:10.383398 2016] [proxy_http:error] [pid 15364:tid 16088] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:40593] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetArticulo.asp?Pagina=/IsolucionSDA/BancoConocimiento/S/Solicituddetrasladooreintegrodeelementos_v2/Solicituddetrasladooreintegrodeelementos_v2.asp?IdArticulo=943 [Fri May 13 08:10:10.383398 2016] [proxy:error] [pid 15364:tid 16088] [client 201.245.192.253:40593] AH00898: Error reading from remote server returned by /IsolucionSDA/BancoConocimiento/S/Solicituddetrasladooreintegrodeelementos_v2/Solicituddetrasladooreintegrodeelementos_v2.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetArticulo.asp?Pagina=/IsolucionSDA/BancoConocimiento/S/Solicituddetrasladooreintegrodeelementos_v2/Solicituddetrasladooreintegrodeelementos_v2.asp?IdArticulo=943 [Fri May 13 08:21:44.038617 2016] [proxy_http:error] [pid 15364:tid 15576] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:51623] 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 [Fri May 13 08:21:44.038617 2016] [proxy_http:error] [pid 15364:tid 14908] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:51628] 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 [Fri May 13 08:59:05.372553 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 09:01:25.523200 2016] [proxy_http:error] [pid 15364:tid 16088] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:59106] 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& [Fri May 13 09:01:25.523200 2016] [proxy:error] [pid 15364:tid 16088] [client 201.245.192.253:59106] AH00898: Error reading from remote server returned by /isolucionsda/Encabezado.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 09:17:53.613335 2016] [proxy_http:error] [pid 15364:tid 15656] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:52437] AH01102: error reading status line from remote server 172.22.1.31:80 [Fri May 13 09:17:53.613335 2016] [proxy:error] [pid 15364:tid 15656] [client 201.245.192.253:52437] AH00898: Error reading from remote server returned by /isolucionsda/Session.asp [Fri May 13 10:06:47.089288 2016] [proxy_http:error] [pid 15364:tid 15152] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:55154] 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& [Fri May 13 10:06:47.089288 2016] [proxy:error] [pid 15364:tid 15152] [client 201.245.192.253:55154] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 10:07:51.267800 2016] [proxy_http:error] [pid 15364:tid 14940] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:46015] 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& [Fri May 13 10:07:51.267800 2016] [proxy:error] [pid 15364:tid 14940] [client 201.245.192.253:46015] AH00898: Error reading from remote server returned by /IsolucionSDA/MagazinHome.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 10:14:48.022532 2016] [proxy_http:error] [pid 15364:tid 15408] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:51411] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FS%2FSolicitudmodificacionaumentocauce%5Fv2%2FSolicitudmodificacionaumentocauce%5Fv2%2Easp&IdArticulo=5231 [Fri May 13 10:14:48.022532 2016] [proxy:error] [pid 15364:tid 15408] [client 201.245.192.253:51411] AH00898: Error reading from remote server returned by /isolucionsda/BancoConocimiento/S/Solicitudmodificacionaumentocauce_v2/Solicitudmodificacionaumentocauce_v2.asp, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FS%2FSolicitudmodificacionaumentocauce%5Fv2%2FSolicitudmodificacionaumentocauce%5Fv2%2Easp&IdArticulo=5231 [Fri May 13 10:23:52.822289 2016] [proxy_http:error] [pid 15364:tid 15696] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:42000] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/Session.asp?Continue=1 [Fri May 13 10:23:52.822289 2016] [proxy:error] [pid 15364:tid 15696] [client 201.245.192.253:42000] AH00898: Error reading from remote server returned by /IsolucionSDA/Session.asp, referer: http://190.27.245.106/IsolucionSDA/Session.asp?Continue=1 [Fri May 13 10:24:38.483569 2016] [proxy_http:error] [pid 15364:tid 16152] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:42708] 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 [Fri May 13 10:24:38.483569 2016] [proxy:error] [pid 15364:tid 16152] [client 201.245.192.253:42708] 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 [Fri May 13 10:35:04.465869 2016] [proxy_http:error] [pid 15364:tid 15104] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:20712] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 10:35:04.465869 2016] [proxy:error] [pid 15364:tid 15104] [client 201.245.192.253:20712] AH00898: Error reading from remote server returned by /IsolucionSDA/g/Bgr_BarraSuperior.jpg, referer: http://190.27.245.106/IsolucionSDA/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 10:35:05.776271 2016] [proxy_http:error] [pid 15364:tid 15028] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:20714] 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& [Fri May 13 10:35:05.776271 2016] [proxy:error] [pid 15364:tid 15028] [client 201.245.192.253:20714] AH00898: Error reading from remote server returned by /IsolucionSDA/BarraFavoritos.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 10:35:56.928761 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 10:37:22.416911 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:36:30.580743 2016] [proxy_http:error] [pid 15364:tid 16008] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:49826] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/modulomeci.asp?codmodulo=3 [Fri May 13 11:36:30.580743 2016] [proxy:error] [pid 15364:tid 16008] [client 201.245.192.253:49826] AH00898: Error reading from remote server returned by /isolucionsda/g/img_flecha01.jpg, referer: http://190.27.245.106/isolucionsda/modulomeci.asp?codmodulo=3 [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:40:45.141990 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:41:21.365254 2016] [proxy_http:error] [pid 15364:tid 15060] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:35778] 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 [Fri May 13 11:41:21.365254 2016] [proxy:error] [pid 15364:tid 15060] [client 201.245.192.253:35778] 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 [Fri May 13 11:41:21.412054 2016] [proxy_http:error] [pid 15364:tid 16224] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:35777] 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 [Fri May 13 11:41:21.412054 2016] [proxy:error] [pid 15364:tid 16224] [client 201.245.192.253:35777] AH00898: Error reading from remote server returned by /IsolucionSDA/Menu.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Fri May 13 11:41:44.671695 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 11:41:58.555719 2016] [core:error] [pid 15364:tid 15720] [client 198.20.99.130:50023] AH00135: Invalid method in request quit [Fri May 13 11:45:07.160050 2016] [proxy_http:error] [pid 15364:tid 16140] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:49903] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FL%2FListadeChequeoPermisodeVertimientosalAlcantarilladoPublico%5Fv2%5F0%2FListadeChequeoPermisodeVertimientosalAlcantarilladoPublico%5Fv2%5F0%2Easp&IdArticulo=4871 [Fri May 13 11:45:07.160050 2016] [proxy:error] [pid 15364:tid 16140] [client 201.245.192.253:49903] AH00898: Error reading from remote server returned by /isolucionsda/BancoConocimiento/L/ListadeChequeoPermisodeVertimientosalAlcantarilladoPublico_v2_0/ListadeChequeoPermisodeVertimientosalAlcantarilladoPublico_v2_0.asp, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FL%2FListadeChequeoPermisodeVertimientosalAlcantarilladoPublico%5Fv2%5F0%2FListadeChequeoPermisodeVertimientosalAlcantarilladoPublico%5Fv2%5F0%2Easp&IdArticulo=4871 [Fri May 13 12:13:34.754650 2016] [proxy_http:error] [pid 15364:tid 15300] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:58966] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FI%2FInformeTecnicoDeterminaciondeCargasContaminantes%2DOtrosUsuarios%5Fv2%5F0%2FInformeTecnicoDeterminaciondeCargasContaminantes%2DOtrosUsuarios%5Fv2%5F0%2Easp&IdArticulo=5120 [Fri May 13 12:13:34.754650 2016] [proxy:error] [pid 15364:tid 15300] [client 201.245.192.253:58966] AH00898: Error reading from remote server returned by /isolucionsda/BancoConocimiento/I/InformeTecnicoDeterminaciondeCargasContaminantes-OtrosUsuarios_v2_0/126pm04-pr108-f-a301.xlsx, referer: http://190.27.245.106/isolucionsda/FramesetArticulo.asp?Pagina=BancoConocimiento%2FI%2FInformeTecnicoDeterminaciondeCargasContaminantes%2DOtrosUsuarios%5Fv2%5F0%2FInformeTecnicoDeterminaciondeCargasContaminantes%2DOtrosUsuarios%5Fv2%5F0%2Easp&IdArticulo=5120 [Fri May 13 12:29:56.464374 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 12:53:02.760809 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 12:56:24.203963 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 13:51:53.858211 2016] [proxy_http:error] [pid 15364:tid 14796] (OS 10053)An established connection was aborted by the software in your host machine. : [client 186.84.196.182:53426] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/Session.asp?Continue=1 [Fri May 13 13:51:53.858211 2016] [proxy:error] [pid 15364:tid 14796] [client 186.84.196.182:53426] AH00898: Error reading from remote server returned by /IsolucionSDA/Session.asp, referer: http://190.27.245.106/IsolucionSDA/Session.asp?Continue=1 [Fri May 13 14:02:15.862503 2016] [proxy_http:error] [pid 15364:tid 14908] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:47449] 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 [Fri May 13 14:04:16.934316 2016] [proxy_http:error] [pid 15364:tid 14912] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:55327] 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& [Fri May 13 14:04:16.934316 2016] [proxy:error] [pid 15364:tid 14912] [client 201.245.192.253:55327] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Fri May 13 14:05:17.727623 2016] [proxy:error] [pid 15364:tid 15356] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:05:17.727623 2016] [proxy:error] [pid 15364:tid 15356] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 14:05:17.727623 2016] [proxy_http:error] [pid 15364:tid 15356] [client 201.245.179.194:47254] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://metadatos.ideca.gov.co/geoportal/catalog/search/resource/details.page?uuid=%7BE28D0804-C2F6-407E-AA0C-5ED9DBC4328C%7D [Fri May 13 14:14:17.457371 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 14:14:17.457371 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 14:33:54.167438 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 14:56:54.988263 2016] [proxy:error] [pid 15364:tid 14836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:54.988263 2016] [proxy:error] [pid 15364:tid 14836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 14:56:54.988263 2016] [proxy_http:error] [pid 15364:tid 14836] [client 190.60.208.211:27907] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:56:54.988263 2016] [proxy:error] [pid 15364:tid 16244] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:54.988263 2016] [proxy_http:error] [pid 15364:tid 16244] [client 190.60.208.211:27905] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:56:54.988263 2016] [proxy:error] [pid 15364:tid 15152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:54.988263 2016] [proxy_http:error] [pid 15364:tid 15152] [client 190.60.208.211:27906] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:56:55.019463 2016] [proxy:error] [pid 15364:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:55.019463 2016] [proxy_http:error] [pid 15364:tid 16260] [client 190.60.208.211:27908] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:56:55.487464 2016] [proxy:error] [pid 15364:tid 16008] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:55.487464 2016] [proxy_http:error] [pid 15364:tid 16008] [client 190.60.208.211:27941] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:56:55.503064 2016] [proxy:error] [pid 15364:tid 15600] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:56:55.503064 2016] [proxy_http:error] [pid 15364:tid 15600] [client 190.60.208.211:27940] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/;jsessionid=A708557D170F59FEFD7419F409CFA97E [Fri May 13 14:57:03.006677 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.006677 2016] [proxy:error] [pid 15364:tid 14864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.006677 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:28340] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:03.006677 2016] [proxy_http:error] [pid 15364:tid 14864] [client 190.60.208.211:28341] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:03.022277 2016] [proxy:error] [pid 15364:tid 15520] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.022277 2016] [proxy_http:error] [pid 15364:tid 15520] [client 190.60.208.211:28342] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:03.037877 2016] [proxy:error] [pid 15364:tid 15132] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.037877 2016] [proxy:error] [pid 15364:tid 15132] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 14:57:03.037877 2016] [proxy_http:error] [pid 15364:tid 15132] [client 190.60.208.211:28344] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:03.037877 2016] [proxy:error] [pid 15364:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 14:57:03.053477 2016] [proxy:error] [pid 15364:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 14:57:03.053477 2016] [proxy:error] [pid 15364:tid 15132] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 14:57:03.069077 2016] [proxy:error] [pid 15364:tid 15132] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 14:57:03.115877 2016] [proxy:error] [pid 15364:tid 15172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.115877 2016] [proxy_http:error] [pid 15364:tid 15172] [client 190.60.208.211:28354] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:03.256277 2016] [proxy:error] [pid 15364:tid 14716] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:03.256277 2016] [proxy_http:error] [pid 15364:tid 14716] [client 190.60.208.211:28370] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:24.051114 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:24.051114 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:24893] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 14:57:24.066714 2016] [proxy:error] [pid 15364:tid 14864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 14:57:24.066714 2016] [proxy_http:error] [pid 15364:tid 14864] [client 190.60.208.211:24892] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:55.887551 2016] [proxy:error] [pid 15364:tid 15720] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:55.887551 2016] [proxy:error] [pid 15364:tid 15720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:12:55.887551 2016] [proxy_http:error] [pid 15364:tid 15720] [client 190.60.208.211:25979] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:55.903151 2016] [proxy:error] [pid 15364:tid 15356] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:55.903151 2016] [proxy_http:error] [pid 15364:tid 15356] [client 190.60.208.211:25980] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:55.903151 2016] [proxy:error] [pid 15364:tid 15520] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:55.903151 2016] [proxy_http:error] [pid 15364:tid 15520] [client 190.60.208.211:25981] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:55.934351 2016] [proxy:error] [pid 15364:tid 14844] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:55.934351 2016] [proxy_http:error] [pid 15364:tid 14844] [client 190.60.208.211:25982] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:56.215151 2016] [proxy:error] [pid 15364:tid 15512] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:56.215151 2016] [proxy_http:error] [pid 15364:tid 15512] [client 190.60.208.211:25988] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:12:56.246351 2016] [proxy:error] [pid 15364:tid 16152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:12:56.246351 2016] [proxy_http:error] [pid 15364:tid 16152] [client 190.60.208.211:25989] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.114776 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.114776 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:26283] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.114776 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.114776 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:26284] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.130376 2016] [proxy:error] [pid 15364:tid 15096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.130376 2016] [proxy_http:error] [pid 15364:tid 15096] [client 190.60.208.211:26282] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.145976 2016] [proxy:error] [pid 15364:tid 14680] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.145976 2016] [proxy:error] [pid 15364:tid 14680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:13:10.145976 2016] [proxy_http:error] [pid 15364:tid 14680] [client 190.60.208.211:26285] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.145976 2016] [proxy:error] [pid 15364:tid 15096] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:13:10.161576 2016] [proxy:error] [pid 15364:tid 15096] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:13:10.161576 2016] [proxy:error] [pid 15364:tid 14680] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:13:10.177176 2016] [proxy:error] [pid 15364:tid 14680] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:13:10.333176 2016] [proxy:error] [pid 15364:tid 15252] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.333176 2016] [proxy_http:error] [pid 15364:tid 15252] [client 190.60.208.211:26288] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:10.473576 2016] [proxy:error] [pid 15364:tid 15340] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:10.473576 2016] [proxy_http:error] [pid 15364:tid 15340] [client 190.60.208.211:26290] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:31.143613 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:31.143613 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:26947] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:13:31.159213 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:13:31.159213 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:26948] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.224524 2016] [proxy:error] [pid 15364:tid 15512] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.224524 2016] [proxy:error] [pid 15364:tid 15512] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:18:22.224524 2016] [proxy_http:error] [pid 15364:tid 15512] [client 190.60.208.211:26112] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.240124 2016] [proxy:error] [pid 15364:tid 16116] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.240124 2016] [proxy_http:error] [pid 15364:tid 16116] [client 190.60.208.211:26108] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.240124 2016] [proxy:error] [pid 15364:tid 15028] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.240124 2016] [proxy_http:error] [pid 15364:tid 15028] [client 190.60.208.211:26113] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.240124 2016] [proxy:error] [pid 15364:tid 15252] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.240124 2016] [proxy_http:error] [pid 15364:tid 15252] [client 190.60.208.211:26109] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.458524 2016] [proxy:error] [pid 15364:tid 15452] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.458524 2016] [proxy_http:error] [pid 15364:tid 15452] [client 190.60.208.211:26131] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:22.458524 2016] [proxy:error] [pid 15364:tid 14932] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:22.458524 2016] [proxy_http:error] [pid 15364:tid 14932] [client 190.60.208.211:26128] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.528533 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.528533 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:26396] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.528533 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.528533 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:26398] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.528533 2016] [proxy:error] [pid 15364:tid 14644] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.528533 2016] [proxy_http:error] [pid 15364:tid 14644] [client 190.60.208.211:26394] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.528533 2016] [proxy:error] [pid 15364:tid 15164] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.528533 2016] [proxy_http:error] [pid 15364:tid 15164] [client 190.60.208.211:26395] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.528533 2016] [proxy:error] [pid 15364:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.528533 2016] [proxy_http:error] [pid 15364:tid 16260] [client 190.60.208.211:26397] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.606533 2016] [proxy:error] [pid 15364:tid 15960] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:27.606533 2016] [proxy:error] [pid 15364:tid 15960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:18:27.606533 2016] [proxy_http:error] [pid 15364:tid 15960] [client 190.60.208.211:26399] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:27.622133 2016] [proxy:error] [pid 15364:tid 15300] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:18:48.572970 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:48.572970 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:27119] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:48.572970 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:48.572970 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:27118] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:48.572970 2016] [proxy:error] [pid 15364:tid 15164] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:48.572970 2016] [proxy_http:error] [pid 15364:tid 15164] [client 190.60.208.211:27116] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:48.572970 2016] [proxy:error] [pid 15364:tid 14644] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:48.572970 2016] [proxy_http:error] [pid 15364:tid 14644] [client 190.60.208.211:27117] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:18:48.572970 2016] [proxy:error] [pid 15364:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:18:48.572970 2016] [proxy_http:error] [pid 15364:tid 16260] [client 190.60.208.211:27115] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.721048 2016] [proxy:error] [pid 15364:tid 15864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.721048 2016] [proxy:error] [pid 15364:tid 15864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:19:32.721048 2016] [proxy_http:error] [pid 15364:tid 15864] [client 190.60.208.211:28132] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.721048 2016] [proxy:error] [pid 15364:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.721048 2016] [proxy_http:error] [pid 15364:tid 16260] [client 190.60.208.211:28130] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.721048 2016] [proxy:error] [pid 15364:tid 15576] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.721048 2016] [proxy_http:error] [pid 15364:tid 15576] [client 190.60.208.211:28131] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.752248 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.752248 2016] [proxy:error] [pid 15364:tid 15548] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:19:32.752248 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:28134] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.767848 2016] [proxy:error] [pid 15364:tid 14660] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.767848 2016] [proxy_http:error] [pid 15364:tid 14660] [client 190.60.208.211:28135] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.861448 2016] [proxy:error] [pid 15364:tid 14932] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:32.861448 2016] [proxy:error] [pid 15364:tid 14932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:19:32.861448 2016] [proxy_http:error] [pid 15364:tid 14932] [client 190.60.208.211:28141] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:32.877048 2016] [proxy:error] [pid 15364:tid 14932] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:19:53.749885 2016] [proxy:error] [pid 15364:tid 15864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:53.749885 2016] [proxy_http:error] [pid 15364:tid 15864] [client 190.60.208.211:24594] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:53.765485 2016] [proxy:error] [pid 15364:tid 15576] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:53.765485 2016] [proxy_http:error] [pid 15364:tid 15576] [client 190.60.208.211:24592] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:53.765485 2016] [proxy:error] [pid 15364:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:53.765485 2016] [proxy_http:error] [pid 15364:tid 16260] [client 190.60.208.211:24593] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:53.781085 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:53.781085 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:24595] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:19:53.796685 2016] [proxy:error] [pid 15364:tid 14660] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:19:53.796685 2016] [proxy_http:error] [pid 15364:tid 14660] [client 190.60.208.211:24598] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:30.164475 2016] [proxy:error] [pid 15364:tid 15380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:30.164475 2016] [proxy:error] [pid 15364:tid 15380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:25:30.164475 2016] [proxy_http:error] [pid 15364:tid 15380] [client 190.60.208.211:28087] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:30.164475 2016] [proxy:error] [pid 15364:tid 14844] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:30.164475 2016] [proxy_http:error] [pid 15364:tid 14844] [client 190.60.208.211:28089] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:30.180075 2016] [proxy:error] [pid 15364:tid 15696] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:30.180075 2016] [proxy_http:error] [pid 15364:tid 15696] [client 190.60.208.211:28088] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:30.211275 2016] [proxy:error] [pid 15364:tid 16372] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:30.211275 2016] [proxy:error] [pid 15364:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 15:25:30.211275 2016] [proxy_http:error] [pid 15364:tid 16372] [client 190.60.208.211:28090] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:30.226876 2016] [proxy:error] [pid 15364:tid 16372] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:25:30.242476 2016] [proxy:error] [pid 15364:tid 16372] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:25:30.258076 2016] [proxy:error] [pid 15364:tid 16372] AH00940: HTTP: disabled connection for (172.22.1.51) [Fri May 13 15:25:32.301679 2016] [proxy:error] [pid 15364:tid 14680] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:32.301679 2016] [proxy_http:error] [pid 15364:tid 14680] [client 190.60.208.211:28167] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:32.332879 2016] [proxy:error] [pid 15364:tid 15528] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:32.332879 2016] [proxy_http:error] [pid 15364:tid 15528] [client 190.60.208.211:28170] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:51.193312 2016] [proxy:error] [pid 15364:tid 15380] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:51.193312 2016] [proxy_http:error] [pid 15364:tid 15380] [client 190.60.208.211:24776] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:51.193312 2016] [proxy:error] [pid 15364:tid 14844] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:51.193312 2016] [proxy_http:error] [pid 15364:tid 14844] [client 190.60.208.211:24775] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 15:25:51.193312 2016] [proxy:error] [pid 15364:tid 15696] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 15:25:51.193312 2016] [proxy_http:error] [pid 15364:tid 15696] [client 190.60.208.211:24777] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:18.748886 2016] [proxy:error] [pid 15364:tid 15528] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:18.748886 2016] [proxy:error] [pid 15364:tid 15528] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 16:45:18.748886 2016] [proxy_http:error] [pid 15364:tid 15528] [client 190.60.208.211:26355] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:18.764486 2016] [proxy:error] [pid 15364:tid 15164] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:18.764486 2016] [proxy_http:error] [pid 15364:tid 15164] [client 190.60.208.211:26354] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:18.780086 2016] [proxy:error] [pid 15364:tid 15096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:18.780086 2016] [proxy_http:error] [pid 15364:tid 15096] [client 190.60.208.211:26353] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:18.780086 2016] [proxy:error] [pid 15364:tid 15300] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:18.780086 2016] [proxy_http:error] [pid 15364:tid 15300] [client 190.60.208.211:26352] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:19.310487 2016] [proxy:error] [pid 15364:tid 15520] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:19.310487 2016] [proxy_http:error] [pid 15364:tid 15520] [client 190.60.208.211:26363] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:19.310487 2016] [proxy:error] [pid 15364:tid 14800] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:19.310487 2016] [proxy_http:error] [pid 15364:tid 14800] [client 190.60.208.211:26364] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.023294 2016] [proxy:error] [pid 15364:tid 16288] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.023294 2016] [proxy_http:error] [pid 15364:tid 16288] [client 190.60.208.211:26488] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.023294 2016] [proxy:error] [pid 15364:tid 16152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.023294 2016] [proxy_http:error] [pid 15364:tid 16152] [client 190.60.208.211:26491] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.023294 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.023294 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:26490] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.038894 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.038894 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:26493] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.038894 2016] [proxy:error] [pid 15364:tid 16244] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.038894 2016] [proxy_http:error] [pid 15364:tid 16244] [client 190.60.208.211:26489] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:23.038894 2016] [proxy:error] [pid 15364:tid 15768] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:23.038894 2016] [proxy_http:error] [pid 15364:tid 15768] [client 190.60.208.211:26492] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.067731 2016] [proxy:error] [pid 15364:tid 15656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.067731 2016] [proxy:error] [pid 15364:tid 15656] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 16:45:44.067731 2016] [proxy:error] [pid 15364:tid 15768] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.067731 2016] [proxy_http:error] [pid 15364:tid 15768] [client 190.60.208.211:26764] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.067731 2016] [proxy_http:error] [pid 15364:tid 15656] [client 190.60.208.211:26762] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.067731 2016] [proxy:error] [pid 15364:tid 14908] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.067731 2016] [proxy_http:error] [pid 15364:tid 14908] [client 190.60.208.211:26763] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.098931 2016] [proxy:error] [pid 15364:tid 16288] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.098931 2016] [proxy:error] [pid 15364:tid 16152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.098931 2016] [proxy_http:error] [pid 15364:tid 16288] [client 190.60.208.211:26767] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.098931 2016] [proxy_http:error] [pid 15364:tid 16152] [client 190.60.208.211:26766] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 16:45:44.098931 2016] [proxy:error] [pid 15364:tid 16244] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 16:45:44.098931 2016] [proxy_http:error] [pid 15364:tid 16244] [client 190.60.208.211:26765] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 17:00:50.632123 2016] [core:error] [pid 15364:tid 15060] (20024)The given path is misformatted or contained invalid characters: [client 207.182.136.170:64450] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Fri May 13 17:25:31.074723 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 18:01:31.600518 2016] [proxy:error] [pid 15364:tid 15308] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:31.600518 2016] [proxy:error] [pid 15364:tid 15308] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 18:01:31.600518 2016] [proxy_http:error] [pid 15364:tid 15308] [client 190.60.208.211:26772] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:31.616118 2016] [proxy:error] [pid 15364:tid 14800] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:31.616118 2016] [proxy_http:error] [pid 15364:tid 14800] [client 190.60.208.211:26770] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:31.631718 2016] [proxy:error] [pid 15364:tid 14940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:31.631718 2016] [proxy:error] [pid 15364:tid 15104] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:31.631718 2016] [proxy_http:error] [pid 15364:tid 14940] [client 190.60.208.211:26769] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:31.631718 2016] [proxy_http:error] [pid 15364:tid 15104] [client 190.60.208.211:26771] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:32.380519 2016] [proxy:error] [pid 15364:tid 15340] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:32.380519 2016] [proxy_http:error] [pid 15364:tid 15340] [client 190.60.208.211:26786] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:32.427319 2016] [proxy:error] [pid 15364:tid 16328] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:32.427319 2016] [proxy_http:error] [pid 15364:tid 16328] [client 190.60.208.211:26785] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.420926 2016] [proxy:error] [pid 15364:tid 16224] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.420926 2016] [proxy_http:error] [pid 15364:tid 16224] [client 190.60.208.211:26825] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.420926 2016] [proxy:error] [pid 15364:tid 14708] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.420926 2016] [proxy_http:error] [pid 15364:tid 14708] [client 190.60.208.211:26824] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.420926 2016] [proxy:error] [pid 15364:tid 15172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.420926 2016] [proxy_http:error] [pid 15364:tid 15172] [client 190.60.208.211:26828] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.436526 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.436526 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:26823] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.436526 2016] [proxy:error] [pid 15364:tid 15376] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.436526 2016] [proxy_http:error] [pid 15364:tid 15376] [client 190.60.208.211:26827] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:36.436526 2016] [proxy:error] [pid 15364:tid 14864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:36.436526 2016] [proxy_http:error] [pid 15364:tid 14864] [client 190.60.208.211:26826] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.449763 2016] [proxy:error] [pid 15364:tid 14864] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.449763 2016] [proxy:error] [pid 15364:tid 14864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Fri May 13 18:01:57.449763 2016] [proxy_http:error] [pid 15364:tid 14864] [client 190.60.208.211:27049] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.449763 2016] [proxy:error] [pid 15364:tid 14708] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.449763 2016] [proxy_http:error] [pid 15364:tid 14708] [client 190.60.208.211:27048] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.449763 2016] [proxy:error] [pid 15364:tid 15172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.449763 2016] [proxy_http:error] [pid 15364:tid 15172] [client 190.60.208.211:27047] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.480963 2016] [proxy:error] [pid 15364:tid 15548] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.480963 2016] [proxy_http:error] [pid 15364:tid 15548] [client 190.60.208.211:27051] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.480963 2016] [proxy:error] [pid 15364:tid 16224] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.480963 2016] [proxy_http:error] [pid 15364:tid 16224] [client 190.60.208.211:27052] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:01:57.480963 2016] [proxy:error] [pid 15364:tid 15376] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Fri May 13 18:01:57.480963 2016] [proxy_http:error] [pid 15364:tid 15376] [client 190.60.208.211:27050] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://localhost:8080/es/ [Fri May 13 18:28:47.700192 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 20:16:29.309541 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 20:21:43.634493 2016] [core:error] [pid 15364:tid 16152] [client 93.158.212.100:62277] AH00135: Invalid method in request SXEX / HTTP/1.1 [Fri May 13 20:21:44.960495 2016] [core:error] [pid 15364:tid 15028] [client 93.158.212.100:31216] AH00135: Invalid method in request TTJK / HTTP/1.1 [Fri May 13 21:34:05.090918 2016] [mpm_winnt:warn] [pid 15364:tid 17052] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Fri May 13 22:55:52.843938 2016] [core:error] [pid 15364:tid 14884] (20024)The given path is misformatted or contained invalid characters: [client 207.46.13.160:10432] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0312 ]-- |