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: [Thu Mar 02 02:43:28.438910 2017] [core:error] [pid 5032:tid 16388] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:22380] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 02:43:38.719328 2017] [core:error] [pid 5032:tid 16388] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:22380] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 02:43:39.982930 2017] [core:error] [pid 5032:tid 16388] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:22735] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 02:43:50.263348 2017] [core:error] [pid 5032:tid 16388] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:22735] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 02:44:30.901419 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 03:18:31.634604 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 03:20:18.666392 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 04:53:22.430999 2017] [core:error] [pid 5032:tid 16400] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21472] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 04:53:35.909423 2017] [core:error] [pid 5032:tid 16400] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21472] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 04:53:38.811028 2017] [core:error] [pid 5032:tid 16400] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:17816] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 04:53:49.247446 2017] [core:error] [pid 5032:tid 16400] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:17816] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 04:54:44.518343 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 05:23:13.017744 2017] [core:error] [pid 5032:tid 15832] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:61822] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 05:23:16.777351 2017] [core:error] [pid 5032:tid 15832] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:61857] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 05:23:27.057769 2017] [core:error] [pid 5032:tid 15832] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:61857] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 05:39:33.136266 2017] [core:error] [pid 5032:tid 15568] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21005] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 05:39:43.557084 2017] [core:error] [pid 5032:tid 15568] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21005] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 05:39:44.664686 2017] [core:error] [pid 5032:tid 15568] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21156] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 05:39:55.147904 2017] [core:error] [pid 5032:tid 15568] (20024)The given path is misformatted or contained invalid characters: [client 120.37.67.177:21156] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 07:13:57.553015 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 07:16:38.982098 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 07:41:01.671867 2017] [proxy_http:error] [pid 5032:tid 16136] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:10541] 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 [Thu Mar 02 07:41:01.671867 2017] [proxy:error] [pid 5032:tid 16136] [client 201.245.192.253:10541] 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 [Thu Mar 02 07:46:03.438797 2017] [proxy_http:error] [pid 5032:tid 16388] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:13570] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Thu Mar 02 07:46:03.438797 2017] [proxy:error] [pid 5032:tid 16388] [client 201.245.192.253:13570] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Thu Mar 02 07:55:32.652597 2017] [proxy_http:error] [pid 5032:tid 15348] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:20177] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Thu Mar 02 07:55:32.652597 2017] [proxy:error] [pid 5032:tid 15348] [client 201.245.192.253:20177] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentosExternos3.asp [Thu Mar 02 08:30:03.805835 2017] [proxy_http:error] [pid 5032:tid 16388] (OS 10053)An established connection was aborted by the software in your host machine. : [client 190.25.100.159:29297] 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& [Thu Mar 02 08:30:03.805835 2017] [proxy:error] [pid 5032:tid 16388] [client 190.25.100.159:29297] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 08:48:54.542621 2017] [proxy_http:error] [pid 5032:tid 15196] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:25674] 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& [Thu Mar 02 08:48:54.542621 2017] [proxy:error] [pid 5032:tid 15196] [client 201.245.192.253:25674] AH00898: Error reading from remote server returned by /isolucionsda/g/shim.gif, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 08:49:01.469033 2017] [proxy_http:error] [pid 5032:tid 15300] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:25804] 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& [Thu Mar 02 08:49:01.469033 2017] [proxy:error] [pid 5032:tid 15300] [client 201.245.192.253:25804] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 08:58:54.706875 2017] [proxy_http:error] [pid 5032:tid 15800] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:24008] 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& [Thu Mar 02 08:58:54.706875 2017] [proxy:error] [pid 5032:tid 15800] [client 201.245.192.253:24008] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 08:58:54.706875 2017] [proxy_http:error] [pid 5032:tid 15420] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:24007] 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& [Thu Mar 02 08:58:54.706875 2017] [proxy:error] [pid 5032:tid 15420] [client 201.245.192.253:24007] AH00898: Error reading from remote server returned by /isolucionsda/MagazinHome.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 09:27:01.678238 2017] [proxy:error] [pid 5032:tid 16400] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 09:27:01.678238 2017] [proxy:error] [pid 5032:tid 16400] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 09:27:01.678238 2017] [proxy_http:error] [pid 5032:tid 16400] [client 201.245.192.253:21821] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 09:27:48.556320 2017] [proxy:error] [pid 5032:tid 15864] AH00940: HTTP: disabled connection for (172.22.1.26) [Thu Mar 02 09:30:24.899795 2017] [core:error] [pid 5032:tid 15704] (20024)The given path is misformatted or contained invalid characters: [client 65.208.151.116:8452] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file, referer: http://www.dama.gov.co/ [Thu Mar 02 09:58:53.336796 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 09:58:53.336796 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 09:58:53.336796 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 09:58:53.352396 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 09:58:53.352396 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 09:58:53.352396 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:06:31.369200 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:06:31.369200 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:06:31.369200 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:06:31.369200 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:06:31.369200 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 10:21:54.391621 2017] [proxy_http:error] [pid 5032:tid 15276] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:11626] 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 [Thu Mar 02 10:21:54.391621 2017] [proxy:error] [pid 5032:tid 15276] [client 201.245.192.253:11626] 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 [Thu Mar 02 10:54:35.970267 2017] [proxy_http:error] [pid 5032:tid 16456] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:18105] 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& [Thu Mar 02 10:54:35.970267 2017] [proxy:error] [pid 5032:tid 16456] [client 201.245.192.253:18105] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 11:04:22.500097 2017] [proxy_http:error] [pid 5032:tid 16320] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:23427] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Mar 02 11:04:22.500097 2017] [proxy:error] [pid 5032:tid 16320] [client 201.245.192.253:23427] AH00898: Error reading from remote server returned by /IsolucionSDA/g/Bot_CalibracionOff_ESP.jpg, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Mar 02 11:52:39.908786 2017] [proxy_http:error] [pid 5032:tid 16440] (OS 10053)An established connection was aborted by the software in your host machine. : [client 190.145.134.217:53898] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Mar 02 11:58:14.139373 2017] [proxy_http:error] [pid 5032:tid 15624] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19523] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:14.139373 2017] [proxy:error] [pid 5032:tid 15624] [client 201.245.192.253:19523] AH00898: Error reading from remote server returned by /sipse/faces/bienvenido.xhtml, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:14.529374 2017] [proxy_http:error] [pid 5032:tid 16188] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:18716] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:14.950574 2017] [proxy_http:error] [pid 5032:tid 15244] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19525] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse [Thu Mar 02 11:58:14.950574 2017] [proxy:error] [pid 5032:tid 15244] [client 201.245.192.253:19525] AH00898: Error reading from remote server returned by /sipse/faces/javax.faces.resource/images/ui-bg_flat_0_2d5972_40x100.png, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse [Thu Mar 02 11:58:15.917776 2017] [proxy_http:error] [pid 5032:tid 15196] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:29335] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/autenticacion.xhtml [Thu Mar 02 11:58:20.348184 2017] [proxy_http:error] [pid 5032:tid 16112] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:29526] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:23.078189 2017] [proxy_http:error] [pid 5032:tid 16100] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19325] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:24.294991 2017] [proxy_http:error] [pid 5032:tid 15888] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:29827] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/presentacion/sistema/anexos/cargarAnexoSolicitudProceso.xhtml [Thu Mar 02 11:58:25.714593 2017] [proxy_http:error] [pid 5032:tid 15356] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19930] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:25.714593 2017] [proxy:error] [pid 5032:tid 15356] [client 201.245.192.253:19930] AH00898: Error reading from remote server returned by /isolucionsda/ActualizarActividad.aspx, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:32.485005 2017] [proxy_http:error] [pid 5032:tid 15872] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19997] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:32.485005 2017] [proxy:error] [pid 5032:tid 15872] [client 201.245.192.253:19997] AH00898: Error reading from remote server returned by /isolucionsda/ActualizarActividad.aspx, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:34.466209 2017] [proxy_http:error] [pid 5032:tid 15168] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:19988] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:34.466209 2017] [proxy:error] [pid 5032:tid 15168] [client 201.245.192.253:19988] AH00898: Error reading from remote server returned by /isolucionsda/ActualizarActividad.aspx, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:36.743813 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:36.743813 2017] [proxy:error] [pid 5032:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 11:58:36.743813 2017] [proxy_http:error] [pid 5032:tid 16372] [client 201.245.192.253:20194] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse [Thu Mar 02 11:58:36.759413 2017] [proxy:error] [pid 5032:tid 16312] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:36.759413 2017] [proxy_http:error] [pid 5032:tid 16312] [client 201.245.192.253:20195] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/crearModificarSolicitudProceso.xhtml [Thu Mar 02 11:58:39.130617 2017] [proxy:error] [pid 5032:tid 15612] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:39.130617 2017] [proxy:error] [pid 5032:tid 15612] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:58:39.130617 2017] [proxy_http:error] [pid 5032:tid 15612] [client 201.245.192.253:20257] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:39.349017 2017] [proxy:error] [pid 5032:tid 15196] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:39.349017 2017] [proxy_http:error] [pid 5032:tid 15196] [client 201.245.192.253:20260] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:41.111820 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:41.111820 2017] [proxy:error] [pid 5032:tid 16152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:58:41.111820 2017] [proxy_http:error] [pid 5032:tid 16152] [client 201.245.192.253:20313] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:41.236621 2017] [proxy:error] [pid 5032:tid 16044] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:41.299021 2017] [proxy:error] [pid 5032:tid 16188] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:41.299021 2017] [proxy:error] [pid 5032:tid 16188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 11:58:41.299021 2017] [proxy_http:error] [pid 5032:tid 16188] [client 201.245.192.253:20223] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/proyectos/proyecto/proyecto.xhtml [Thu Mar 02 11:58:41.439421 2017] [proxy:error] [pid 5032:tid 16112] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:41.439421 2017] [proxy_http:error] [pid 5032:tid 16112] [client 201.245.192.253:30718] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:41.782621 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:41.782621 2017] [proxy_http:error] [pid 5032:tid 15792] [client 201.245.192.253:20345] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:45.370628 2017] [proxy:error] [pid 5032:tid 15664] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:45.370628 2017] [proxy_http:error] [pid 5032:tid 15664] [client 201.245.192.253:30841] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/sistema/anexos/cargarAnexoSolicitudProceso.xhtml [Thu Mar 02 11:58:48.131833 2017] [proxy:error] [pid 5032:tid 15400] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:48.131833 2017] [proxy:error] [pid 5032:tid 15400] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:58:48.131833 2017] [proxy_http:error] [pid 5032:tid 15400] [client 201.245.192.253:20507] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:48.319033 2017] [proxy:error] [pid 5032:tid 15888] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:48.319033 2017] [proxy_http:error] [pid 5032:tid 15888] [client 201.245.192.253:20514] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:48.521833 2017] [proxy:error] [pid 5032:tid 16100] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:48.521833 2017] [proxy_http:error] [pid 5032:tid 16100] [client 201.245.192.253:20523] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:48.802634 2017] [proxy:error] [pid 5032:tid 15496] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:48.802634 2017] [proxy_http:error] [pid 5032:tid 15496] [client 201.245.192.253:20529] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:49.239435 2017] [proxy:error] [pid 5032:tid 16440] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:49.239435 2017] [proxy:error] [pid 5032:tid 16440] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:58:49.239435 2017] [proxy_http:error] [pid 5032:tid 16440] [client 201.245.192.253:20540] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:49.442235 2017] [proxy:error] [pid 5032:tid 16144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:49.442235 2017] [proxy_http:error] [pid 5032:tid 16144] [client 201.245.192.253:20546] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/DetalleTareas.aspx?Number=68706553516557514551 [Thu Mar 02 11:58:52.063040 2017] [proxy:error] [pid 5032:tid 15244] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:52.063040 2017] [proxy:error] [pid 5032:tid 15244] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:58:52.063040 2017] [proxy_http:error] [pid 5032:tid 15244] [client 201.245.192.253:20608] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:58:54.153443 2017] [proxy_http:error] [pid 5032:tid 15392] (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.61:8080, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:54.153443 2017] [proxy:error] [pid 5032:tid 15392] [client 201.245.192.253:20714] AH00898: Error reading from remote server returned by /sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml, referer: http://190.27.245.106/sipse/faces/faces/autenticacion.xhtml [Thu Mar 02 11:58:56.477847 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:56.509047 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:56.540247 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:56.587047 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:56.633848 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:56.680648 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:57.055048 2017] [proxy:error] [pid 5032:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:57.070648 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:57.086248 2017] [proxy:error] [pid 5032:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 11:58:57.788250 2017] [proxy:error] [pid 5032:tid 15948] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:57.788250 2017] [proxy_http:error] [pid 5032:tid 15948] [client 201.245.192.253:20790] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:58:59.691453 2017] [proxy:error] [pid 5032:tid 16312] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:58:59.691453 2017] [proxy_http:error] [pid 5032:tid 16312] [client 201.245.192.253:20833] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 11:58:59.941053 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 11:58:59.941053 2017] [proxy_http:error] [pid 5032:tid 16372] [client 201.245.192.253:20840] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:02.093857 2017] [proxy:error] [pid 5032:tid 15196] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:02.093857 2017] [proxy_http:error] [pid 5032:tid 15196] [client 201.245.192.253:20861] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:02.140657 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:02.140657 2017] [proxy_http:error] [pid 5032:tid 16328] [client 201.245.192.253:20890] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:03.482260 2017] [proxy:error] [pid 5032:tid 16188] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:03.482260 2017] [proxy_http:error] [pid 5032:tid 16188] [client 201.245.192.253:20894] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:05.510263 2017] [proxy:error] [pid 5032:tid 16112] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:05.510263 2017] [proxy_http:error] [pid 5032:tid 16112] [client 201.245.192.253:21004] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:05.962664 2017] [proxy:error] [pid 5032:tid 16044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:05.962664 2017] [proxy_http:error] [pid 5032:tid 16044] [client 201.245.192.253:21013] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:08.427468 2017] [proxy:error] [pid 5032:tid 16364] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:08.427468 2017] [proxy_http:error] [pid 5032:tid 16364] [client 201.245.192.253:21075] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:08.427468 2017] [proxy:error] [pid 5032:tid 16024] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:08.427468 2017] [proxy_http:error] [pid 5032:tid 16024] [client 201.245.192.253:21074] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:09.831471 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:09.831471 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:21076] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:10.689472 2017] [proxy:error] [pid 5032:tid 16440] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:10.689472 2017] [proxy_http:error] [pid 5032:tid 16440] [client 201.245.192.253:21109] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:10.720672 2017] [proxy:error] [pid 5032:tid 16144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:10.720672 2017] [proxy_http:error] [pid 5032:tid 16144] [client 201.245.192.253:21110] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=MagazinHome.asp [Thu Mar 02 11:59:20.782690 2017] [proxy:error] [pid 5032:tid 16312] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:59:20.782690 2017] [proxy:error] [pid 5032:tid 16312] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 11:59:20.782690 2017] [proxy_http:error] [pid 5032:tid 16312] [client 201.245.192.253:21502] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 11:59:21.328691 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 11:59:21.328691 2017] [proxy_http:error] [pid 5032:tid 16372] [client 201.245.192.253:31762] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 11:59:28.239503 2017] [proxy:error] [pid 5032: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.43:7778 (172.22.1.43) failed [Thu Mar 02 11:59:28.239503 2017] [proxy:error] [pid 5032:tid 16152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.43) for 60s [Thu Mar 02 11:59:28.239503 2017] [proxy_http:error] [pid 5032:tid 16152] [client 190.25.157.12:61058] AH01114: HTTP: failed to make connection to backend: 172.22.1.43 [Thu Mar 02 11:59:30.719907 2017] [proxy:error] [pid 5032:tid 15168] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:31.796309 2017] [proxy:error] [pid 5032:tid 15748] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:32.872711 2017] [proxy:error] [pid 5032:tid 16144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:59:32.872711 2017] [proxy:error] [pid 5032:tid 16144] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 11:59:32.872711 2017] [proxy_http:error] [pid 5032:tid 16144] [client 201.245.192.253:32115] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 11:59:32.872711 2017] [proxy:error] [pid 5032:tid 15168] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:33.933513 2017] [proxy:error] [pid 5032:tid 15416] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:35.041115 2017] [proxy:error] [pid 5032:tid 15392] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:36.101917 2017] [proxy:error] [pid 5032:tid 16352] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:36.195517 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:59:36.195517 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:21953] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 11:59:37.162719 2017] [proxy:error] [pid 5032:tid 16488] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:38.535521 2017] [proxy:error] [pid 5032:tid 16488] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:39.611923 2017] [proxy:error] [pid 5032:tid 16488] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:40.703925 2017] [proxy:error] [pid 5032:tid 16488] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:41.749127 2017] [proxy:error] [pid 5032:tid 16388] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:42.794329 2017] [proxy:error] [pid 5032:tid 16388] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:43.839530 2017] [proxy:error] [pid 5032:tid 15416] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:43.901931 2017] [proxy:error] [pid 5032:tid 15148] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 11:59:43.901931 2017] [proxy:error] [pid 5032:tid 15148] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 11:59:43.901931 2017] [proxy_http:error] [pid 5032:tid 15148] [client 201.245.192.253:22125] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 11:59:44.884732 2017] [proxy:error] [pid 5032:tid 16072] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:45.914334 2017] [proxy:error] [pid 5032:tid 15416] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:46.975136 2017] [proxy:error] [pid 5032:tid 15416] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:48.004738 2017] [proxy:error] [pid 5032:tid 16152] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:49.065540 2017] [proxy:error] [pid 5032:tid 16144] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:50.079541 2017] [proxy:error] [pid 5032:tid 16112] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:50.173142 2017] [proxy:error] [pid 5032:tid 15872] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 11:59:50.173142 2017] [proxy:error] [pid 5032:tid 15872] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 11:59:50.173142 2017] [proxy_http:error] [pid 5032:tid 15872] [client 201.245.192.253:22298] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Session.asp?Continue=1 [Thu Mar 02 11:59:50.828343 2017] [proxy:error] [pid 5032:tid 15664] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 11:59:51.233943 2017] [proxy:error] [pid 5032:tid 15664] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:52.357145 2017] [proxy:error] [pid 5032:tid 15664] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:53.449147 2017] [proxy:error] [pid 5032:tid 16212] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:54.525549 2017] [proxy:error] [pid 5032:tid 15664] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:55.555151 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:56.927953 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:57.957555 2017] [proxy:error] [pid 5032:tid 16452] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 11:59:59.018357 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 12:00:00.110359 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 12:00:01.139961 2017] [proxy:error] [pid 5032:tid 15512] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 12:00:02.169563 2017] [proxy:error] [pid 5032:tid 16488] AH00940: HTTP: disabled connection for (172.22.1.43) [Thu Mar 02 12:00:02.403563 2017] [proxy:error] [pid 5032:tid 15392] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:02.403563 2017] [proxy_http:error] [pid 5032:tid 15392] [client 201.245.192.253:32800] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:08.986775 2017] [proxy:error] [pid 5032:tid 16100] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:09.688776 2017] [proxy:error] [pid 5032:tid 15888] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:19.703993 2017] [proxy:error] [pid 5032:tid 15820] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:33.010817 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:33.010817 2017] [proxy:error] [pid 5032:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:00:33.010817 2017] [proxy_http:error] [pid 5032:tid 16372] [client 201.245.192.253:33791] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:36.208822 2017] [proxy:error] [pid 5032:tid 15400] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:38.860827 2017] [proxy:error] [pid 5032:tid 15168] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:40.155629 2017] [proxy:error] [pid 5032:tid 15196] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:00:40.233630 2017] [proxy:error] [pid 5032:tid 15196] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:00:40.717230 2017] [proxy:error] [pid 5032:tid 15664] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:40.717230 2017] [proxy_http:error] [pid 5032:tid 15664] [client 201.245.192.253:11448] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:41.887232 2017] [proxy:error] [pid 5032:tid 15212] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:41.887232 2017] [proxy_http:error] [pid 5032:tid 15212] [client 201.245.192.253:34028] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:42.058833 2017] [proxy:error] [pid 5032:tid 16072] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:42.058833 2017] [proxy_http:error] [pid 5032:tid 16072] [client 201.245.192.253:34035] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 12:00:42.277233 2017] [proxy:error] [pid 5032:tid 16072] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:42.417633 2017] [proxy:error] [pid 5032:tid 15468] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:42.417633 2017] [proxy_http:error] [pid 5032:tid 15468] [client 201.245.192.253:11480] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:47.284842 2017] [proxy:error] [pid 5032:tid 15332] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:47.284842 2017] [proxy:error] [pid 5032:tid 15332] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:00:47.284842 2017] [proxy_http:error] [pid 5032:tid 15332] [client 201.245.192.253:11625] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:00:48.220844 2017] [proxy:error] [pid 5032:tid 15332] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:00:52.994452 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:00:52.994452 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:11770] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:01:06.192075 2017] [proxy_http:error] [pid 5032:tid 15468] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:34749] 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& [Thu Mar 02 12:01:06.192075 2017] [proxy:error] [pid 5032:tid 15468] [client 201.245.192.253:34749] AH00898: Error reading from remote server returned by /IsolucionSDA/IdentificaUsuario.asp, referer: http://190.27.245.106/IsolucionSDA/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 12:01:09.951682 2017] [proxy:error] [pid 5032:tid 15332] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:01:09.951682 2017] [proxy:error] [pid 5032:tid 15332] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:01:09.951682 2017] [proxy_http:error] [pid 5032:tid 15332] [client 201.245.192.253:34913] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 12:01:16.113693 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:01:16.113693 2017] [proxy:error] [pid 5032:tid 16388] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:01:16.113693 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:12798] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Thu Mar 02 12:01:43.772541 2017] [proxy:error] [pid 5032:tid 15212] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:01:43.772541 2017] [proxy:error] [pid 5032:tid 15212] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:01:43.772541 2017] [proxy_http:error] [pid 5032:tid 15212] [client 201.245.192.253:13843] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:01:46.034545 2017] [proxy:error] [pid 5032:tid 16044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:01:46.034545 2017] [proxy_http:error] [pid 5032:tid 16044] [client 201.245.192.253:23852] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:01:52.321356 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:01:52.321356 2017] [proxy_http:error] [pid 5032:tid 16388] [client 191.95.254.21:14723] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:01:55.394562 2017] [proxy:error] [pid 5032:tid 16364] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:01:55.394562 2017] [proxy_http:error] [pid 5032:tid 16364] [client 191.95.254.21:14766] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:02:11.712190 2017] [proxy:error] [pid 5032:tid 15236] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.43:80 (172.22.1.43) failed [Thu Mar 02 12:02:11.712190 2017] [proxy:error] [pid 5032:tid 15236] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.43) for 60s [Thu Mar 02 12:02:11.712190 2017] [proxy_http:error] [pid 5032:tid 15236] [client 191.95.254.21:14574] AH01114: HTTP: failed to make connection to backend: 172.22.1.43 [Thu Mar 02 12:02:18.560602 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 12:02:18.560602 2017] [proxy:error] [pid 5032:tid 15520] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:02:18.560602 2017] [proxy_http:error] [pid 5032:tid 15520] [client 201.245.192.253:24788] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 12:02:29.340221 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 12:02:29.340221 2017] [proxy_http:error] [pid 5032:tid 15792] [client 201.245.192.253:15371] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/proyectos/proyecto/proyecto.xhtml [Thu Mar 02 12:02:44.862248 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 12:02:44.862248 2017] [proxy:error] [pid 5032:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:02:44.862248 2017] [proxy_http:error] [pid 5032:tid 16372] [client 201.245.192.253:25512] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Thu Mar 02 12:02:50.462658 2017] [proxy:error] [pid 5032: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.61:8080 (172.22.1.61) failed [Thu Mar 02 12:02:50.462658 2017] [proxy:error] [pid 5032:tid 15792] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:02:50.462658 2017] [proxy_http:error] [pid 5032:tid 15792] [client 201.245.192.253:15979] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/proyectos/proyecto/proyecto.xhtml [Thu Mar 02 12:02:50.961859 2017] [proxy:error] [pid 5032:tid 15792] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:02:54.799466 2017] [proxy:error] [pid 5032:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:02:58.231472 2017] [proxy:error] [pid 5032:tid 15356] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:02:58.730673 2017] [proxy:error] [pid 5032:tid 16352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:02:58.730673 2017] [proxy_http:error] [pid 5032:tid 16352] [client 201.245.192.253:16259] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Session.asp?Continue=1 [Thu Mar 02 12:02:59.822675 2017] [proxy:error] [pid 5032:tid 15244] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:02:59.822675 2017] [proxy:error] [pid 5032:tid 15244] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:02:59.822675 2017] [proxy_http:error] [pid 5032:tid 15244] [client 201.245.192.253:26009] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Thu Mar 02 12:03:19.775110 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 12:03:19.775110 2017] [proxy_http:error] [pid 5032:tid 15520] [client 201.245.192.253:26613] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Thu Mar 02 12:03:21.459913 2017] [proxy:error] [pid 5032:tid 16044] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:03:22.895115 2017] [proxy:error] [pid 5032:tid 16212] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:03:26.186721 2017] [proxy:error] [pid 5032:tid 16212] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:04:07.682794 2017] [proxy:error] [pid 5032:tid 15236] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:04:07.682794 2017] [proxy:error] [pid 5032:tid 15236] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:04:07.682794 2017] [proxy_http:error] [pid 5032:tid 15236] [client 201.245.192.253:28100] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Thu Mar 02 12:04:18.556013 2017] [proxy:error] [pid 5032:tid 16336] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:04:54.576476 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 12:04:54.576476 2017] [proxy:error] [pid 5032:tid 15864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:04:54.576476 2017] [proxy_http:error] [pid 5032:tid 15864] [client 201.245.192.253:29322] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:04:54.654476 2017] [proxy:error] [pid 5032:tid 15236] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:04:54.654476 2017] [proxy_http:error] [pid 5032:tid 15236] [client 201.245.192.253:29324] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:04:55.216077 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:04:55.216077 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:29340] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:04:56.854080 2017] [proxy:error] [pid 5032:tid 16024] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:04:56.854080 2017] [proxy_http:error] [pid 5032:tid 16024] [client 201.245.192.253:29363] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/IsolucionSDA/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:06:43.433467 2017] [proxy:error] [pid 5032:tid 15188] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:06:43.433467 2017] [proxy:error] [pid 5032:tid 15188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:06:43.433467 2017] [proxy_http:error] [pid 5032:tid 15188] [client 201.245.192.253:32346] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:06:47.817075 2017] [proxy:error] [pid 5032:tid 16420] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 12:06:47.817075 2017] [proxy:error] [pid 5032:tid 16420] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:06:47.817075 2017] [proxy_http:error] [pid 5032:tid 16420] [client 181.142.133.228:49395] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:06:48.534676 2017] [proxy:error] [pid 5032:tid 16452] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:06:48.534676 2017] [proxy_http:error] [pid 5032:tid 16452] [client 201.245.192.253:32485] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:06:49.611078 2017] [proxy:error] [pid 5032:tid 15468] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:06:49.611078 2017] [proxy_http:error] [pid 5032:tid 15468] [client 152.204.131.54:51664] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 12:07:17.176327 2017] [proxy:error] [pid 5032:tid 15416] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:07:17.176327 2017] [proxy:error] [pid 5032:tid 15416] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:07:17.176327 2017] [proxy_http:error] [pid 5032:tid 15416] [client 201.245.192.253:10949] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Thu Mar 02 12:09:13.146930 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:09:13.146930 2017] [proxy:error] [pid 5032:tid 16388] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:09:13.146930 2017] [proxy_http:error] [pid 5032:tid 16388] [client 190.145.134.217:54125] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Thu Mar 02 12:09:21.508545 2017] [proxy:error] [pid 5032:tid 15848] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:09:21.508545 2017] [proxy:error] [pid 5032:tid 15848] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:09:21.508545 2017] [proxy_http:error] [pid 5032:tid 15848] [client 201.245.192.253:24279] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 12:09:21.586545 2017] [proxy:error] [pid 5032:tid 15848] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:21.633345 2017] [proxy:error] [pid 5032:tid 15848] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:21.695745 2017] [proxy:error] [pid 5032:tid 15848] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:21.742546 2017] [proxy:error] [pid 5032:tid 15848] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:21.773746 2017] [proxy:error] [pid 5032:tid 15848] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:23.006148 2017] [proxy:error] [pid 5032:tid 16412] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:38.684175 2017] [proxy:error] [pid 5032:tid 16388] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:09:49.479394 2017] [proxy:error] [pid 5032:tid 15584] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:09:58.839411 2017] [proxy:error] [pid 5032:tid 15520] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:10:01.413415 2017] [proxy:error] [pid 5032:tid 16100] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:10:05.438222 2017] [proxy:error] [pid 5032:tid 15148] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:10:07.669026 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:10:41.287085 2017] [proxy:error] [pid 5032:tid 16352] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:10:41.287085 2017] [proxy:error] [pid 5032:tid 16352] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:10:41.287085 2017] [proxy_http:error] [pid 5032:tid 16352] [client 201.245.192.253:26086] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Thu Mar 02 12:11:30.115171 2017] [proxy:error] [pid 5032:tid 15308] AH00940: HTTP: disabled connection for (172.22.1.31) [Thu Mar 02 12:12:22.905664 2017] [proxy:error] [pid 5032: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.26:8080 (172.22.1.26) failed [Thu Mar 02 12:12:22.905664 2017] [proxy:error] [pid 5032:tid 16328] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:12:22.905664 2017] [proxy_http:error] [pid 5032:tid 16328] [client 181.142.133.228:49458] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:12:26.821271 2017] [proxy:error] [pid 5032:tid 16176] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:12:26.821271 2017] [proxy:error] [pid 5032:tid 16176] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:12:26.821271 2017] [proxy_http:error] [pid 5032:tid 16176] [client 152.204.131.54:51739] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:16:19.339679 2017] [proxy:error] [pid 5032:tid 16412] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 12:16:19.339679 2017] [proxy:error] [pid 5032:tid 16412] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:16:19.339679 2017] [proxy_http:error] [pid 5032:tid 16412] [client 181.142.133.228:49673] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:17:47.682634 2017] [proxy:error] [pid 5032: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.26:8080 (172.22.1.26) failed [Thu Mar 02 12:17:47.682634 2017] [proxy:error] [pid 5032:tid 15308] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:17:47.682634 2017] [proxy_http:error] [pid 5032:tid 15308] [client 181.142.133.228:50120] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:18:30.301909 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:18:30.301909 2017] [proxy:error] [pid 5032:tid 16388] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:18:30.301909 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:15629] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Thu Mar 02 12:18:36.198719 2017] [proxy:error] [pid 5032:tid 15400] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:18:36.198719 2017] [proxy:error] [pid 5032:tid 15400] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Thu Mar 02 12:18:36.198719 2017] [proxy_http:error] [pid 5032:tid 15400] [client 201.245.192.253:25695] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:18:36.323520 2017] [proxy:error] [pid 5032: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.31:80 (172.22.1.31) failed [Thu Mar 02 12:18:36.323520 2017] [proxy_http:error] [pid 5032:tid 16328] [client 201.245.192.253:25701] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:18:38.367123 2017] [proxy:error] [pid 5032:tid 15888] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:18:38.367123 2017] [proxy_http:error] [pid 5032:tid 15888] [client 201.245.192.253:25702] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:18:42.485530 2017] [proxy:error] [pid 5032:tid 15200] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:18:42.485530 2017] [proxy_http:error] [pid 5032:tid 15200] [client 201.245.192.253:25778] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:18:42.501130 2017] [proxy:error] [pid 5032:tid 16420] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Thu Mar 02 12:18:42.501130 2017] [proxy_http:error] [pid 5032:tid 16420] [client 201.245.192.253:25865] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 12:18:50.971945 2017] [proxy:error] [pid 5032:tid 15168] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:18:50.987545 2017] [proxy:error] [pid 5032:tid 15364] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:19:11.220781 2017] [proxy:error] [pid 5032:tid 16312] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:19:25.338806 2017] [proxy:error] [pid 5032:tid 16312] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:20:46.224948 2017] [proxy:error] [pid 5032:tid 16212] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 12:20:46.224948 2017] [proxy:error] [pid 5032:tid 16212] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:20:46.224948 2017] [proxy_http:error] [pid 5032:tid 16212] [client 181.142.133.228:50197] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:22:33.475136 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:22:33.475136 2017] [proxy:error] [pid 5032:tid 16388] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:22:33.475136 2017] [proxy_http:error] [pid 5032:tid 16388] [client 201.245.192.253:22352] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Thu Mar 02 12:22:33.475136 2017] [proxy:error] [pid 5032:tid 15848] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:22:33.475136 2017] [proxy_http:error] [pid 5032:tid 15848] [client 201.245.192.253:22351] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse [Thu Mar 02 12:25:59.598298 2017] [proxy:error] [pid 5032:tid 15584] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Thu Mar 02 12:25:59.598298 2017] [proxy:error] [pid 5032:tid 15584] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Thu Mar 02 12:25:59.598298 2017] [proxy_http:error] [pid 5032:tid 15584] [client 201.245.192.253:14802] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarHistorialSolProceso.xhtml [Thu Mar 02 12:25:59.676298 2017] [proxy:error] [pid 5032:tid 15584] AH00940: HTTP: disabled connection for (172.22.1.61) [Thu Mar 02 12:29:39.199884 2017] [proxy:error] [pid 5032: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.43:7778 (172.22.1.43) failed [Thu Mar 02 12:29:39.199884 2017] [proxy:error] [pid 5032:tid 15252] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.43) for 60s [Thu Mar 02 12:29:39.199884 2017] [proxy_http:error] [pid 5032:tid 15252] [client 190.25.157.12:61902] AH01114: HTTP: failed to make connection to backend: 172.22.1.43 [Thu Mar 02 12:30:33.519179 2017] [proxy:error] [pid 5032:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 12:30:33.519179 2017] [proxy:error] [pid 5032:tid 16388] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:30:33.519179 2017] [proxy_http:error] [pid 5032:tid 16388] [client 190.25.100.159:25907] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 12:50:45.500908 2017] [proxy:error] [pid 5032:tid 15624] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 12:50:45.500908 2017] [proxy:error] [pid 5032:tid 15624] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 12:50:45.500908 2017] [proxy_http:error] [pid 5032:tid 15624] [client 181.142.133.228:50349] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Thu Mar 02 13:06:48.771400 2017] [proxy:error] [pid 5032: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 [Thu Mar 02 13:06:48.771400 2017] [proxy:error] [pid 5032:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Mar 02 13:06:48.771400 2017] [proxy_http:error] [pid 5032:tid 16372] [client 152.61.128.50:36670] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Mar 02 13:06:48.974200 2017] [proxy:error] [pid 5032:tid 16032] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Mar 02 13:06:49.192601 2017] [proxy:error] [pid 5032:tid 16032] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Mar 02 13:17:33.036931 2017] [core:error] [pid 5032:tid 16456] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:23642] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 13:17:43.332950 2017] [core:error] [pid 5032:tid 16456] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:23642] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 13:17:44.144151 2017] [core:error] [pid 5032:tid 15740] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:24067] AH00127: Cannot map HEAD /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 13:17:54.455769 2017] [core:error] [pid 5032:tid 15740] (20024)The given path is misformatted or contained invalid characters: [client 116.24.103.159:24067] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file [Thu Mar 02 13:24:19.308445 2017] [proxy_http:error] [pid 5032:tid 15212] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:16727] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=SucursalSeleccion.asp&CargaPagina=ModuloProcesos&IdModulo=3 [Thu Mar 02 13:24:28.169261 2017] [proxy_http:error] [pid 5032:tid 15732] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:16534] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=SucursalSeleccion.asp&CargaPagina=ModuloProcesos&IdModulo=3 [Thu Mar 02 13:37:55.470679 2017] [proxy_http:error] [pid 5032:tid 15348] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : [client 201.245.192.253:28617] AH01110: error reading response, referer: http://190.27.245.106/sipse/faces/presentacion/financiero/estudioPrevio/personalSolicitado/personalSolicitadoSolicitudProceso.xhtml [Thu Mar 02 13:38:32.473944 2017] [proxy_http:error] [pid 5032:tid 16168] (OS 10053)An established connection was aborted by the software in your host machine. : [client 181.142.209.119:64936] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Thu Mar 02 13:38:32.473944 2017] [proxy:error] [pid 5032:tid 16168] [client 181.142.209.119:64936] AH00898: Error reading from remote server returned by /isolucionsda/, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Thu Mar 02 13:57:10.028706 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 14:32:03.115583 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 14:39:59.400019 2017] [proxy_http:error] [pid 5032:tid 15252] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:32847] 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& [Thu Mar 02 14:39:59.400019 2017] [proxy:error] [pid 5032:tid 15252] [client 201.245.192.253:32847] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Mar 02 14:41:51.689017 2017] [proxy_http:error] [pid 5032:tid 16160] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:23324] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Mar 02 14:45:15.253774 2017] [proxy_http:error] [pid 5032:tid 15832] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:10711] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=FiltroNoConformidades.asp&Estado=Abiertas&PintarAuditorias=SI&EsAbierta=1&ConMenu=NO [Thu Mar 02 14:52:54.846181 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 14:52:54.846181 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 14:52:54.846181 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 15:42:19.490988 2017] [core:error] [pid 5032:tid 16412] (20024)The given path is misformatted or contained invalid characters: [client 69.58.178.57:49092] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Thu Mar 02 16:37:51.313640 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 16:46:50.559788 2017] [cgi:error] [pid 5032:tid 15356] [client 179.158.52.22:59511] script not found or unable to stat: E:/nuevo/htdocs/hndUnblock.cgi [Thu Mar 02 16:46:50.949788 2017] [cgi:error] [pid 5032:tid 15356] [client 179.158.52.22:59514] script not found or unable to stat: E:/nuevo/htdocs/tmUnblock.cgi [Thu Mar 02 16:55:23.660289 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 18:17:44.641367 2017] [proxy_http:error] [pid 5032:tid 15740] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:17907] 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 [Thu Mar 02 18:17:44.641367 2017] [proxy:error] [pid 5032:tid 15740] [client 201.245.192.253:17907] 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 [Thu Mar 02 18:17:44.656967 2017] [proxy_http:error] [pid 5032:tid 16096] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:17908] 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 [Thu Mar 02 18:17:44.656967 2017] [proxy:error] [pid 5032:tid 16096] [client 201.245.192.253:17908] 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 [Thu Mar 02 20:14:23.094459 2017] [core:error] [pid 5032:tid 15664] (20024)The given path is misformatted or contained invalid characters: [client 181.63.89.234:57389] AH00127: Cannot map HEAD /https://www.dama.gov.co/ HTTP/1.1 to file [Thu Mar 02 20:30:49.172191 2017] [access_compat:error] [pid 5032:tid 15436] [client 191.96.249.97:33903] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/scripts [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.559972 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 20:51:30.575572 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 02 21:36:04.779069 2017] [proxy:error] [pid 5032:tid 16252] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 21:36:04.779069 2017] [proxy:error] [pid 5032:tid 16252] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Thu Mar 02 21:36:04.779069 2017] [proxy_http:error] [pid 5032:tid 16252] [client 181.128.204.95:1985] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1829284&ext=html&codfile=-1&iscodfile=false&nombre=Reportes%20de%20Consumo%20para%20Concesiones%20de%20%20Agua%20en%20el%20DC%20.html [Thu Mar 02 21:36:04.779069 2017] [proxy:error] [pid 5032:tid 16264] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 21:36:04.779069 2017] [proxy_http:error] [pid 5032:tid 16264] [client 181.128.204.95:1981] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1829284&ext=html&codfile=-1&iscodfile=false&nombre=Reportes%20de%20Consumo%20para%20Concesiones%20de%20%20Agua%20en%20el%20DC%20.html [Thu Mar 02 21:36:04.779069 2017] [proxy:error] [pid 5032:tid 16012] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 21:36:04.779069 2017] [proxy_http:error] [pid 5032:tid 16012] [client 181.128.204.95:1983] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1829284&ext=html&codfile=-1&iscodfile=false&nombre=Reportes%20de%20Consumo%20para%20Concesiones%20de%20%20Agua%20en%20el%20DC%20.html [Thu Mar 02 21:36:04.794669 2017] [proxy:error] [pid 5032:tid 15772] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 21:36:04.794669 2017] [proxy_http:error] [pid 5032:tid 15772] [client 181.128.204.95:60118] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1829284&ext=html&codfile=-1&iscodfile=false&nombre=Reportes%20de%20Consumo%20para%20Concesiones%20de%20%20Agua%20en%20el%20DC%20.html [Thu Mar 02 21:36:04.794669 2017] [proxy:error] [pid 5032:tid 15848] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Thu Mar 02 21:36:04.794669 2017] [proxy_http:error] [pid 5032:tid 15848] [client 181.128.204.95:60116] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1829284&ext=html&codfile=-1&iscodfile=false&nombre=Reportes%20de%20Consumo%20para%20Concesiones%20de%20%20Agua%20en%20el%20DC%20.html [Thu Mar 02 22:07:17.827559 2017] [mpm_winnt:warn] [pid 5032:tid 17792] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0312 ]-- |