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 Apr 07 00:01:23.047020 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 00:14:20.255985 2016] [proxy:error] [pid 4748:tid 15676] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 00:14:20.255985 2016] [proxy:error] [pid 4748:tid 15676] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 00:14:20.255985 2016] [proxy_http:error] [pid 4748:tid 15676] [client 152.61.128.66:33986] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 00:14:20.474385 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:14:20.692786 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:14:20.926786 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:14:21.145186 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:14:21.379187 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:21:36.073950 2016] [proxy:error] [pid 4748:tid 14800] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 00:21:36.073950 2016] [proxy:error] [pid 4748:tid 14800] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 00:21:36.073950 2016] [proxy_http:error] [pid 4748:tid 14800] [client 152.61.128.66:60948] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 00:21:36.307951 2016] [proxy:error] [pid 4748:tid 14800] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:21:36.541951 2016] [proxy:error] [pid 4748:tid 14800] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:21:36.775952 2016] [proxy:error] [pid 4748:tid 14800] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:21:37.009952 2016] [proxy:error] [pid 4748:tid 14800] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 00:40:28.808540 2016] [proxy:error] [pid 4748:tid 15820] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 00:40:28.808540 2016] [proxy:error] [pid 4748:tid 15820] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 00:40:28.808540 2016] [proxy_http:error] [pid 4748:tid 15820] [client 152.61.192.232:64101] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 00:40:29.026940 2016] [proxy:error] [pid 4748:tid 15820] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 01:03:12.484935 2016] [proxy:error] [pid 4748:tid 15384] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 01:03:12.484935 2016] [proxy:error] [pid 4748:tid 15384] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 01:03:12.484935 2016] [proxy_http:error] [pid 4748:tid 15384] [client 152.61.192.232:13512] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 01:03:12.718935 2016] [proxy:error] [pid 4748:tid 15384] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 01:03:12.952936 2016] [proxy:error] [pid 4748:tid 15384] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 05:10:32.296800 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 05:10:32.296800 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 06:32:16.369214 2016] [proxy:error] [pid 4748:tid 14752] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 06:32:16.369214 2016] [proxy:error] [pid 4748:tid 14752] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 06:32:16.369214 2016] [proxy_http:error] [pid 4748:tid 14752] [client 152.61.192.232:52899] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 06:32:16.587614 2016] [proxy:error] [pid 4748:tid 14752] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 06:57:27.045667 2016] [proxy:error] [pid 4748:tid 14848] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 06:57:27.045667 2016] [proxy:error] [pid 4748:tid 14848] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 06:57:27.045667 2016] [proxy_http:error] [pid 4748:tid 14848] [client 152.61.192.232:2442] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 06:57:27.279668 2016] [proxy:error] [pid 4748:tid 14848] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 06:57:27.529268 2016] [proxy:error] [pid 4748:tid 14848] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 08:47:39.868082 2016] [proxy_http:error] [pid 4748:tid 14976] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:30243] AH01102: error reading status line from remote server 172.22.1.31:80 [Thu Apr 07 08:47:39.868082 2016] [proxy:error] [pid 4748:tid 14976] [client 201.245.192.253:30243] AH00898: Error reading from remote server returned by /isolucionsda/ [Thu Apr 07 08:56:51.141850 2016] [proxy_http:error] [pid 4748:tid 14816] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:33666] 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 Apr 07 08:56:51.141850 2016] [proxy:error] [pid 4748:tid 14816] [client 201.245.192.253:33666] AH00898: Error reading from remote server returned by /isolucionsda/g/Img_LogoIsoCabezote.jpg, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Thu Apr 07 08:57:44.041543 2016] [proxy_http:error] [pid 4748:tid 15396] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:33867] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/Administracion/SalaEdicion/Articulo.asp?Id_Articulo=9764 [Thu Apr 07 09:12:08.376661 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 09:59:56.661099 2016] [proxy_http:error] [pid 4748:tid 15272] (20014)Internal error: [client 201.245.192.253:46473] AH01102: error reading status line from remote server 192.168.175.30:80, referer: http://190.27.245.106/catalogoisis/index.php [Thu Apr 07 10:10:53.266253 2016] [proxy_http:error] [pid 4748:tid 15820] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:41237] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/bancoconocimiento/m/mapadeprocesos__v4/mapadeprocesos__v4.asp [Thu Apr 07 10:10:53.281853 2016] [proxy_http:error] [pid 4748:tid 15200] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:41235] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/bancoconocimiento/m/mapadeprocesos__v4/mapadeprocesos__v4.asp [Thu Apr 07 10:40:11.031540 2016] [proxy:error] [pid 4748:tid 15216] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 10:40:11.031540 2016] [proxy:error] [pid 4748:tid 15216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 10:40:11.031540 2016] [proxy_http:error] [pid 4748:tid 15216] [client 152.61.192.232:56325] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 10:40:11.265540 2016] [proxy:error] [pid 4748:tid 15216] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:40:11.515141 2016] [proxy:error] [pid 4748:tid 14892] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:40:11.749141 2016] [proxy:error] [pid 4748:tid 14892] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:40:11.998742 2016] [proxy:error] [pid 4748:tid 14892] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:46:39.331822 2016] [proxy_http:error] [pid 4748:tid 15904] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:45754] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Administracion/SalaEdicion/MagazinArticuloPublicar.asp [Thu Apr 07 10:50:14.986601 2016] [proxy_http:error] [pid 4748:tid 15600] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:36488] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp?Id_Articulo=9769 [Thu Apr 07 10:59:01.877526 2016] [proxy:error] [pid 4748: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.51:8399 (172.22.1.51) failed [Thu Apr 07 10:59:01.877526 2016] [proxy:error] [pid 4748:tid 15888] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 10:59:01.877526 2016] [proxy_http:error] [pid 4748:tid 15888] [client 152.61.192.232:64606] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 10:59:02.173927 2016] [proxy:error] [pid 4748:tid 15888] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:59:02.485927 2016] [proxy:error] [pid 4748:tid 15888] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:59:09.724340 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:59:10.005140 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 10:59:10.317141 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 11:40:26.931691 2016] [proxy_http:error] [pid 4748:tid 15764] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:33491] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/ISOlucionSDA/Administracion/SalaEdicion/Articulo.asp?Id_Articulo=9776 [Thu Apr 07 11:53:15.825841 2016] [access_compat:error] [pid 4748:tid 14912] [client 200.32.82.4:65140] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/ [Thu Apr 07 12:29:59.393112 2016] [proxy:error] [pid 4748:tid 15144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 12:29:59.393112 2016] [proxy:error] [pid 4748:tid 15144] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 12:29:59.393112 2016] [proxy_http:error] [pid 4748:tid 15144] [client 152.61.128.66:51392] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Thu Apr 07 12:29:59.611512 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:29:59.829913 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:30:00.063913 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:30:00.282313 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:30:00.516314 2016] [proxy:error] [pid 4748:tid 15144] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:33:35.094691 2016] [proxy:error] [pid 4748:tid 14928] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 12:33:35.094691 2016] [proxy:error] [pid 4748:tid 14928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 12:33:35.094691 2016] [proxy_http:error] [pid 4748:tid 14928] [client 186.155.211.115:54982] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://www.ideca.gov.co/es/servicios/directorio-de-servicios [Thu Apr 07 12:33:48.401514 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:33:48.666715 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:33:48.900715 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:33:49.119115 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 12:33:49.353116 2016] [proxy:error] [pid 4748:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 13:46:11.730943 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 13:50:09.538761 2016] [proxy_http:error] [pid 4748:tid 15228] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:22860] 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 Apr 07 13:50:09.538761 2016] [proxy:error] [pid 4748:tid 15228] [client 201.245.192.253:22860] AH00898: Error reading from remote server returned by /IsolucionSDA/BarraTitulos.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina1=FrameSetGeneral.asp& [Thu Apr 07 14:25:45.151312 2016] [proxy_http:error] [pid 4748:tid 14904] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:41985] 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 Apr 07 14:25:45.151312 2016] [proxy:error] [pid 4748:tid 14904] [client 201.245.192.253:41985] AH00898: Error reading from remote server returned by /isolucionsda/g/Bot_TalentoOff_ESP.jpg, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Apr 07 14:39:18.864341 2016] [proxy:error] [pid 4748:tid 14976] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:18.864341 2016] [proxy:error] [pid 4748:tid 14976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:39:18.864341 2016] [proxy_http:error] [pid 4748:tid 14976] [client 172.22.2.1:11714] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:18.864341 2016] [proxy:error] [pid 4748:tid 14716] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:39:18.864341 2016] [proxy_http:error] [pid 4748:tid 14716] [client 172.22.2.1:11715] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:18.879941 2016] [proxy:error] [pid 4748:tid 15320] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:18.879941 2016] [proxy_http:error] [pid 4748:tid 15320] [client 172.22.2.1:11717] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:18.895541 2016] [proxy:error] [pid 4748:tid 15524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:18.895541 2016] [proxy_http:error] [pid 4748:tid 15524] [client 172.22.2.1:11716] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:18.895541 2016] [proxy:error] [pid 4748:tid 14772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:18.895541 2016] [proxy_http:error] [pid 4748:tid 14772] [client 172.22.2.1:11719] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:18.895541 2016] [proxy:error] [pid 4748:tid 14744] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:18.895541 2016] [proxy_http:error] [pid 4748:tid 14744] [client 172.22.2.1:11718] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.908778 2016] [proxy:error] [pid 4748:tid 14716] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:39:39.908778 2016] [proxy:error] [pid 4748:tid 14716] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:39:39.908778 2016] [proxy_http:error] [pid 4748:tid 14716] [client 172.22.2.1:11721] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.924378 2016] [proxy:error] [pid 4748:tid 14976] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:39.924378 2016] [proxy_http:error] [pid 4748:tid 14976] [client 172.22.2.1:11720] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.924378 2016] [proxy:error] [pid 4748:tid 15320] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:39.924378 2016] [proxy_http:error] [pid 4748:tid 15320] [client 172.22.2.1:11722] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.955578 2016] [proxy:error] [pid 4748:tid 15524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:39.955578 2016] [proxy_http:error] [pid 4748:tid 15524] [client 172.22.2.1:11723] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.955578 2016] [proxy:error] [pid 4748:tid 14744] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:39.955578 2016] [proxy_http:error] [pid 4748:tid 14744] [client 172.22.2.1:11724] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:39:39.955578 2016] [proxy:error] [pid 4748:tid 14772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:39:39.955578 2016] [proxy_http:error] [pid 4748:tid 14772] [client 172.22.2.1:11725] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/en/;jsessionid=3C01E738691B68DCD6124BCAFAA54013 [Thu Apr 07 14:40:01.702016 2016] [proxy:error] [pid 4748:tid 15524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:01.702016 2016] [proxy:error] [pid 4748:tid 15524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:40:01.702016 2016] [proxy_http:error] [pid 4748:tid 15524] [client 201.245.192.253:17259] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:01.717616 2016] [proxy:error] [pid 4748:tid 14744] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:01.717616 2016] [proxy_http:error] [pid 4748:tid 14744] [client 201.245.192.253:17260] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:01.717616 2016] [proxy:error] [pid 4748:tid 14772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:01.717616 2016] [proxy_http:error] [pid 4748:tid 14772] [client 201.245.192.253:17261] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:01.826816 2016] [proxy:error] [pid 4748:tid 15340] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:01.826816 2016] [proxy_http:error] [pid 4748:tid 15340] [client 201.245.192.253:17258] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:02.591218 2016] [proxy:error] [pid 4748:tid 14976] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:02.591218 2016] [proxy:error] [pid 4748:tid 14976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:40:02.591218 2016] [proxy_http:error] [pid 4748:tid 14976] [client 201.245.192.253:17278] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:02.606818 2016] [proxy:error] [pid 4748:tid 14976] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 14:40:02.622418 2016] [proxy:error] [pid 4748:tid 14976] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 14:40:02.669218 2016] [proxy:error] [pid 4748:tid 14716] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:02.669218 2016] [proxy_http:error] [pid 4748:tid 14716] [client 201.245.192.253:17279] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:23.557654 2016] [proxy:error] [pid 4748:tid 15340] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:23.557654 2016] [proxy:error] [pid 4748:tid 15340] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:40:23.557654 2016] [proxy_http:error] [pid 4748:tid 15340] [client 201.245.192.253:17383] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:23.557654 2016] [proxy:error] [pid 4748:tid 14744] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:23.557654 2016] [proxy_http:error] [pid 4748:tid 14744] [client 201.245.192.253:17384] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:23.557654 2016] [proxy:error] [pid 4748:tid 15524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:23.557654 2016] [proxy_http:error] [pid 4748:tid 15524] [client 201.245.192.253:17381] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:23.573254 2016] [proxy:error] [pid 4748:tid 14772] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:23.573254 2016] [proxy_http:error] [pid 4748:tid 14772] [client 201.245.192.253:17382] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:25.679258 2016] [proxy:error] [pid 4748:tid 15492] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:25.679258 2016] [proxy_http:error] [pid 4748:tid 15492] [client 201.245.192.253:17398] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:25.694858 2016] [proxy:error] [pid 4748:tid 15820] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:25.694858 2016] [proxy_http:error] [pid 4748:tid 15820] [client 201.245.192.253:17400] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:25.710458 2016] [proxy:error] [pid 4748:tid 14840] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:25.710458 2016] [proxy_http:error] [pid 4748:tid 14840] [client 201.245.192.253:17397] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:25.710458 2016] [proxy:error] [pid 4748:tid 14792] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:25.710458 2016] [proxy_http:error] [pid 4748:tid 14792] [client 201.245.192.253:17399] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.350059 2016] [proxy:error] [pid 4748:tid 14944] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:26.350059 2016] [proxy_http:error] [pid 4748:tid 14944] [client 201.245.192.253:17401] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.350059 2016] [proxy:error] [pid 4748:tid 14912] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:26.350059 2016] [proxy_http:error] [pid 4748:tid 14912] [client 201.245.192.253:17402] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.786860 2016] [proxy:error] [pid 4748:tid 15780] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:26.786860 2016] [proxy_http:error] [pid 4748:tid 15780] [client 201.245.192.253:17407] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.786860 2016] [proxy:error] [pid 4748: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.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:26.786860 2016] [proxy_http:error] [pid 4748:tid 15888] [client 201.245.192.253:17405] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.786860 2016] [proxy:error] [pid 4748:tid 15312] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:26.786860 2016] [proxy_http:error] [pid 4748:tid 15312] [client 201.245.192.253:17404] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:26.802460 2016] [proxy:error] [pid 4748:tid 15988] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:26.802460 2016] [proxy_http:error] [pid 4748:tid 15988] [client 201.245.192.253:17406] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:27.176861 2016] [proxy:error] [pid 4748:tid 15516] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:27.176861 2016] [proxy_http:error] [pid 4748:tid 15516] [client 201.245.192.253:17409] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:27.286061 2016] [proxy:error] [pid 4748:tid 15732] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:27.286061 2016] [proxy_http:error] [pid 4748:tid 15732] [client 201.245.192.253:17410] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:28.378063 2016] [proxy:error] [pid 4748:tid 15328] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:28.378063 2016] [proxy_http:error] [pid 4748:tid 15328] [client 201.245.192.253:17414] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:28.409263 2016] [proxy:error] [pid 4748:tid 15600] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:28.409263 2016] [proxy_http:error] [pid 4748:tid 15600] [client 201.245.192.253:17417] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:28.409263 2016] [proxy:error] [pid 4748:tid 14816] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:28.409263 2016] [proxy_http:error] [pid 4748:tid 14816] [client 201.245.192.253:17415] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:28.409263 2016] [proxy:error] [pid 4748:tid 15684] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:28.409263 2016] [proxy_http:error] [pid 4748:tid 15684] [client 201.245.192.253:17416] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:29.688465 2016] [proxy:error] [pid 4748:tid 14856] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:29.688465 2016] [proxy_http:error] [pid 4748:tid 14856] [client 201.245.192.253:17421] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:29.828865 2016] [proxy:error] [pid 4748:tid 15764] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:29.828865 2016] [proxy_http:error] [pid 4748:tid 15764] [client 201.245.192.253:17423] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:30.983267 2016] [proxy:error] [pid 4748:tid 15588] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:30.983267 2016] [proxy_http:error] [pid 4748:tid 15588] [client 201.245.192.253:17431] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:30.983267 2016] [proxy:error] [pid 4748: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.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:30.983267 2016] [proxy_http:error] [pid 4748:tid 15612] [client 201.245.192.253:17430] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:30.998868 2016] [proxy:error] [pid 4748:tid 15900] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:30.998868 2016] [proxy_http:error] [pid 4748:tid 15900] [client 201.245.192.253:17429] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:30.998868 2016] [proxy:error] [pid 4748:tid 15380] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:30.998868 2016] [proxy_http:error] [pid 4748:tid 15380] [client 201.245.192.253:17432] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.373268 2016] [proxy:error] [pid 4748:tid 15840] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:31.373268 2016] [proxy_http:error] [pid 4748:tid 15840] [client 201.245.192.253:17437] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.482468 2016] [proxy:error] [pid 4748:tid 15272] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:31.482468 2016] [proxy_http:error] [pid 4748:tid 15272] [client 201.245.192.253:17438] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.966069 2016] [proxy:error] [pid 4748:tid 14800] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:31.966069 2016] [proxy_http:error] [pid 4748:tid 14800] [client 201.245.192.253:17443] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.966069 2016] [proxy:error] [pid 4748: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.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:31.966069 2016] [proxy_http:error] [pid 4748:tid 15468] [client 201.245.192.253:17445] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.997269 2016] [proxy:error] [pid 4748:tid 14784] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:31.997269 2016] [proxy_http:error] [pid 4748:tid 14784] [client 201.245.192.253:17444] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:31.997269 2016] [proxy:error] [pid 4748:tid 15192] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:31.997269 2016] [proxy_http:error] [pid 4748:tid 15192] [client 201.245.192.253:17442] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:32.028469 2016] [proxy:error] [pid 4748:tid 15144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:32.028469 2016] [proxy_http:error] [pid 4748:tid 15144] [client 201.245.192.253:17446] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:32.168870 2016] [proxy:error] [pid 4748:tid 15724] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:32.168870 2016] [proxy_http:error] [pid 4748:tid 15724] [client 201.245.192.253:17447] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.276472 2016] [proxy:error] [pid 4748:tid 15852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:33.276472 2016] [proxy_http:error] [pid 4748:tid 15852] [client 201.245.192.253:17452] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.276472 2016] [proxy:error] [pid 4748:tid 14752] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:33.276472 2016] [proxy_http:error] [pid 4748:tid 14752] [client 201.245.192.253:17450] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.307672 2016] [proxy:error] [pid 4748:tid 15676] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:33.307672 2016] [proxy_http:error] [pid 4748:tid 15676] [client 201.245.192.253:17453] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.307672 2016] [proxy:error] [pid 4748:tid 15904] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:33.307672 2016] [proxy_http:error] [pid 4748:tid 15904] [client 201.245.192.253:17451] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.728872 2016] [proxy:error] [pid 4748:tid 15104] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:33.728872 2016] [proxy:error] [pid 4748:tid 15104] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:40:33.728872 2016] [proxy_http:error] [pid 4748:tid 15104] [client 201.245.192.253:17454] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:33.791272 2016] [proxy:error] [pid 4748:tid 15104] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 14:40:33.822472 2016] [proxy:error] [pid 4748:tid 15104] AH00940: HTTP: disabled connection for (172.22.1.51) [Thu Apr 07 14:40:33.838072 2016] [proxy:error] [pid 4748:tid 14808] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:33.838072 2016] [proxy_http:error] [pid 4748:tid 14808] [client 201.245.192.253:17455] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:54.352109 2016] [proxy:error] [pid 4748:tid 14752] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:54.352109 2016] [proxy_http:error] [pid 4748:tid 14752] [client 201.245.192.253:17540] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:54.367709 2016] [proxy:error] [pid 4748:tid 15852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:54.367709 2016] [proxy_http:error] [pid 4748:tid 15852] [client 201.245.192.253:17541] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:54.367709 2016] [proxy:error] [pid 4748: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.51:8399 (172.22.1.51) failed [Thu Apr 07 14:40:54.367709 2016] [proxy_http:error] [pid 4748:tid 15468] [client 201.245.192.253:17543] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:40:54.398909 2016] [proxy:error] [pid 4748:tid 15904] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:40:54.398909 2016] [proxy_http:error] [pid 4748:tid 15904] [client 201.245.192.253:17542] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.229884 2016] [proxy:error] [pid 4748:tid 14912] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.229884 2016] [proxy:error] [pid 4748:tid 14912] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Thu Apr 07 14:55:51.229884 2016] [proxy_http:error] [pid 4748:tid 14912] [client 201.245.192.253:10859] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.307884 2016] [proxy:error] [pid 4748:tid 15516] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.307884 2016] [proxy_http:error] [pid 4748:tid 15516] [client 201.245.192.253:10862] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.354684 2016] [proxy:error] [pid 4748:tid 15676] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.354684 2016] [proxy_http:error] [pid 4748:tid 15676] [client 201.245.192.253:10861] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.354684 2016] [proxy:error] [pid 4748:tid 15780] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.354684 2016] [proxy_http:error] [pid 4748:tid 15780] [client 201.245.192.253:10860] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.744685 2016] [proxy:error] [pid 4748:tid 15852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.744685 2016] [proxy_http:error] [pid 4748:tid 15852] [client 201.245.192.253:10866] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 14:55:51.807085 2016] [proxy:error] [pid 4748:tid 15272] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection 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 Apr 07 14:55:51.807085 2016] [proxy_http:error] [pid 4748:tid 15272] [client 201.245.192.253:10867] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://172.22.1.60/ [Thu Apr 07 15:09:17.782500 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 15:24:39.993720 2016] [proxy_http:error] [pid 4748:tid 15724] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:56033] 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 Apr 07 15:24:40.009320 2016] [proxy_http:error] [pid 4748:tid 15032] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:56227] 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 Apr 07 15:24:40.009320 2016] [proxy:error] [pid 4748:tid 15032] [client 201.245.192.253:56227] AH00898: Error reading from remote server returned by /isolucionsda/g/Bot_Administrador.jpg, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Apr 07 15:46:52.377461 2016] [proxy_http:error] [pid 4748:tid 14944] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:50316] 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=5 [Thu Apr 07 15:46:52.377461 2016] [proxy:error] [pid 4748:tid 14944] [client 201.245.192.253:50316] AH00898: Error reading from remote server returned by /isolucionsda/BarraFavoritos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=5 [Thu Apr 07 15:51:20.744732 2016] [proxy_http:error] [pid 4748:tid 14744] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:39330] 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 Apr 07 15:51:20.744732 2016] [proxy:error] [pid 4748:tid 14744] [client 201.245.192.253:39330] AH00898: Error reading from remote server returned by /isolucionsda/g/Img_DivBarraSup.jpg, referer: http://190.27.245.106/isolucionsda/IdentificaUsuario.asp?Pagina1=FrameSetGeneral.asp& [Thu Apr 07 15:52:03.223607 2016] [proxy_http:error] [pid 4748:tid 15684] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:39788] 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 Apr 07 15:52:03.223607 2016] [proxy:error] [pid 4748:tid 15684] [client 201.245.192.253:39788] AH00898: Error reading from remote server returned by /isolucionsda/g/Bot_Home.jpg, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina1=FrameSetGeneral.asp&&Pagina=MagazinHome.asp [Thu Apr 07 16:16:49.001416 2016] [proxy_http:error] [pid 4748:tid 15640] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:52729] 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 Apr 07 16:16:49.001416 2016] [proxy:error] [pid 4748:tid 15640] [client 201.245.192.253:52729] AH00898: Error reading from remote server returned by /IsolucionSDA/BarraTitulos.asp, referer: http://190.27.245.106/IsolucionSDA/FrameSetGeneral.asp?Pagina=SucursalSeleccion.asp&CargaPagina=ModuloProcesos&IdModulo=3 [Thu Apr 07 17:25:36.442066 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 17:25:36.442066 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 20:00:15.122963 2016] [core:error] [pid 4748:tid 14944] (20024)The given path is misformatted or contained invalid characters: [client 168.61.152.85:42668] AH00127: Cannot map GET /galeria/carrusel/Carrusel/jquery-ui-%0A%0A1.8.13.custom.min.js HTTP/1.1 to file [Thu Apr 07 20:45:58.045581 2016] [proxy_http:error] [pid 4748:tid 15964] (OS 10053)An established connection was aborted by the software in your host machine. : [client 186.85.53.114:63254] 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 Apr 07 20:45:58.045581 2016] [proxy:error] [pid 4748:tid 15964] [client 186.85.53.114:63254] AH00898: Error reading from remote server returned by /isolucionsda/BarraTitulos.asp, referer: http://190.27.245.106/isolucionsda/FrameSetGeneral.asp?Pagina=Menu.asp&IdModulo=4 [Thu Apr 07 21:08:47.213186 2016] [proxy_http:error] [pid 4748:tid 15600] (OS 10053)An established connection was aborted by the software in your host machine. : [client 181.130.82.141:63002] 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 Apr 07 21:14:01.663938 2016] [proxy_http:error] [pid 4748:tid 15676] (OS 10053)An established connection was aborted by the software in your host machine. : [client 181.130.82.141:63072] AH01102: error reading status line from remote server 172.22.1.31:80, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Apr 07 21:14:01.663938 2016] [proxy:error] [pid 4748:tid 15676] [client 181.130.82.141:63072] AH00898: Error reading from remote server returned by /isolucionsda/g/Bot_AmbientalOver_ESP.jpg, referer: http://190.27.245.106/isolucionsda/Encabezado.asp?Pagina=ListadoMaestroDocumentos3.asp [Thu Apr 07 21:47:04.942221 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 22:40:29.095249 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Thu Apr 07 22:40:29.095249 2016] [mpm_winnt:warn] [pid 4748:tid 16088] (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.1872 ]-- |