Software: Apache. PHP/5.5.15 uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 SYSTEM Safe-mode: OFF (not secure) E:\nuevo\apache\logs\ drwxrwxrwx | |
| Viewing file: Select action/file-type: [Fri Mar 02 01:02:41.907273 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 01:03:12.907046 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 01:06:27.571180 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 01:10:08.537819 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 01:11:47.567483 2018] [core:error] [pid 12904:tid 17456] (20024)The given path is misformatted or contained invalid characters: [client 40.77.167.149:8719] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 02 01:45:04.118679 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php
[Fri Mar 02 01:45:04.328691 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php5
[Fri Mar 02 01:45:04.531703 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php-cgi
[Fri Mar 02 01:45:04.757716 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php.cgi
[Fri Mar 02 01:45:04.962727 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php4
[Fri Mar 02 01:45:05.173739 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/php5-cli
[Fri Mar 02 01:45:05.376751 2018] [cgi:error] [pid 12904:tid 15776] [client 89.19.24.154:37755] script not found or unable to stat: E:/nuevo/cgi-bin/test.cgi
[Fri Mar 02 01:46:29.093539 2018] [core:error] [pid 12904:tid 15776] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.122:53706] AH00127: Cannot map GET /www.ambientebogota.gov.co:81 HTTP/1.1 to file
[Fri Mar 02 01:46:31.378670 2018] [core:error] [pid 12904:tid 17644] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.122:53709] AH00127: Cannot map GET /js/),this.$menu.html(t),this},next:function(t){var n=this.$menu.find( HTTP/1.1 to file
[Fri Mar 02 01:46:32.155714 2018] [core:error] [pid 12904:tid 16276] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.122:53724] AH00127: Cannot map GET /js/));Yt.optgroup=Yt.option,Yt.tbody=Yt.tfoot=Yt.colgroup=Yt.caption=Yt.thead,Yt.th=Yt.td,it.extend({clone:function(e,t,n){var r,i,o,a,s,u=it.contains(e.ownerDocument,e);if(nt.html5Clone||it.isXMLDoc(e)||!Bt.test( HTTP/1.1 to file
[Fri Mar 02 01:46:32.657743 2018] [core:error] [pid 12904:tid 15980] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.122:53729] AH00127: Cannot map GET /js/,data:t}).done(function(e){i=arguments,a.html(r?it( HTTP/1.1 to file
[Fri Mar 02 01:46:32.823753 2018] [core:error] [pid 12904:tid 16372] (20024)The given path is misformatted or contained invalid characters: [client 199.168.137.122:53730] AH00127: Cannot map GET /js/],_default:nt.htmlSerialize?[0, HTTP/1.1 to file
[Fri Mar 02 02:03:44.956787 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 02:04:15.956560 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 02:07:37.181070 2018] [proxy:error] [pid 12904:tid 17864] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Mar 02 02:07:37.181070 2018] [proxy:error] [pid 12904:tid 17864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Mar 02 02:07:37.181070 2018] [proxy_http:error] [pid 12904:tid 17864] [client 152.61.128.50:40070] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Mar 02 02:07:37.479087 2018] [proxy:error] [pid 12904:tid 17864] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 02 02:07:37.777104 2018] [proxy:error] [pid 12904:tid 17864] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 02 02:29:07.430868 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 02:29:38.430641 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 02:31:41.576685 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 02:37:08.557387 2018] [proxy:error] [pid 12904:tid 16024] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Mar 02 02:37:08.557387 2018] [proxy:error] [pid 12904:tid 16024] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Mar 02 02:37:08.557387 2018] [proxy_http:error] [pid 12904:tid 16024] [client 152.61.192.232:49070] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Mar 02 02:37:08.838403 2018] [proxy:error] [pid 12904:tid 16024] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 02 02:37:09.135420 2018] [proxy:error] [pid 12904:tid 16024] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 02 02:39:35.420787 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 03:26:52.504059 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 03:27:23.503832 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 03:40:46.430757 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 03:41:17.430530 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 03:55:54.152675 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 04:25:12.257233 2018] [proxy:error] [pid 12904:tid 18300] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 04:25:12.257233 2018] [proxy:error] [pid 12904:tid 18300] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 04:25:12.257233 2018] [proxy_http:error] [pid 12904:tid 18300] [client 66.249.64.139:44090] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 04:36:59.866706 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 04:53:05.403932 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 04:53:36.404705 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 05:21:53.285761 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 05:22:24.285534 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:33:01.137868 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:48:17.086257 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:48:48.086030 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:48:48.086030 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:52:59.018383 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 06:52:59.018383 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 07:02:58.757686 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 07:03:29.757459 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 07:17:04.957086 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 07:17:35.957859 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 07:28:33.805486 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed
[Fri Mar 02 07:28:33.805486 2018] [proxy:error] [pid 12904:tid 16908] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 07:28:33.805486 2018] [proxy_http:error] [pid 12904:tid 16908] [client 66.249.88.63:39960] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 07:43:28.494659 2018] [proxy:error] [pid 12904:tid 17508] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 07:43:28.494659 2018] [proxy:error] [pid 12904:tid 17508] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 07:43:28.494659 2018] [proxy_http:error] [pid 12904:tid 17508] [client 201.245.192.253:53480] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 08:11:40.884458 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:14:40.821750 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:15:11.821523 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:17:20.104860 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:17:51.104634 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:18:07.004543 2018] [core:error] [pid 12904:tid 18084] [client 89.248.172.16:47752] AH00135: Invalid method in request quit
[Fri Mar 02 08:29:42.157303 2018] [proxy:error] [pid 12904:tid 15996] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 08:29:42.157303 2018] [proxy:error] [pid 12904:tid 15996] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 08:29:42.157303 2018] [proxy_http:error] [pid 12904:tid 15996] [client 66.249.64.139:63285] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 08:43:28.721580 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:43:59.721353 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 08:50:25.521420 2018] [proxy:error] [pid 12904:tid 17972] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 08:50:25.521420 2018] [proxy:error] [pid 12904:tid 17972] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 08:50:25.521420 2018] [proxy_http:error] [pid 12904:tid 17972] [client 201.245.192.253:55997] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 08:50:34.757948 2018] [proxy:error] [pid 12904:tid 16112] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 08:50:34.757948 2018] [proxy:error] [pid 12904:tid 16112] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 08:50:34.757948 2018] [proxy_http:error] [pid 12904:tid 16112] [client 201.245.192.253:55998] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 09:31:33.584585 2018] [proxy:error] [pid 12904:tid 16636] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 09:31:33.584585 2018] [proxy:error] [pid 12904:tid 16636] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 09:31:33.584585 2018] [proxy_http:error] [pid 12904:tid 16636] [client 190.24.229.178:25285] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 09:38:09.042204 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 09:45:55.262870 2018] [proxy:error] [pid 12904:tid 16444] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 09:45:55.262870 2018] [proxy:error] [pid 12904:tid 16444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 09:45:55.262870 2018] [proxy_http:error] [pid 12904:tid 16444] [client 186.31.151.137:4451] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 10:34:34.890863 2018] [proxy_http:error] [pid 12904:tid 17404] (OS 10054)An existing connection was forcibly closed by the remote host. : [client 201.245.192.253:55861] AH01102: error reading status line from remote server 172.22.1.61:8080, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse
[Fri Mar 02 10:34:34.890863 2018] [proxy:error] [pid 12904:tid 17404] [client 201.245.192.253:55861] AH00898: Error reading from remote server returned by /sipse/faces/javax.faces.resource/images/ui-bg_flat_0_2d5972_40x100.png, referer: http://190.27.245.106/sipse/faces/javax.faces.resource/theme.css?ln=primefaces-sipse
[Fri Mar 02 10:38:47.745326 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 10:39:18.745099 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 10:42:46.306971 2018] [proxy:error] [pid 12904:tid 16936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 10:42:46.306971 2018] [proxy:error] [pid 12904:tid 16936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 10:42:46.306971 2018] [proxy_http:error] [pid 12904:tid 16936] [client 201.245.192.253:50347] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 10:43:01.179821 2018] [proxy:error] [pid 12904:tid 18080] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 10:43:01.179821 2018] [proxy_http:error] [pid 12904:tid 18080] [client 201.245.192.253:50354] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 10:51:06.779596 2018] [proxy:error] [pid 12904:tid 15732] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 10:51:06.779596 2018] [proxy:error] [pid 12904:tid 15732] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 10:51:06.779596 2018] [proxy_http:error] [pid 12904:tid 15732] [client 201.245.192.253:62900] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 10:51:11.750880 2018] [proxy:error] [pid 12904:tid 16656] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 10:51:11.750880 2018] [proxy_http:error] [pid 12904:tid 16656] [client 201.245.192.253:62903] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 10:55:10.879558 2018] [proxy:error] [pid 12904:tid 16372] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 10:55:10.879558 2018] [proxy:error] [pid 12904:tid 16372] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 10:55:10.879558 2018] [proxy_http:error] [pid 12904:tid 16372] [client 186.155.30.66:58100] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Fri Mar 02 10:59:51.561612 2018] [proxy:error] [pid 12904:tid 16664] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 10:59:51.561612 2018] [proxy:error] [pid 12904:tid 16664] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 10:59:51.561612 2018] [proxy_http:error] [pid 12904:tid 16664] [client 186.155.30.66:58426] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Fri Mar 02 10:59:54.139759 2018] [proxy:error] [pid 12904:tid 16588] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 10:59:56.560898 2018] [proxy:error] [pid 12904:tid 15776] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 10:59:56.560898 2018] [proxy_http:error] [pid 12904:tid 15776] [client 186.155.30.66:58428] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda
[Fri Mar 02 11:01:55.261687 2018] [proxy:error] [pid 12904:tid 18304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 11:01:55.261687 2018] [proxy:error] [pid 12904:tid 18304] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 11:01:55.261687 2018] [proxy_http:error] [pid 12904:tid 18304] [client 186.155.30.66:58463] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 11:07:32.479975 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 11:08:36.264623 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 11:08:36.320626 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 11:14:52.661152 2018] [proxy:error] [pid 12904:tid 18136] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 11:14:52.661152 2018] [proxy:error] [pid 12904:tid 18136] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 11:14:52.661152 2018] [proxy_http:error] [pid 12904:tid 18136] [client 181.148.67.87:61217] 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
[Fri Mar 02 11:16:45.708618 2018] [proxy:error] [pid 12904:tid 16180] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 11:16:45.708618 2018] [proxy:error] [pid 12904:tid 16180] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 11:16:45.708618 2018] [proxy_http:error] [pid 12904:tid 16180] [client 186.155.204.124:52754] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 11:53:57.276256 2018] [proxy:error] [pid 12904:tid 15644] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 11:53:57.276256 2018] [proxy:error] [pid 12904:tid 15644] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 11:53:57.276256 2018] [proxy_http:error] [pid 12904:tid 15644] [client 181.57.167.66:36428] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 11:53:57.301258 2018] [proxy:error] [pid 12904:tid 15644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 11:53:57.330259 2018] [proxy:error] [pid 12904:tid 15644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 11:53:57.353261 2018] [proxy:error] [pid 12904:tid 15644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 11:53:57.377262 2018] [proxy:error] [pid 12904:tid 15644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 11:53:57.422264 2018] [proxy:error] [pid 12904:tid 15644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 12:05:04.277406 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:05:35.377185 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:13:07.010017 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed
[Fri Mar 02 12:13:07.010017 2018] [proxy:error] [pid 12904:tid 16844] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 12:13:07.010017 2018] [proxy_http:error] [pid 12904:tid 16844] [client 201.245.192.253:51009] 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&
[Fri Mar 02 12:13:09.780176 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
[Fri Mar 02 12:13:09.780176 2018] [proxy_http:error] [pid 12904:tid 17572] [client 201.245.192.253:51010] 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&
[Fri Mar 02 12:13:27.480188 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
[Fri Mar 02 12:13:27.480188 2018] [proxy_http:error] [pid 12904:tid 17616] [client 201.245.192.253:51034] 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&
[Fri Mar 02 12:19:01.626300 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:31:13.310150 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:31:44.309923 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:33:11.931935 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 12:43:33.655495 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 13:08:00.086370 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 13:13:09.610074 2018] [proxy:error] [pid 12904:tid 16852] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 13:13:09.610074 2018] [proxy:error] [pid 12904:tid 16852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 13:13:09.610074 2018] [proxy_http:error] [pid 12904:tid 16852] [client 201.245.192.253:55541] 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
[Fri Mar 02 13:13:18.682593 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
[Fri Mar 02 13:13:18.682593 2018] [proxy_http:error] [pid 12904:tid 15684] [client 201.245.192.253:55546] 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
[Fri Mar 02 13:41:33.296519 2018] [core:error] [pid 12904:tid 18052] (20024)The given path is misformatted or contained invalid characters: [client 201.245.192.253:52604] AH00127: Cannot map GET /galeria/nivo-slider/demo/about:blank HTTP/1.1 to file, referer: http://www.ambientebogota.gov.co/es/
[Fri Mar 02 13:43:59.777898 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 14:07:02.202968 2018] [proxy:error] [pid 12904:tid 17912] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 14:07:02.202968 2018] [proxy:error] [pid 12904:tid 17912] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 14:07:02.202968 2018] [proxy_http:error] [pid 12904:tid 17912] [client 201.245.192.253:51698] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 14:44:59.861242 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 14:45:30.861016 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:20:53.694435 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:21:24.694208 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:40:53.801077 2018] [proxy:error] [pid 12904:tid 17468] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 15:40:53.801077 2018] [proxy:error] [pid 12904:tid 17468] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 15:40:53.801077 2018] [proxy_http:error] [pid 12904:tid 17468] [client 66.249.88.63:35385] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 15:42:31.731678 2018] [core:error] [pid 12904:tid 15672] (20024)The given path is misformatted or contained invalid characters: [client 66.249.64.29:53777] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 02 15:48:18.601518 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:48:30.175180 2018] [core:error] [pid 12904:tid 17932] [client 80.82.77.33:33472] AH00135: Invalid method in request quit
[Fri Mar 02 15:49:44.627438 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:50:15.627211 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 15:58:19.209871 2018] [proxy:error] [pid 12904:tid 16692] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 15:58:19.209871 2018] [proxy:error] [pid 12904:tid 16692] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 15:58:19.209871 2018] [proxy_http:error] [pid 12904:tid 16692] [client 201.245.192.253:53422] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 15:58:29.686470 2018] [proxy:error] [pid 12904:tid 17932] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 15:58:44.043291 2018] [proxy:error] [pid 12904:tid 17916] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:00:36.703735 2018] [proxy:error] [pid 12904:tid 16916] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:00:36.703735 2018] [proxy:error] [pid 12904:tid 16916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:00:36.703735 2018] [proxy_http:error] [pid 12904:tid 16916] [client 186.80.191.236:61362] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:06:43.748729 2018] [proxy:error] [pid 12904:tid 16676] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:06:43.748729 2018] [proxy:error] [pid 12904:tid 16676] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:06:43.748729 2018] [proxy_http:error] [pid 12904:tid 16676] [client 186.28.92.170:54488] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:06:58.247558 2018] [proxy:error] [pid 12904:tid 17404] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:07:15.907568 2018] [proxy:error] [pid 12904:tid 16692] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:07:27.651240 2018] [proxy:error] [pid 12904:tid 15672] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:09:25.973007 2018] [core:error] [pid 12904:tid 18136] (20024)The given path is misformatted or contained invalid characters: [client 217.182.192.80:45848] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 02 16:13:12.971991 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
[Fri Mar 02 16:13:12.971991 2018] [proxy:error] [pid 12904:tid 15952] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:13:12.971991 2018] [proxy_http:error] [pid 12904:tid 15952] [client 201.245.192.253:51110] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:13:34.086199 2018] [proxy:error] [pid 12904:tid 17500] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:13:36.867358 2018] [proxy:error] [pid 12904:tid 18144] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:17:22.730276 2018] [proxy:error] [pid 12904:tid 16012] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:17:22.730276 2018] [proxy:error] [pid 12904:tid 16012] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:17:22.730276 2018] [proxy_http:error] [pid 12904:tid 16012] [client 201.245.192.253:64079] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:17:32.407830 2018] [proxy:error] [pid 12904:tid 16596] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:17:53.148016 2018] [proxy:error] [pid 12904:tid 18092] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:18:29.659105 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 16:18:44.010925 2018] [proxy:error] [pid 12904:tid 17520] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:18:44.010925 2018] [proxy:error] [pid 12904:tid 17520] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:18:44.010925 2018] [proxy_http:error] [pid 12904:tid 17520] [client 201.245.192.253:64122] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:18:50.911320 2018] [proxy:error] [pid 12904:tid 16644] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:18:57.441694 2018] [proxy:error] [pid 12904:tid 16916] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:18:59.710823 2018] [proxy:error] [pid 12904:tid 17772] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:18:59.710823 2018] [proxy_http:error] [pid 12904:tid 17772] [client 201.245.192.253:64127] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:19:00.658878 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 16:20:34.211228 2018] [proxy:error] [pid 12904:tid 15836] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:20:34.211228 2018] [proxy:error] [pid 12904:tid 15836] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:20:34.211228 2018] [proxy_http:error] [pid 12904:tid 15836] [client 201.245.192.253:64150] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:21:58.011022 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed
[Fri Mar 02 16:21:58.011022 2018] [proxy:error] [pid 12904:tid 16844] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:21:58.011022 2018] [proxy_http:error] [pid 12904:tid 16844] [client 201.245.192.253:60855] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:24:07.201411 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
[Fri Mar 02 16:24:07.201411 2018] [proxy:error] [pid 12904:tid 17572] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:24:07.201411 2018] [proxy_http:error] [pid 12904:tid 17572] [client 201.245.192.253:49352] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:24:07.877449 2018] [proxy:error] [pid 12904:tid 17572] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:24:08.912509 2018] [proxy:error] [pid 12904:tid 16748] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:24:08.912509 2018] [proxy_http:error] [pid 12904:tid 16748] [client 201.245.192.253:49353] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:24:09.800559 2018] [proxy:error] [pid 12904:tid 15916] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:24:09.800559 2018] [proxy_http:error] [pid 12904:tid 15916] [client 201.245.192.253:49354] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:24:14.267815 2018] [proxy:error] [pid 12904:tid 18012] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:24:14.267815 2018] [proxy_http:error] [pid 12904:tid 18012] [client 201.245.192.253:53300] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:24:24.601406 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
[Fri Mar 02 16:24:24.601406 2018] [proxy_http:error] [pid 12904:tid 15704] [client 201.245.192.253:49356] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:25:36.129497 2018] [proxy:error] [pid 12904:tid 17488] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:25:36.129497 2018] [proxy:error] [pid 12904:tid 17488] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:25:36.129497 2018] [proxy_http:error] [pid 12904:tid 17488] [client 201.245.192.253:60948] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:26:02.793022 2018] [proxy:error] [pid 12904:tid 17500] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:26:12.120556 2018] [proxy:error] [pid 12904:tid 15676] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:27:02.330428 2018] [proxy:error] [pid 12904:tid 15936] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:27:02.330428 2018] [proxy:error] [pid 12904:tid 15936] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:27:02.330428 2018] [proxy_http:error] [pid 12904:tid 15936] [client 201.245.192.253:60964] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:28:54.892866 2018] [proxy:error] [pid 12904:tid 17560] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:28:54.892866 2018] [proxy:error] [pid 12904:tid 17560] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:28:54.892866 2018] [proxy_http:error] [pid 12904:tid 17560] [client 201.245.192.253:56334] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:29:02.473299 2018] [proxy:error] [pid 12904:tid 18304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:29:02.473299 2018] [proxy_http:error] [pid 12904:tid 18304] [client 190.24.131.66:59840] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:29:57.431443 2018] [proxy:error] [pid 12904:tid 17228] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:29:57.431443 2018] [proxy:error] [pid 12904:tid 17228] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:29:57.431443 2018] [proxy_http:error] [pid 12904:tid 17228] [client 190.24.131.66:59853] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:30:03.494790 2018] [proxy:error] [pid 12904:tid 15672] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:30:15.049451 2018] [proxy:error] [pid 12904:tid 18144] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:30:15.049451 2018] [proxy_http:error] [pid 12904:tid 18144] [client 201.245.192.253:52152] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:30:38.392786 2018] [proxy:error] [pid 12904:tid 18144] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:30:38.392786 2018] [proxy:error] [pid 12904:tid 18144] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:30:38.392786 2018] [proxy_http:error] [pid 12904:tid 18144] [client 190.24.131.66:59862] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:30:44.749149 2018] [proxy:error] [pid 12904:tid 15864] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 16:30:44.749149 2018] [proxy_http:error] [pid 12904:tid 15864] [client 201.245.192.253:52180] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:30:47.173288 2018] [proxy:error] [pid 12904:tid 17228] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:30:47.173288 2018] [proxy_http:error] [pid 12904:tid 17228] [client 201.245.192.253:56512] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:31:33.692949 2018] [proxy:error] [pid 12904:tid 15728] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:31:33.692949 2018] [proxy:error] [pid 12904:tid 15728] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:31:33.692949 2018] [proxy_http:error] [pid 12904:tid 15728] [client 201.245.192.253:56593] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/Medicion/ConsultaIndicadores.aspx
[Fri Mar 02 16:31:38.493223 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
[Fri Mar 02 16:31:38.493223 2018] [proxy_http:error] [pid 12904:tid 16096] [client 201.245.192.253:61992] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:31:39.893303 2018] [proxy:error] [pid 12904:tid 18304] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:31:39.893303 2018] [proxy_http:error] [pid 12904:tid 18304] [client 201.245.192.253:56603] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/Medicion/ConsultaIndicadores.aspx
[Fri Mar 02 16:32:50.695353 2018] [proxy:error] [pid 12904:tid 16444] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:32:50.695353 2018] [proxy:error] [pid 12904:tid 16444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:32:50.695353 2018] [proxy_http:error] [pid 12904:tid 16444] [client 201.245.192.253:62090] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:34:44.650871 2018] [proxy:error] [pid 12904:tid 17772] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:34:44.650871 2018] [proxy:error] [pid 12904:tid 17772] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:34:44.650871 2018] [proxy_http:error] [pid 12904:tid 17772] [client 201.245.192.253:62219] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:37:48.195369 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
[Fri Mar 02 16:37:48.195369 2018] [proxy:error] [pid 12904:tid 15684] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:37:48.195369 2018] [proxy_http:error] [pid 12904:tid 15684] [client 186.28.92.170:54807] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:38:04.695313 2018] [proxy:error] [pid 12904:tid 16116] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 16:38:04.695313 2018] [proxy_http:error] [pid 12904:tid 16116] [client 201.245.192.253:62300] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:42:01.495857 2018] [proxy:error] [pid 12904:tid 18084] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:42:01.495857 2018] [proxy:error] [pid 12904:tid 18084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:42:01.495857 2018] [proxy_http:error] [pid 12904:tid 18084] [client 186.28.92.170:55311] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:42:07.651209 2018] [proxy:error] [pid 12904:tid 17348] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:42:07.651209 2018] [proxy_http:error] [pid 12904:tid 17348] [client 186.28.92.170:55317] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:44:01.751735 2018] [proxy:error] [pid 12904:tid 17772] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:44:01.751735 2018] [proxy:error] [pid 12904:tid 17772] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:44:01.751735 2018] [proxy_http:error] [pid 12904:tid 17772] [client 186.28.92.170:55499] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:44:27.503208 2018] [proxy:error] [pid 12904:tid 15916] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:47:40.251233 2018] [proxy:error] [pid 12904:tid 16300] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:47:40.251233 2018] [proxy:error] [pid 12904:tid 16300] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:47:40.251233 2018] [proxy_http:error] [pid 12904:tid 16300] [client 186.28.92.170:55612] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:49:29.132460 2018] [proxy:error] [pid 12904:tid 17524] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:49:29.132460 2018] [proxy:error] [pid 12904:tid 17524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:49:29.132460 2018] [proxy_http:error] [pid 12904:tid 17524] [client 186.28.92.170:55664] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:51:30.632410 2018] [proxy:error] [pid 12904:tid 16452] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 16:51:30.632410 2018] [proxy:error] [pid 12904:tid 16452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:51:30.632410 2018] [proxy_http:error] [pid 12904:tid 16452] [client 201.245.192.253:61137] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:52:09.949659 2018] [proxy:error] [pid 12904:tid 18100] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:52:56.932346 2018] [proxy:error] [pid 12904:tid 17968] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:52:56.932346 2018] [proxy:error] [pid 12904:tid 17968] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:52:56.932346 2018] [proxy_http:error] [pid 12904:tid 17968] [client 186.28.92.170:55686] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:53:12.932261 2018] [proxy:error] [pid 12904:tid 17524] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:53:12.932261 2018] [proxy_http:error] [pid 12904:tid 17524] [client 186.28.92.170:55705] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:53:39.595786 2018] [proxy:error] [pid 12904:tid 16444] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:53:39.595786 2018] [proxy:error] [pid 12904:tid 16444] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:53:39.595786 2018] [proxy_http:error] [pid 12904:tid 16444] [client 186.28.92.170:55712] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 16:56:49.695659 2018] [proxy:error] [pid 12904:tid 17928] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:56:49.695659 2018] [proxy:error] [pid 12904:tid 17928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:56:49.695659 2018] [proxy_http:error] [pid 12904:tid 17928] [client 186.28.92.170:55767] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 16:57:42.946705 2018] [proxy:error] [pid 12904:tid 17100] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 16:58:34.553657 2018] [proxy:error] [pid 12904:tid 17412] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 16:58:34.553657 2018] [proxy:error] [pid 12904:tid 17412] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 16:58:34.553657 2018] [proxy_http:error] [pid 12904:tid 17412] [client 201.245.192.253:61244] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/frmHome.aspx
[Fri Mar 02 17:18:26.266819 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:18:57.266592 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:21:02.297743 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:21:33.297516 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:26:30.697527 2018] [proxy:error] [pid 12904:tid 16292] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:26:30.697527 2018] [proxy:error] [pid 12904:tid 16292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:26:30.697527 2018] [proxy_http:error] [pid 12904:tid 16292] [client 186.28.92.170:56093] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 17:26:37.900939 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
[Fri Mar 02 17:26:37.901939 2018] [proxy_http:error] [pid 12904:tid 17392] [client 190.60.224.146:32181] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 17:27:06.034548 2018] [proxy:error] [pid 12904:tid 16220] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:27:06.034548 2018] [proxy:error] [pid 12904:tid 16220] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:27:06.034548 2018] [proxy_http:error] [pid 12904:tid 16220] [client 186.28.92.170:56108] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:29:36.097131 2018] [proxy:error] [pid 12904:tid 16828] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:29:36.097131 2018] [proxy:error] [pid 12904:tid 16828] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:29:36.097131 2018] [proxy_http:error] [pid 12904:tid 16828] [client 186.28.92.170:56154] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:30:21.728741 2018] [proxy:error] [pid 12904:tid 17804] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 17:30:32.435353 2018] [proxy:error] [pid 12904:tid 15628] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 17:30:57.697798 2018] [proxy:error] [pid 12904:tid 16004] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:30:57.697798 2018] [proxy:error] [pid 12904:tid 16004] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:30:57.697798 2018] [proxy_http:error] [pid 12904:tid 16004] [client 201.245.192.253:53699] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:31:24.225315 2018] [proxy:error] [pid 12904:tid 16032] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 17:31:49.526763 2018] [proxy:error] [pid 12904:tid 18176] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 17:32:24.497763 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:32:55.497536 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:33:40.135089 2018] [proxy:error] [pid 12904:tid 17804] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:33:40.135089 2018] [proxy:error] [pid 12904:tid 17804] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:33:40.135089 2018] [proxy_http:error] [pid 12904:tid 17804] [client 201.245.192.253:53741] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:37:19.334626 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
[Fri Mar 02 17:37:19.334626 2018] [proxy:error] [pid 12904:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:37:19.334626 2018] [proxy_http:error] [pid 12904:tid 17956] [client 201.245.192.253:53771] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:41:02.734404 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:41:02.734404 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:41:02.735404 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:41:02.735404 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:41:02.735404 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 17:49:53.998791 2018] [proxy:error] [pid 12904:tid 16172] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 17:49:53.998791 2018] [proxy:error] [pid 12904:tid 16172] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:49:53.998791 2018] [proxy_http:error] [pid 12904:tid 16172] [client 201.245.192.253:53830] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:51:28.098173 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
[Fri Mar 02 17:51:28.098173 2018] [proxy:error] [pid 12904:tid 15896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 17:51:28.098173 2018] [proxy_http:error] [pid 12904:tid 15896] [client 201.245.192.253:53837] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 17:53:46.768104 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 18:04:29.997895 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
[Fri Mar 02 18:04:29.997895 2018] [proxy:error] [pid 12904:tid 17956] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 18:04:29.997895 2018] [proxy_http:error] [pid 12904:tid 17956] [client 201.245.192.253:53902] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 18:23:12.280086 2018] [proxy:error] [pid 12904:tid 16928] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 18:23:12.280086 2018] [proxy:error] [pid 12904:tid 16928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 18:23:12.280086 2018] [proxy_http:error] [pid 12904:tid 16928] [client 201.245.192.253:54072] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 18:27:55.499285 2018] [proxy:error] [pid 12904: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.31:80 (172.22.1.31) failed
[Fri Mar 02 18:27:55.499285 2018] [proxy:error] [pid 12904:tid 17292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 18:27:55.499285 2018] [proxy_http:error] [pid 12904:tid 17292] [client 186.28.92.170:56638] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/frmHome.aspx
[Fri Mar 02 18:41:25.399609 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 18:41:56.399382 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 18:53:57.734640 2018] [proxy:error] [pid 12904:tid 15748] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 18:53:57.734640 2018] [proxy:error] [pid 12904:tid 15748] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 18:53:57.734640 2018] [proxy_http:error] [pid 12904:tid 15748] [client 186.28.92.170:56943] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 18:55:22.310477 2018] [proxy:error] [pid 12904:tid 17500] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 18:55:22.310477 2018] [proxy:error] [pid 12904:tid 17500] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 18:55:22.310477 2018] [proxy_http:error] [pid 12904:tid 17500] [client 186.28.92.170:56991] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/frmHome.aspx
[Fri Mar 02 18:55:46.660870 2018] [proxy:error] [pid 12904:tid 16544] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 18:56:03.168814 2018] [proxy:error] [pid 12904:tid 17912] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 19:10:34.434648 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 19:18:12.689859 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
[Fri Mar 02 19:18:12.689859 2018] [proxy:error] [pid 12904:tid 16244] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 19:18:12.689859 2018] [proxy_http:error] [pid 12904:tid 16244] [client 186.28.92.170:57199] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 19:39:01.135266 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 19:39:32.135039 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 20:06:08.443342 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 20:06:08.444342 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 20:25:49.734908 2018] [proxy:error] [pid 12904:tid 15764] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 20:25:49.734908 2018] [proxy:error] [pid 12904:tid 15764] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:25:49.734908 2018] [proxy_http:error] [pid 12904:tid 15764] [client 190.156.183.10:49795] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 20:26:07.097901 2018] [proxy:error] [pid 12904:tid 16388] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 02 20:26:07.097901 2018] [proxy_http:error] [pid 12904:tid 16388] [client 190.156.183.10:49804] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 20:32:52.236074 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 20:33:53.244563 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
[Fri Mar 02 20:33:53.244563 2018] [proxy:error] [pid 12904:tid 18016] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:33:53.244563 2018] [proxy_http:error] [pid 12904:tid 18016] [client 190.156.183.10:49991] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 20:43:25.098272 2018] [proxy:error] [pid 12904: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
[Fri Mar 02 20:43:25.098272 2018] [proxy:error] [pid 12904:tid 16260] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:43:25.098272 2018] [proxy_http:error] [pid 12904:tid 16260] [client 190.156.183.10:50038] 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
[Fri Mar 02 20:43:35.799884 2018] [proxy:error] [pid 12904:tid 16164] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 20:45:29.477386 2018] [core:error] [pid 12904:tid 18016] (20024)The given path is misformatted or contained invalid characters: [client 138.197.64.79:56166] AH00127: Cannot map GET /galeria/carrusel/Carrusel/jquery-ui-%0A%0A1.8.13.custom.min.js HTTP/1.1 to file
[Fri Mar 02 20:45:38.334892 2018] [proxy:error] [pid 12904:tid 15756] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 20:45:38.334892 2018] [proxy:error] [pid 12904:tid 15756] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:45:38.334892 2018] [proxy_http:error] [pid 12904:tid 15756] [client 190.156.183.10:50095] 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
[Fri Mar 02 20:46:05.338437 2018] [proxy:error] [pid 12904:tid 15952] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 20:46:34.889127 2018] [proxy:error] [pid 12904:tid 17276] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 20:48:57.400278 2018] [proxy:error] [pid 12904:tid 16292] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 20:48:57.400278 2018] [proxy:error] [pid 12904:tid 16292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:48:57.400278 2018] [proxy_http:error] [pid 12904:tid 16292] [client 190.156.183.10:50348] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 20:50:30.935628 2018] [proxy:error] [pid 12904:tid 16944] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 20:50:30.935628 2018] [proxy:error] [pid 12904:tid 16944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:50:30.935628 2018] [proxy_http:error] [pid 12904:tid 16944] [client 190.156.183.10:50356] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 20:52:47.145419 2018] [proxy:error] [pid 12904:tid 16944] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 20:52:47.145419 2018] [proxy:error] [pid 12904:tid 16944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:52:47.145419 2018] [proxy_http:error] [pid 12904:tid 16944] [client 190.156.183.10:50384] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 02 20:59:08.145211 2018] [proxy:error] [pid 12904:tid 16944] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 20:59:08.145211 2018] [proxy:error] [pid 12904:tid 16944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 20:59:08.145211 2018] [proxy_http:error] [pid 12904:tid 16944] [client 190.156.183.10:50593] 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
[Fri Mar 02 20:59:21.961001 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
[Fri Mar 02 20:59:21.961001 2018] [proxy_http:error] [pid 12904:tid 17616] [client 190.156.183.10:50596] 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
[Fri Mar 02 21:05:02.097456 2018] [proxy:error] [pid 12904:tid 18092] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:05:02.097456 2018] [proxy:error] [pid 12904:tid 18092] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:05:02.097456 2018] [proxy_http:error] [pid 12904:tid 18092] [client 186.114.17.111:61371] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:05:09.986907 2018] [proxy:error] [pid 12904:tid 17308] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 02 21:05:10.697948 2018] [proxy:error] [pid 12904:tid 16768] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:05:10.697948 2018] [proxy_http:error] [pid 12904:tid 16768] [client 186.114.17.111:61378] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:05:36.999452 2018] [proxy:error] [pid 12904:tid 17308] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:05:36.999452 2018] [proxy:error] [pid 12904:tid 17308] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:05:36.999452 2018] [proxy_http:error] [pid 12904:tid 17308] [client 186.114.17.111:61389] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:05:42.945792 2018] [proxy:error] [pid 12904:tid 18092] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:05:42.945792 2018] [proxy_http:error] [pid 12904:tid 18092] [client 186.114.17.111:61390] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:06:15.345645 2018] [proxy:error] [pid 12904:tid 17308] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:06:15.345645 2018] [proxy:error] [pid 12904:tid 17308] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:06:15.345645 2018] [proxy_http:error] [pid 12904:tid 17308] [client 186.114.17.111:61398] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:06:25.445223 2018] [proxy:error] [pid 12904:tid 17228] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:06:25.445223 2018] [proxy_http:error] [pid 12904:tid 17228] [client 186.114.17.111:61400] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:06:57.945082 2018] [proxy:error] [pid 12904:tid 18108] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:06:57.945082 2018] [proxy:error] [pid 12904:tid 18108] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:06:57.945082 2018] [proxy_http:error] [pid 12904:tid 18108] [client 186.114.17.111:61536] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:09:43.099528 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
[Fri Mar 02 21:09:43.099528 2018] [proxy:error] [pid 12904:tid 16096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:09:43.099528 2018] [proxy_http:error] [pid 12904:tid 16096] [client 186.114.17.111:61554] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:13:03.234975 2018] [proxy:error] [pid 12904:tid 18028] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Fri Mar 02 21:13:03.234975 2018] [proxy:error] [pid 12904:tid 18028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 02 21:13:03.234975 2018] [proxy_http:error] [pid 12904:tid 18028] [client 186.114.17.111:61564] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://190.27.245.106:8080/isolucionsda/PaginaLogin.aspx
[Fri Mar 02 21:29:00.399722 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 21:29:00.399722 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 21:54:14.832343 2018] [core:error] [pid 12904:tid 17572] (20024)The given path is misformatted or contained invalid characters: [client 54.209.136.228:37776] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 02 22:05:25.152683 2018] [core:error] [pid 12904:tid 16316] (20024)The given path is misformatted or contained invalid characters: [client 54.209.136.228:21924] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 02 22:06:33.404586 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 22:06:33.404586 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 22:28:49.962033 2018] [access_compat:error] [pid 12904:tid 15756] [client 80.82.64.70:47722] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin
[Fri Mar 02 22:28:50.294052 2018] [access_compat:error] [pid 12904:tid 16312] [client 80.82.64.70:48034] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/scripts
[Fri Mar 02 22:31:48.762260 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 22:32:19.762033 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 23:31:37.737538 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 23:58:12.406747 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 02 23:58:43.406521 2018] [mpm_winnt:warn] [pid 12904:tid 19512] (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 ]-- |