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: [Sun Mar 04 00:43:55.368433 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 00:44:26.368206 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 01:09:46.186135 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 01:13:13.469991 2018] [proxy:error] [pid 12904:tid 18064] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 01:13:13.469991 2018] [proxy:error] [pid 12904:tid 18064] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 01:13:13.469991 2018] [proxy_http:error] [pid 12904:tid 18064] [client 66.249.88.33:57366] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 01:13:18.668288 2018] [proxy:error] [pid 12904:tid 16244] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 01:13:18.668288 2018] [proxy_http:error] [pid 12904:tid 16244] [client 181.53.115.180:54122] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 02:09:57.167671 2018] [proxy:error] [pid 12904:tid 17268] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed [Sun Mar 04 02:09:57.167671 2018] [proxy:error] [pid 12904:tid 17268] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Sun Mar 04 02:09:57.167671 2018] [proxy_http:error] [pid 12904:tid 17268] [client 152.61.128.50:55836] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Sun Mar 04 02:09:57.404685 2018] [proxy:error] [pid 12904:tid 17268] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Mar 04 02:09:57.641698 2018] [proxy:error] [pid 12904:tid 17268] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Mar 04 02:20:46.910834 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 02:25:14.495139 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 02:25:45.495913 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 02:54:02.832995 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 02:54:33.832768 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 03:01:58.333192 2018] [proxy:error] [pid 12904: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.51:8399 (172.22.1.51) failed [Sun Mar 04 03:01:58.333192 2018] [proxy:error] [pid 12904:tid 16072] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Sun Mar 04 03:01:58.333192 2018] [proxy_http:error] [pid 12904:tid 16072] [client 152.61.192.232:55786] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Sun Mar 04 03:01:58.644209 2018] [proxy:error] [pid 12904:tid 16072] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Mar 04 03:01:58.889223 2018] [proxy:error] [pid 12904:tid 16072] AH00940: HTTP: disabled connection for (172.22.1.51) [Sun Mar 04 03:35:54.367646 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 03:36:25.368419 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 04:17:19.725801 2018] [proxy:error] [pid 12904:tid 17392] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 04:17:19.725801 2018] [proxy:error] [pid 12904:tid 17392] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 04:17:19.725801 2018] [proxy_http:error] [pid 12904:tid 17392] [client 66.249.64.139:49288] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 04:28:37.433563 2018] [proxy:error] [pid 12904:tid 18100] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 04:28:37.433563 2018] [proxy:error] [pid 12904:tid 18100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 04:28:37.433563 2018] [proxy_http:error] [pid 12904:tid 18100] [client 66.249.64.139:49099] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 05:02:46.874785 2018] [access_compat:error] [pid 12904:tid 18156] [client 46.183.219.132:55784] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpmyadmin4 [Sun Mar 04 05:02:59.652515 2018] [access_compat:error] [pid 12904:tid 16608] [client 46.183.219.132:42412] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin-2.11.11 [Sun Mar 04 05:19:18.293490 2018] [cgi:error] [pid 12904:tid 16404] [client 89.19.24.154:34400] script not found or unable to stat: E:/nuevo/cgi-bin/test-cgi [Sun Mar 04 05:55:13.967788 2018] [proxy:error] [pid 12904:tid 17932] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 05:55:13.967788 2018] [proxy:error] [pid 12904:tid 17932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 05:55:13.967788 2018] [proxy_http:error] [pid 12904:tid 17932] [client 66.249.64.139:59487] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 06:04:51.420816 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 06:09:32.426889 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 06:10:03.426662 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 06:25:20.618122 2018] [core:error] [pid 12904:tid 18300] [client 66.240.192.138:53090] AH00135: Invalid method in request quit [Sun Mar 04 06:37:28.506755 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 07:06:19.962789 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 07:33:53.327356 2018] [proxy:error] [pid 12904:tid 15952] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 07:33:53.327356 2018] [proxy:error] [pid 12904:tid 15952] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 07:33:53.327356 2018] [proxy_http:error] [pid 12904:tid 15952] [client 66.249.64.141:51506] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 07:58:44.633654 2018] [proxy:error] [pid 12904:tid 16948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 07:58:44.633654 2018] [proxy:error] [pid 12904:tid 16948] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 07:58:44.633654 2018] [proxy_http:error] [pid 12904:tid 16948] [client 66.249.64.141:50971] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 08:07:57.968303 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 08:08:28.968076 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 08:30:01.207988 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 09:05:01.669127 2018] [proxy:error] [pid 12904: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.61:8080 (172.22.1.61) failed [Sun Mar 04 09:05:01.669127 2018] [proxy:error] [pid 12904:tid 16012] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Sun Mar 04 09:05:01.669127 2018] [proxy_http:error] [pid 12904:tid 16012] [client 66.249.88.63:53520] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Sun Mar 04 09:05:01.904141 2018] [proxy:error] [pid 12904:tid 16012] AH00940: HTTP: disabled connection for (172.22.1.61) [Sun Mar 04 09:15:11.794024 2018] [core:error] [pid 12904:tid 17848] [client 184.154.74.66:37710] AH00135: Invalid method in request SSH-2.0-Go [Sun Mar 04 09:32:11.460346 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:00:16.833744 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:00:47.833517 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:03:09.829639 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:03:40.830412 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:05:21.731183 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed [Sun Mar 04 10:05:21.731183 2018] [proxy:error] [pid 12904:tid 16312] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 10:05:21.731183 2018] [proxy_http:error] [pid 12904:tid 16312] [client 186.179.100.184:31331] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 10:07:36.942917 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed [Sun Mar 04 10:07:36.942917 2018] [proxy:error] [pid 12904:tid 16312] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 10:07:36.942917 2018] [proxy_http:error] [pid 12904:tid 16312] [client 191.102.126.66:50060] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 10:31:57.033429 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:32:28.033202 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:47:34.422045 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 10:54:56.145310 2018] [proxy:error] [pid 12904:tid 17576] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Sun Mar 04 10:54:56.145310 2018] [proxy:error] [pid 12904:tid 17576] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Sun Mar 04 10:54:56.145310 2018] [proxy_http:error] [pid 12904:tid 17576] [client 66.249.88.62:62437] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://190.27.245.106/sipse/faces/faces/faces/faces/faces/faces/faces/faces/faces/autenticacion.xhtml [Sun Mar 04 10:54:56.391324 2018] [proxy:error] [pid 12904:tid 17576] AH00940: HTTP: disabled connection for (172.22.1.61) [Sun Mar 04 11:29:32.920094 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 11:30:03.919868 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 11:38:03.818316 2018] [proxy:error] [pid 12904:tid 18032] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 11:38:03.818316 2018] [proxy:error] [pid 12904:tid 18032] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 11:38:03.818316 2018] [proxy_http:error] [pid 12904:tid 18032] [client 181.53.236.57:51227] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 11:38:50.080962 2018] [proxy:error] [pid 12904:tid 16276] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 11:39:58.132855 2018] [proxy:error] [pid 12904:tid 15884] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 11:39:58.132855 2018] [proxy:error] [pid 12904:tid 15884] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 11:39:58.132855 2018] [proxy_http:error] [pid 12904:tid 15884] [client 181.53.236.57:51242] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 11:39:58.237861 2018] [core:error] [pid 12904:tid 16788] [client 89.248.167.131:53268] AH00135: Invalid method in request quit [Sun Mar 04 11:58:22.423016 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 11:58:53.422789 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 12:00:46.226241 2018] [core:error] [pid 12904:tid 17364] (20024)The given path is misformatted or contained invalid characters: [client 54.37.85.105:43066] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Sun Mar 04 13:24:43.925381 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 13:25:14.825149 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 13:48:56.756478 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 13:53:31.669203 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 13:54:02.669976 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 14:02:26.232778 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 14:02:57.232551 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 14:51:07.469863 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 14:51:38.469636 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 15:03:35.034621 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 15:04:06.034394 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 15:29:53.540907 2018] [proxy:error] [pid 12904:tid 17572] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 15:29:53.540907 2018] [proxy:error] [pid 12904:tid 17572] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:29:53.540907 2018] [proxy_http:error] [pid 12904:tid 17572] [client 190.157.165.228:64956] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:29:55.335009 2018] [proxy:error] [pid 12904:tid 15704] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:29:55.335009 2018] [proxy_http:error] [pid 12904:tid 15704] [client 190.157.165.228:64957] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:30:05.569595 2018] [proxy:error] [pid 12904:tid 17208] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:30:05.569595 2018] [proxy_http:error] [pid 12904:tid 17208] [client 190.157.165.228:64959] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:33:29.334249 2018] [proxy:error] [pid 12904:tid 17964] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:33:29.334249 2018] [proxy:error] [pid 12904:tid 17964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:33:29.334249 2018] [proxy_http:error] [pid 12904:tid 17964] [client 190.157.165.228:65014] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:39:56.169375 2018] [proxy:error] [pid 12904:tid 16276] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:39:56.169375 2018] [proxy:error] [pid 12904:tid 16276] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:39:56.169375 2018] [proxy_http:error] [pid 12904:tid 16276] [client 181.53.11.74:49699] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:40:08.969107 2018] [proxy:error] [pid 12904:tid 16276] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 15:40:39.630861 2018] [proxy:error] [pid 12904:tid 15652] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 15:41:21.141235 2018] [proxy:error] [pid 12904:tid 17964] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:41:21.141235 2018] [proxy:error] [pid 12904:tid 17964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:41:21.141235 2018] [proxy_http:error] [pid 12904:tid 17964] [client 181.53.11.74:49712] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:41:50.695926 2018] [proxy:error] [pid 12904:tid 18156] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 15:43:45.034465 2018] [proxy:error] [pid 12904:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 15:43:45.034465 2018] [proxy:error] [pid 12904:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:43:45.034465 2018] [proxy_http:error] [pid 12904:tid 17956] [client 181.53.11.74:61274] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 15:43:51.033809 2018] [proxy:error] [pid 12904:tid 15652] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:43:51.033809 2018] [proxy_http:error] [pid 12904:tid 15652] [client 181.53.11.74:49948] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:45:15.842659 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed [Sun Mar 04 15:45:15.842659 2018] [proxy:error] [pid 12904:tid 15684] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:45:15.842659 2018] [proxy_http:error] [pid 12904:tid 15684] [client 181.53.11.74:50910] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 15:46:13.316947 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 15:46:15.671081 2018] [proxy:error] [pid 12904:tid 15652] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 15:51:49.834194 2018] [proxy:error] [pid 12904:tid 15628] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:51:49.834194 2018] [proxy:error] [pid 12904:tid 15628] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:51:49.834194 2018] [proxy_http:error] [pid 12904:tid 15628] [client 181.53.11.74:55827] 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 [Sun Mar 04 15:56:46.135142 2018] [proxy:error] [pid 12904:tid 17600] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 15:56:46.135142 2018] [proxy:error] [pid 12904:tid 17600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 15:56:46.135142 2018] [proxy_http:error] [pid 12904:tid 17600] [client 190.157.165.228:65200] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:03:53.944611 2018] [proxy:error] [pid 12904:tid 17956] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 16:03:53.944611 2018] [proxy:error] [pid 12904:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:03:53.944611 2018] [proxy_http:error] [pid 12904:tid 17956] [client 186.85.72.204:63203] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:03:57.485814 2018] [proxy:error] [pid 12904:tid 17364] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:03:57.485814 2018] [proxy_http:error] [pid 12904:tid 17364] [client 186.85.72.204:63204] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:11:20.838172 2018] [proxy:error] [pid 12904:tid 16896] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 16:11:20.838172 2018] [proxy:error] [pid 12904:tid 16896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:11:20.838172 2018] [proxy_http:error] [pid 12904:tid 16896] [client 181.53.11.74:56099] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:13:54.246946 2018] [proxy:error] [pid 12904:tid 17856] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:13:54.246946 2018] [proxy:error] [pid 12904:tid 17856] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:13:54.246946 2018] [proxy_http:error] [pid 12904:tid 17856] [client 181.53.11.74:56222] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:17:01.716669 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 16:17:09.953140 2018] [core:error] [pid 12904:tid 17228] [client 71.6.146.185:54429] AH00135: Invalid method in request quit [Sun Mar 04 16:21:06.238655 2018] [proxy:error] [pid 12904:tid 17952] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:21:06.238655 2018] [proxy:error] [pid 12904:tid 17952] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:21:06.238655 2018] [proxy_http:error] [pid 12904:tid 17952] [client 181.53.11.74:56311] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:23:01.139227 2018] [proxy:error] [pid 12904:tid 17500] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Sun Mar 04 16:23:01.139227 2018] [proxy:error] [pid 12904:tid 17500] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Sun Mar 04 16:23:01.139227 2018] [proxy_http:error] [pid 12904:tid 17500] [client 181.53.11.74:56366] AH01114: HTTP: failed to make connection to backend: 172.22.1.61, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Sun Mar 04 16:23:12.138856 2018] [proxy:error] [pid 12904:tid 18100] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 16:23:12.138856 2018] [proxy:error] [pid 12904:tid 18100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:23:12.138856 2018] [proxy_http:error] [pid 12904:tid 18100] [client 181.53.11.74:56358] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:23:14.651000 2018] [proxy:error] [pid 12904:tid 17484] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 16:24:40.169891 2018] [proxy:error] [pid 12904: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 [Sun Mar 04 16:24:40.169891 2018] [proxy:error] [pid 12904:tid 16364] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:24:40.169891 2018] [proxy_http:error] [pid 12904:tid 16364] [client 181.53.11.74:56416] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:25:09.895591 2018] [proxy:error] [pid 12904:tid 17856] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 16:25:10.987654 2018] [proxy:error] [pid 12904:tid 17780] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 16:25:18.388077 2018] [proxy:error] [pid 12904:tid 17992] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 16:28:31.636130 2018] [proxy:error] [pid 12904:tid 17600] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:28:31.636130 2018] [proxy:error] [pid 12904:tid 17600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:28:31.636130 2018] [proxy_http:error] [pid 12904:tid 17600] [client 181.53.11.74:56487] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:35:56.270562 2018] [proxy:error] [pid 12904:tid 17992] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:35:56.270562 2018] [proxy:error] [pid 12904:tid 17992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:35:56.270562 2018] [proxy_http:error] [pid 12904:tid 17992] [client 181.53.11.74:56790] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:36:05.040064 2018] [proxy:error] [pid 12904:tid 16096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:36:05.040064 2018] [proxy_http:error] [pid 12904:tid 16096] [client 181.53.11.74:56791] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:38:47.170337 2018] [proxy:error] [pid 12904:tid 16096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:38:47.170337 2018] [proxy:error] [pid 12904:tid 16096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:38:47.170337 2018] [proxy_http:error] [pid 12904:tid 16096] [client 181.53.11.74:57162] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:44:58.235561 2018] [proxy:error] [pid 12904:tid 17496] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 16:44:58.235561 2018] [proxy:error] [pid 12904:tid 17496] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:44:58.235561 2018] [proxy_http:error] [pid 12904:tid 17496] [client 181.53.11.74:57682] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:45:55.492835 2018] [proxy:error] [pid 12904:tid 18008] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 16:52:01.438766 2018] [proxy:error] [pid 12904:tid 16672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:52:01.438766 2018] [proxy:error] [pid 12904:tid 16672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:52:01.438766 2018] [proxy_http:error] [pid 12904:tid 16672] [client 181.53.11.74:58068] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:52:02.165808 2018] [proxy:error] [pid 12904:tid 17940] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:52:02.165808 2018] [proxy_http:error] [pid 12904:tid 17940] [client 181.53.11.74:58069] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:56:31.266200 2018] [proxy:error] [pid 12904:tid 16672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:56:31.266200 2018] [proxy:error] [pid 12904:tid 16672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:56:31.266200 2018] [proxy_http:error] [pid 12904:tid 16672] [client 181.53.11.74:58103] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:58:03.038449 2018] [proxy:error] [pid 12904:tid 17780] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:58:03.038449 2018] [proxy:error] [pid 12904:tid 17780] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:58:03.038449 2018] [proxy_http:error] [pid 12904:tid 17780] [client 66.249.88.62:33771] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:58:08.065736 2018] [proxy:error] [pid 12904:tid 16056] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:58:08.065736 2018] [proxy_http:error] [pid 12904:tid 16056] [client 181.53.11.74:48754] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 16:58:57.147544 2018] [proxy:error] [pid 12904:tid 18016] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 16:58:57.147544 2018] [proxy:error] [pid 12904:tid 18016] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 16:58:57.147544 2018] [proxy_http:error] [pid 12904:tid 18016] [client 190.157.165.228:49718] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 18:00:09.271577 2018] [proxy:error] [pid 12904:tid 17120] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 18:00:09.271577 2018] [proxy:error] [pid 12904:tid 17120] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 18:00:09.271577 2018] [proxy_http:error] [pid 12904:tid 17120] [client 186.28.57.69:29081] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 18:01:03.694690 2018] [proxy:error] [pid 12904:tid 16096] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 18:13:08.339137 2018] [proxy:error] [pid 12904:tid 18040] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 18:13:08.339137 2018] [proxy:error] [pid 12904:tid 18040] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 18:13:08.339137 2018] [proxy_http:error] [pid 12904:tid 18040] [client 181.53.11.74:58544] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 18:16:24.039331 2018] [proxy:error] [pid 12904:tid 16524] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 18:16:24.039331 2018] [proxy:error] [pid 12904:tid 16524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 18:16:24.039331 2018] [proxy_http:error] [pid 12904:tid 16524] [client 181.53.11.74:58588] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 18:34:18.760801 2018] [proxy:error] [pid 12904:tid 16808] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.61:8080 (172.22.1.61) failed [Sun Mar 04 18:34:18.760801 2018] [proxy:error] [pid 12904:tid 16808] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.61) for 60s [Sun Mar 04 18:34:18.760801 2018] [proxy_http:error] [pid 12904:tid 16808] [client 186.80.48.231:49908] AH01114: HTTP: failed to make connection to backend: 172.22.1.61 [Sun Mar 04 19:01:57.271663 2018] [proxy:error] [pid 12904:tid 17980] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 19:01:57.271663 2018] [proxy:error] [pid 12904:tid 17980] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:01:57.271663 2018] [proxy_http:error] [pid 12904:tid 17980] [client 200.118.245.226:49684] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:01:57.759690 2018] [proxy:error] [pid 12904:tid 15720] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Sun Mar 04 19:01:57.759690 2018] [proxy_http:error] [pid 12904:tid 15720] [client 200.118.245.226:49685] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:02:01.684915 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 19:23:19.175983 2018] [proxy:error] [pid 12904:tid 17036] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 19:23:19.175983 2018] [proxy:error] [pid 12904:tid 17036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:23:19.175983 2018] [proxy_http:error] [pid 12904:tid 17036] [client 186.28.83.96:53800] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:24:43.958833 2018] [proxy:error] [pid 12904:tid 15896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 19:24:43.958833 2018] [proxy:error] [pid 12904:tid 15896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:24:43.958833 2018] [proxy_http:error] [pid 12904:tid 15896] [client 186.28.83.96:53819] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:24:50.471205 2018] [proxy:error] [pid 12904:tid 16312] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 19:34:00.939690 2018] [proxy:error] [pid 12904:tid 16524] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 19:34:00.939690 2018] [proxy:error] [pid 12904:tid 16524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:34:00.939690 2018] [proxy_http:error] [pid 12904:tid 16524] [client 181.53.11.74:58797] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:39:42.291214 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 19:39:42.299215 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 19:40:31.976056 2018] [proxy:error] [pid 12904:tid 16088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 19:40:31.976056 2018] [proxy:error] [pid 12904:tid 16088] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:40:31.976056 2018] [proxy_http:error] [pid 12904:tid 16088] [client 190.157.165.228:50444] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 19:52:33.076301 2018] [proxy:error] [pid 12904:tid 15672] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 19:52:33.076301 2018] [proxy:error] [pid 12904:tid 15672] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 19:52:33.076301 2018] [proxy_http:error] [pid 12904:tid 15672] [client 190.157.165.228:50518] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Sun Mar 04 19:52:33.173306 2018] [proxy:error] [pid 12904:tid 18028] AH00940: HTTP: disabled connection for (172.22.1.31) [Sun Mar 04 20:31:50.379131 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed [Sun Mar 04 20:31:50.379131 2018] [proxy:error] [pid 12904:tid 16072] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 20:31:50.379131 2018] [proxy_http:error] [pid 12904:tid 16072] [client 181.53.11.74:61109] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 20:32:07.179092 2018] [proxy:error] [pid 12904:tid 16096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 20:32:07.179092 2018] [proxy_http:error] [pid 12904:tid 16096] [client 181.53.11.74:61112] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx [Sun Mar 04 20:37:55.267001 2018] [proxy:error] [pid 12904:tid 17616] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 20:37:55.267001 2018] [proxy:error] [pid 12904:tid 17616] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 20:37:55.267001 2018] [proxy_http:error] [pid 12904:tid 17616] [client 181.49.95.70:55836] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Sun Mar 04 20:50:37.539601 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Sun Mar 04 21:31:29.967871 2018] [proxy:error] [pid 12904:tid 16104] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Sun Mar 04 21:31:29.967871 2018] [proxy:error] [pid 12904:tid 16104] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Sun Mar 04 21:31:29.967871 2018] [proxy_http:error] [pid 12904:tid 16104] [client 190.27.106.221:57297] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W& [Sun Mar 04 21:31:45.834779 2018] [proxy:error] [pid 12904:tid 18124] AH00940: HTTP: disabled connection for (172.22.1.31) |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0624 ]-- |