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: [Wed Jun 27 00:01:40.974607 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 00:46:23.399319 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 00:48:25.594333 2018] [proxy:error] [pid 8864:tid 12868] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Wed Jun 27 00:48:25.594333 2018] [proxy:error] [pid 8864:tid 12868] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Wed Jun 27 00:48:25.594333 2018] [proxy_http:error] [pid 8864:tid 12868] [client 66.249.66.155:42363] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Wed Jun 27 01:11:02.032316 2018] [proxy:error] [pid 8864:tid 6492] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 01:11:02.032316 2018] [proxy:error] [pid 8864:tid 6492] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Jun 27 01:11:02.032316 2018] [proxy_http:error] [pid 8864:tid 6492] [client 152.61.128.50:33764] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Jun 27 01:11:02.266316 2018] [proxy:error] [pid 8864:tid 14908] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Jun 27 01:11:02.500316 2018] [proxy:error] [pid 8864:tid 12868] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Jun 27 01:21:02.773771 2018] [cgi:error] [pid 8864:tid 7068] [client 181.143.160.146:59232] script not found or unable to stat: E:/nuevo/htdocs/login.cgi [Wed Jun 27 01:37:02.581057 2018] [proxy:error] [pid 8864:tid 7164] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 01:37:02.581057 2018] [proxy:error] [pid 8864:tid 7164] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s [Wed Jun 27 01:37:02.581057 2018] [proxy_http:error] [pid 8864:tid 7164] [client 152.61.192.232:38786] AH01114: HTTP: failed to make connection to backend: 172.22.1.51 [Wed Jun 27 01:37:02.861857 2018] [proxy:error] [pid 8864:tid 7164] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Jun 27 01:37:03.142658 2018] [proxy:error] [pid 8864:tid 7164] AH00940: HTTP: disabled connection for (172.22.1.51) [Wed Jun 27 03:33:58.178579 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 05:34:46.356910 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 05:34:46.356910 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 05:34:46.356910 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 05:43:42.607851 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 05:43:42.607851 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 06:47:23.101362 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 07:11:42.140725 2018] [proxy:error] [pid 8864:tid 12588] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 07:11:42.140725 2018] [proxy:error] [pid 8864:tid 12588] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 07:11:42.140725 2018] [proxy_http:error] [pid 8864:tid 12588] [client 66.249.66.143:51686] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 07:16:04.626786 2018] [proxy:error] [pid 8864:tid 17824] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 07:16:04.626786 2018] [proxy:error] [pid 8864:tid 17824] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 07:16:04.626786 2018] [proxy_http:error] [pid 8864:tid 17824] [client 66.249.66.143:60161] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 08:06:23.388088 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 08:07:25.382597 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 08:14:53.134583 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 08:37:06.874526 2018] [proxy:error] [pid 8864:tid 7164] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 08:37:06.874526 2018] [proxy:error] [pid 8864:tid 7164] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 08:37:06.874526 2018] [proxy_http:error] [pid 8864:tid 7164] [client 82.210.255.132:19337] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 09:02:14.741974 2018] [access_compat:error] [pid 8864:tid 4812] [client 203.195.191.219:59020] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/index.php [Wed Jun 27 09:02:16.723178 2018] [access_compat:error] [pid 8864:tid 10352] [client 203.195.191.219:59416] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin [Wed Jun 27 09:02:46.956031 2018] [access_compat:error] [pid 8864:tid 18056] [client 203.195.191.219:64645] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpmyadmin0 [Wed Jun 27 09:02:48.843634 2018] [access_compat:error] [pid 8864:tid 18056] [client 203.195.191.219:64771] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpmyadmin1 [Wed Jun 27 09:02:49.608035 2018] [access_compat:error] [pid 8864:tid 10352] [client 203.195.191.219:65112] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpmyadmin2 [Wed Jun 27 09:02:52.852841 2018] [access_compat:error] [pid 8864:tid 10352] [client 203.195.191.219:65369] AH01797: client denied by server configuration: E:/nuevo/htdocs/xampp/phpmyadmin [Wed Jun 27 09:02:53.586042 2018] [access_compat:error] [pid 8864:tid 10352] [client 203.195.191.219:1167] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyadmin_bak [Wed Jun 27 09:02:56.706048 2018] [access_compat:error] [pid 8864:tid 9568] [client 203.195.191.219:1411] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpmyadmin-old [Wed Jun 27 09:02:57.408049 2018] [access_compat:error] [pid 8864:tid 16608] [client 203.195.191.219:1722] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdminold [Wed Jun 27 09:02:58.094450 2018] [access_compat:error] [pid 8864:tid 16608] [client 203.195.191.219:1865] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin.old [Wed Jun 27 09:03:02.914859 2018] [access_compat:error] [pid 8864:tid 7656] [client 203.195.191.219:2518] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/phpmyadmin [Wed Jun 27 09:03:04.771262 2018] [access_compat:error] [pid 8864:tid 7656] [client 203.195.191.219:2829] AH01797: client denied by server configuration: E:/nuevo/htdocs/phpMyAdmin [Wed Jun 27 09:31:53.394698 2018] [proxy:error] [pid 8864:tid 13852] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 09:31:53.394698 2018] [proxy:error] [pid 8864:tid 13852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 09:31:53.394698 2018] [proxy_http:error] [pid 8864:tid 13852] [client 186.31.107.204:23618] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 09:31:53.410298 2018] [proxy:error] [pid 8864:tid 12724] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 09:31:53.410298 2018] [proxy:error] [pid 8864:tid 13852] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 09:35:21.015463 2018] [core:error] [pid 8864:tid 12096] (20024)The given path is misformatted or contained invalid characters: [client 201.245.192.253:55175] AH00127: Cannot map GET /galeria/nivo-slider/demo/about:blank HTTP/1.1 to file, referer: http://www.ambientebogota.gov.co/es/ [Wed Jun 27 09:44:57.608075 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 09:44:57.608075 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 09:44:57.873276 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 10:15:17.351272 2018] [proxy:error] [pid 8864: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 [Wed Jun 27 10:15:17.351272 2018] [proxy:error] [pid 8864:tid 17560] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 10:15:17.351272 2018] [proxy_http:error] [pid 8864:tid 17560] [client 181.49.74.106:52620] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 10:15:18.724074 2018] [proxy:error] [pid 8864:tid 16560] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 10:15:18.724074 2018] [proxy_http:error] [pid 8864:tid 16560] [client 181.49.74.106:53639] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 11:10:51.997529 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 11:12:38.998117 2018] [core:error] [pid 8864:tid 12868] (20024)The given path is misformatted or contained invalid characters: [client 104.131.178.32:53164] AH00127: Cannot map GET /galeria/carrusel/Carrusel/jquery-ui-%0A%0A1.8.13.custom.min.js HTTP/1.1 to file [Wed Jun 27 11:43:44.106193 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 11:43:44.137393 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 12:00:04.240314 2018] [proxy:error] [pid 8864:tid 11052] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:00:04.240314 2018] [proxy:error] [pid 8864:tid 11052] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 12:00:04.240314 2018] [proxy_http:error] [pid 8864:tid 11052] [client 201.245.192.253:61341] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:43.126131 2018] [proxy:error] [pid 8864:tid 13648] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:43.126131 2018] [proxy:error] [pid 8864:tid 13648] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 12:09:43.126131 2018] [proxy_http:error] [pid 8864:tid 13648] [client 186.30.240.103:49651] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:44.296133 2018] [proxy:error] [pid 8864:tid 6724] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:44.296133 2018] [proxy_http:error] [pid 8864:tid 6724] [client 186.30.240.103:49652] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:45.497335 2018] [proxy:error] [pid 8864:tid 9704] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:45.497335 2018] [proxy_http:error] [pid 8864:tid 9704] [client 186.30.240.103:49653] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:46.136936 2018] [proxy:error] [pid 8864:tid 7792] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:46.136936 2018] [proxy_http:error] [pid 8864:tid 7792] [client 186.30.240.103:49654] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:46.402137 2018] [proxy:error] [pid 8864:tid 12900] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:46.402137 2018] [proxy_http:error] [pid 8864:tid 12900] [client 186.30.240.103:49657] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:46.714137 2018] [proxy:error] [pid 8864:tid 9020] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:46.714137 2018] [proxy_http:error] [pid 8864:tid 9020] [client 186.30.240.103:49658] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:09:46.823337 2018] [proxy:error] [pid 8864:tid 10268] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:09:46.823337 2018] [proxy_http:error] [pid 8864:tid 10268] [client 186.30.240.103:49656] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:35:18.028427 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 12:42:28.027582 2018] [proxy:error] [pid 8864:tid 7976] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:42:28.027582 2018] [proxy:error] [pid 8864:tid 7976] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 12:42:28.027582 2018] [proxy_http:error] [pid 8864:tid 7976] [client 66.249.66.153:44337] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 12:50:07.479589 2018] [proxy:error] [pid 8864:tid 18152] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 12:50:07.479589 2018] [proxy:error] [pid 8864:tid 18152] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 12:50:07.479589 2018] [proxy_http:error] [pid 8864:tid 18152] [client 66.249.66.153:57554] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 13:21:24.552886 2018] [proxy:error] [pid 8864:tid 12716] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed [Wed Jun 27 13:21:24.552886 2018] [proxy:error] [pid 8864:tid 12716] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.32) for 60s [Wed Jun 27 13:21:24.552886 2018] [proxy_http:error] [pid 8864:tid 12716] [client 66.249.88.33:63213] AH01114: HTTP: failed to make connection to backend: 172.22.1.32, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Jun 27 13:21:29.638495 2018] [proxy:error] [pid 8864:tid 16008] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.32:80 (172.22.1.32) failed [Wed Jun 27 13:21:29.638495 2018] [proxy_http:error] [pid 8864:tid 16008] [client 181.57.251.206:43483] AH01114: HTTP: failed to make connection to backend: 172.22.1.32, referer: http://www.ambientebogota.gov.co/web/intranet/aplicaciones-para-acceder-fuera-de-la-sda [Wed Jun 27 14:04:31.817430 2018] [proxy:error] [pid 8864:tid 15400] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Jun 27 14:04:31.817430 2018] [proxy:error] [pid 8864:tid 15400] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 14:04:31.817430 2018] [proxy_http:error] [pid 8864:tid 15400] [client 66.249.66.155:42568] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 14:22:43.538548 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 14:37:39.260921 2018] [mpm_winnt:warn] [pid 8864:tid 19376] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 14:43:15.285511 2018] [proxy:warn] [pid 7868:tid 196] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Jun 27 14:43:15.285511 2018] [mpm_winnt:warn] [pid 7868:tid 196] AH00445: ThreadsPerChild of 2500 exceeds ThreadLimit of 1920, decreasing to match [Wed Jun 27 14:43:15.332311 2018] [core:warn] [pid 7868:tid 196] AH00098: pid file E:/nuevo/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Wed Jun 27 14:43:15.332311 2018] [auth_digest:notice] [pid 7868:tid 196] AH01757: generating secret for digest authentication ... [Wed Jun 27 14:43:15.535112 2018] [mpm_winnt:notice] [pid 7868:tid 196] AH00455: Apache/2.4.10 (Win32) OpenSSL/1.0.1i configured -- resuming normal operations [Wed Jun 27 14:43:15.535112 2018] [mpm_winnt:notice] [pid 7868:tid 196] AH00456: Apache Lounge VC11 Server built: Jul 17 2014 11:50:08 [Wed Jun 27 14:43:15.535112 2018] [core:notice] [pid 7868:tid 196] AH00094: Command line: 'e:\\nuevo\\apache\\bin\\httpd.exe -d E:/nuevo/apache' [Wed Jun 27 14:43:15.550712 2018] [mpm_winnt:notice] [pid 7868:tid 196] AH00418: Parent: Created child process 8524 AH00548: NameVirtualHost has no effect and will be removed in the next release E:/nuevo/apache/conf/extra/httpd-vhosts.conf:44 [Wed Jun 27 14:43:16.143513 2018] [proxy:warn] [pid 8524:tid 212] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Jun 27 14:43:16.393113 2018] [proxy:warn] [pid 8524:tid 212] AH01146: Ignoring parameter 'timeout=700' for worker 'http://172.22.1.26:8080/forest' because of worker sharing [Wed Jun 27 14:43:16.471113 2018] [auth_digest:notice] [pid 8524:tid 212] AH01757: generating secret for digest authentication ... [Wed Jun 27 14:43:16.689514 2018] [mpm_winnt:notice] [pid 8524:tid 212] AH00354: Child: Starting 1920 worker threads. [Wed Jun 27 15:06:34.295968 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 15:48:44.308412 2018] [proxy:error] [pid 8524:tid 18272] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 15:48:44.308412 2018] [proxy:error] [pid 8524:tid 18272] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 15:48:44.308412 2018] [proxy_http:error] [pid 8524:tid 18272] [client 181.62.61.81:59709] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 15:48:50.439223 2018] [proxy:error] [pid 8524:tid 18344] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 15:48:57.927236 2018] [proxy:error] [pid 8524:tid 18068] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 15:48:57.927236 2018] [proxy_http:error] [pid 8524:tid 18068] [client 181.62.61.81:59714] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 15:48:59.986440 2018] [proxy:error] [pid 8524:tid 18008] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 15:48:59.986440 2018] [proxy_http:error] [pid 8524:tid 18008] [client 181.62.61.81:59716] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 15:49:00.173640 2018] [proxy:error] [pid 8524:tid 18280] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 15:49:00.173640 2018] [proxy_http:error] [pid 8524:tid 18280] [client 181.62.61.81:59715] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 15:53:18.837694 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 15:54:43.155842 2018] [proxy:error] [pid 8524:tid 18000] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 15:54:43.155842 2018] [proxy:error] [pid 8524:tid 18000] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 15:54:43.155842 2018] [proxy_http:error] [pid 8524:tid 18000] [client 181.55.6.31:53773] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:27:32.160101 2018] [proxy:error] [pid 8524:tid 18156] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Wed Jun 27 16:27:32.160101 2018] [proxy:error] [pid 8524:tid 18156] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Wed Jun 27 16:27:32.160101 2018] [proxy_http:error] [pid 8524:tid 18156] [client 190.147.80.81:50044] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Wed Jun 27 16:27:32.316101 2018] [proxy:error] [pid 8524:tid 17940] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Wed Jun 27 16:27:32.316101 2018] [proxy_http:error] [pid 8524:tid 17940] [client 190.147.80.81:50046] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Wed Jun 27 16:27:33.408103 2018] [proxy:error] [pid 8524:tid 17940] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 172.22.1.26:8080 (172.22.1.26) failed [Wed Jun 27 16:27:33.408103 2018] [proxy:error] [pid 8524:tid 17940] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.26) for 60s [Wed Jun 27 16:27:33.408103 2018] [proxy_http:error] [pid 8524:tid 17940] [client 190.147.80.81:50048] AH01114: HTTP: failed to make connection to backend: 172.22.1.26 [Wed Jun 27 16:28:05.388159 2018] [proxy:error] [pid 8524:tid 18272] AH00940: HTTP: disabled connection for (172.22.1.26) [Wed Jun 27 16:28:05.388159 2018] [proxy:error] [pid 8524:tid 17912] AH00940: HTTP: disabled connection for (172.22.1.26) [Wed Jun 27 16:28:05.466159 2018] [proxy:error] [pid 8524:tid 17912] AH00940: HTTP: disabled connection for (172.22.1.26) [Wed Jun 27 16:49:34.808424 2018] [proxy:error] [pid 8524:tid 18256] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 16:49:34.808424 2018] [proxy:error] [pid 8524:tid 18256] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 16:49:34.808424 2018] [proxy_http:error] [pid 8524:tid 18256] [client 66.249.66.155:54098] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:53:00.744386 2018] [core:error] [pid 8524:tid 18016] (20024)The given path is misformatted or contained invalid characters: [client 190.144.212.132:65048] AH00127: Cannot map GET /%22imagenes/image002.jpg/%22 HTTP/1.1 to file, referer: http://190.27.245.106/BLA/resoluciones/RESOLUCIONES%202009/2840.pdf [Wed Jun 27 16:53:00.759986 2018] [core:error] [pid 8524:tid 18016] (20024)The given path is misformatted or contained invalid characters: [client 190.144.212.132:65049] AH00127: Cannot map GET /%22imagenes/image004.jpg/%22 HTTP/1.1 to file, referer: http://190.27.245.106/BLA/resoluciones/RESOLUCIONES%202009/2840.pdf [Wed Jun 27 16:53:57.372485 2018] [proxy:error] [pid 8524:tid 17948] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 16:53:57.372485 2018] [proxy:error] [pid 8524:tid 17948] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 16:53:57.372485 2018] [proxy_http:error] [pid 8524:tid 17948] [client 66.249.66.153:40556] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:59:31.025871 2018] [proxy:error] [pid 8524: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 [Wed Jun 27 16:59:31.025871 2018] [proxy:error] [pid 8524:tid 18136] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 16:59:31.025871 2018] [proxy_http:error] [pid 8524:tid 18136] [client 181.131.237.234:50290] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:59:35.393879 2018] [proxy:error] [pid 8524:tid 18076] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 16:59:35.393879 2018] [proxy_http:error] [pid 8524:tid 18076] [client 181.131.237.234:50291] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:59:35.627879 2018] [proxy:error] [pid 8524:tid 17872] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 16:59:35.627879 2018] [proxy_http:error] [pid 8524:tid 17872] [client 181.131.237.234:50292] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:59:36.517081 2018] [proxy:error] [pid 8524:tid 18120] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 16:59:36.517081 2018] [proxy_http:error] [pid 8524:tid 18120] [client 181.131.237.234:50293] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 16:59:37.094282 2018] [proxy:error] [pid 8524:tid 18100] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Jun 27 16:59:37.094282 2018] [proxy_http:error] [pid 8524:tid 18100] [client 181.131.237.234:50294] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 17:11:27.769130 2018] [proxy:error] [pid 8524:tid 17996] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 17:11:27.769130 2018] [proxy:error] [pid 8524:tid 17996] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 17:11:27.769130 2018] [proxy_http:error] [pid 8524:tid 17996] [client 66.249.66.153:50755] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 17:12:12.432008 2018] [proxy:error] [pid 8524:tid 18256] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 17:38:22.122365 2018] [proxy:error] [pid 8524:tid 18184] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 17:38:22.122365 2018] [proxy:error] [pid 8524:tid 18184] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 17:38:22.122365 2018] [proxy_http:error] [pid 8524:tid 18184] [client 66.249.66.155:47670] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 17:39:14.101657 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 18:00:32.352302 2018] [core:error] [pid 8524:tid 17944] (20024)The given path is misformatted or contained invalid characters: [client 157.55.39.206:14695] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file [Wed Jun 27 18:04:26.446313 2018] [core:error] [pid 8524:tid 17912] (20024)The given path is misformatted or contained invalid characters: [client 136.243.89.157:52506] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file, referer: http://www.dama.gov.co/ [Wed Jun 27 18:11:33.590663 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 18:43:31.941633 2018] [proxy:error] [pid 8524:tid 17960] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 18:43:31.941633 2018] [proxy:error] [pid 8524:tid 17960] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 18:43:31.941633 2018] [proxy_http:error] [pid 8524:tid 17960] [client 66.249.66.153:49271] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 18:45:43.715064 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 18:47:18.064030 2018] [proxy:error] [pid 8524:tid 17944] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 18:47:18.064030 2018] [proxy:error] [pid 8524:tid 17944] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 18:47:18.064030 2018] [proxy_http:error] [pid 8524:tid 17944] [client 66.249.66.153:46773] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 19:06:22.762840 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 19:07:56.363005 2018] [proxy:error] [pid 8524:tid 18320] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 19:07:56.363005 2018] [proxy:error] [pid 8524:tid 18320] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 19:07:56.363005 2018] [proxy_http:error] [pid 8524:tid 18320] [client 66.249.66.155:54846] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 19:40:04.432791 2018] [proxy:error] [pid 8524:tid 18096] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 19:40:04.432791 2018] [proxy:error] [pid 8524:tid 18096] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 19:40:04.432791 2018] [proxy_http:error] [pid 8524:tid 18096] [client 66.249.66.156:41428] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 19:41:26.036535 2018] [proxy:error] [pid 8524:tid 17872] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 19:41:26.036535 2018] [proxy:error] [pid 8524:tid 17872] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 19:41:26.036535 2018] [proxy_http:error] [pid 8524:tid 17872] [client 66.249.66.155:59073] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 20:23:25.394160 2018] [proxy:error] [pid 8524:tid 18216] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 20:23:25.394160 2018] [proxy:error] [pid 8524:tid 18216] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 20:23:25.394160 2018] [proxy_http:error] [pid 8524:tid 18216] [client 66.249.66.153:49623] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 20:25:18.447558 2018] [proxy:error] [pid 8524:tid 17872] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 20:25:18.447558 2018] [proxy:error] [pid 8524:tid 17872] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 20:25:18.447558 2018] [proxy_http:error] [pid 8524:tid 17872] [client 66.249.66.155:52961] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 20:59:30.319162 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 21:03:56.720830 2018] [proxy:error] [pid 8524:tid 18348] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 21:03:56.720830 2018] [proxy:error] [pid 8524:tid 18348] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 21:03:56.720830 2018] [proxy_http:error] [pid 8524:tid 18348] [client 66.249.66.155:57569] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 21:04:32.210892 2018] [proxy:error] [pid 8524:tid 18020] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 21:05:49.774229 2018] [proxy:error] [pid 8524:tid 18132] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 21:05:49.774229 2018] [proxy:error] [pid 8524:tid 18132] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 21:05:49.774229 2018] [proxy_http:error] [pid 8524:tid 18132] [client 66.249.66.155:54789] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 21:06:25.264291 2018] [proxy:error] [pid 8524:tid 18324] AH00940: HTTP: disabled connection for (172.22.1.31) [Wed Jun 27 21:07:42.874427 2018] [proxy:error] [pid 8524:tid 17896] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 21:07:42.874427 2018] [proxy:error] [pid 8524:tid 17896] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 21:07:42.874427 2018] [proxy_http:error] [pid 8524:tid 17896] [client 66.249.66.156:55467] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 21:31:19.934116 2018] [access_compat:error] [pid 8524:tid 18140] [client 66.111.41.249:52944] AH01797: client denied by server configuration: E:/nuevo/phpMyAdmin/scripts [Wed Jun 27 21:31:33.038139 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 21:31:33.038139 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 21:39:28.043373 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 22:06:30.009422 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 22:06:30.025022 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 22:19:13.100363 2018] [proxy:error] [pid 8524:tid 18040] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed [Wed Jun 27 22:19:13.100363 2018] [proxy:error] [pid 8524:tid 18040] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 22:19:13.100363 2018] [proxy_http:error] [pid 8524:tid 18040] [client 66.249.66.153:40729] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 22:40:08.075767 2018] [proxy_http:error] [pid 8524:tid 18216] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : [client 190.156.120.40:49450] AH01095: prefetch request body failed to 172.22.1.61:8080 (172.22.1.61) from 190.156.120.40 (), referer: http://190.27.245.106/sipse/faces/presentacion/financiero/solicitudProceso/consultarSolicitudProceso.xhtml [Wed Jun 27 23:57:20.457103 2018] [proxy:error] [pid 8524:tid 17892] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 [Wed Jun 27 23:57:20.457103 2018] [proxy:error] [pid 8524:tid 17892] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s [Wed Jun 27 23:57:20.457103 2018] [proxy_http:error] [pid 8524:tid 17892] [client 66.249.66.155:61356] AH01114: HTTP: failed to make connection to backend: 172.22.1.31 [Wed Jun 27 23:58:57.333273 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed. [Wed Jun 27 23:58:57.333273 2018] [mpm_winnt:warn] [pid 8524:tid 18808] (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 ]-- |