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: [Tue Aug 13 10:38:19.576102 2019] [proxy:error] [pid 7728:tid 18212] (OS 10053)An established connection was aborted by the software in your host machine. : [client 201.245.192.253:61182] AH01084: pass request body failed to 192.168.175.61:80 (192.168.175.61), referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Tue Aug 13 10:38:19.576102 2019] [proxy_http:error] [pid 7728:tid 18212] [client 201.245.192.253:61182] AH01097: pass request body failed to 192.168.175.61:80 (192.168.175.61) from 201.245.192.253 (), referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Tue Aug 13 10:41:27.665633 2019] [proxy_http:error] [pid 7728:tid 18212] (20014)Internal error: [client 201.245.192.253:61182] AH01102: error reading status line from remote server 192.168.175.61:80, referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Tue Aug 13 10:41:27.665633 2019] [proxy:error] [pid 7728:tid 18212] [client 201.245.192.253:61182] AH00898: Error reading from remote server returned by /error/HTTP_BAD_GATEWAY.html.var, referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Tue Aug 13 11:15:57.258868 2019] [proxy_http:error] [pid 7728:tid 18776] (70008)Partial results are valid but processing is incomplete: [client 201.245.192.253:57151] AH01110: error reading response, referer: http://indicadoresoab.ambientebogota.gov.co/admin/hist_indicador.php [Tue Aug 13 14:07:20.141729 2019] [proxy_http:error] [pid 7728:tid 19008] (20014)Internal error: [client 201.245.192.253:63628] AH01102: error reading status line from remote server 192.168.175.61:80, referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Tue Nov 19 17:21:35.837309 2019] [proxy:error] [pid 7320:tid 19092] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 17:21:35.837309 2019] [proxy:error] [pid 7320:tid 19092] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 17:21:35.837309 2019] [proxy_http:error] [pid 7320:tid 19092] [client 201.245.192.253:59708] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/lista_metadato.php [Tue Nov 19 17:21:35.837309 2019] [proxy:error] [pid 7320:tid 19092] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 17:51:09.638424 2019] [proxy:error] [pid 5924:tid 19272] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 17:51:09.638424 2019] [proxy:error] [pid 5924:tid 19272] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 17:51:09.638424 2019] [proxy_http:error] [pid 5924:tid 19272] [client 201.245.192.253:58424] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Tue Nov 19 17:51:09.638424 2019] [proxy:error] [pid 5924:tid 19272] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 17:51:17.485238 2019] [proxy:error] [pid 5924:tid 19284] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 17:51:17.485238 2019] [proxy:error] [pid 5924:tid 19284] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 18:55:44.201630 2019] [proxy:error] [pid 5924:tid 18708] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 18:55:44.201630 2019] [proxy:error] [pid 5924:tid 18708] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 18:55:44.201630 2019] [proxy_http:error] [pid 5924:tid 18708] [client 191.95.58.155:28432] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Tue Nov 19 18:55:44.201630 2019] [proxy:error] [pid 5924:tid 18708] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 18:55:51.096842 2019] [proxy:error] [pid 5924:tid 18804] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 18:55:51.096842 2019] [proxy_http:error] [pid 5924:tid 18804] [client 191.95.58.155:28460] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Tue Nov 19 18:56:12.141279 2019] [proxy:error] [pid 5924:tid 18804] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 18:56:12.141279 2019] [proxy:error] [pid 5924:tid 18804] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 18:56:12.141279 2019] [proxy_http:error] [pid 5924:tid 18804] [client 191.95.58.155:28460] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Tue Nov 19 18:56:12.734080 2019] [proxy:error] [pid 5924:tid 18804] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 18:56:12.734080 2019] [proxy:error] [pid 5924:tid 18804] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 19:14:19.447589 2019] [proxy:error] [pid 5924:tid 18876] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 19:14:19.447589 2019] [proxy:error] [pid 5924:tid 18876] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 19:14:19.447589 2019] [proxy_http:error] [pid 5924:tid 18876] [client 66.249.88.214:50140] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/index.php [Tue Nov 19 19:14:19.447589 2019] [proxy:error] [pid 5924:tid 18876] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 19:14:20.461590 2019] [proxy:error] [pid 5924:tid 18768] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 19:14:20.461590 2019] [proxy_http:error] [pid 5924:tid 18768] [client 66.249.88.218:53331] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/index.php [Tue Nov 19 19:14:24.439597 2019] [proxy:error] [pid 5924:tid 18716] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 19:14:24.439597 2019] [proxy:error] [pid 5924:tid 18716] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 19:14:24.439597 2019] [proxy_http:error] [pid 5924:tid 18716] [client 190.27.31.135:60388] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/index.php [Tue Nov 19 19:14:24.439597 2019] [proxy:error] [pid 5924:tid 18716] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 19:14:41.474827 2019] [proxy:error] [pid 5924:tid 18768] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 19:14:41.474827 2019] [proxy_http:error] [pid 5924:tid 18768] [client 66.249.88.218:53331] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/index.php [Tue Nov 19 19:49:40.099713 2019] [proxy:error] [pid 5924:tid 19144] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Tue Nov 19 19:49:40.099713 2019] [proxy:error] [pid 5924:tid 19144] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Tue Nov 19 19:49:40.099713 2019] [proxy_http:error] [pid 5924:tid 19144] [client 190.27.31.135:49966] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Tue Nov 19 19:49:40.099713 2019] [proxy:error] [pid 5924:tid 19144] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 19:49:40.411714 2019] [proxy:error] [pid 5924:tid 18896] AH00940: HTTP: disabled connection for (192.168.175.61) [Tue Nov 19 19:49:40.411714 2019] [proxy:error] [pid 5924:tid 18896] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Nov 20 09:27:01.235050 2019] [proxy:error] [pid 5924:tid 19216] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Wed Nov 20 09:27:01.235050 2019] [proxy:error] [pid 5924:tid 19216] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Wed Nov 20 09:27:01.235050 2019] [proxy_http:error] [pid 5924:tid 19216] [client 201.245.192.253:55380] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/index.php [Wed Nov 20 09:27:01.235050 2019] [proxy:error] [pid 5924:tid 19216] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Nov 20 09:27:01.547050 2019] [proxy:error] [pid 5924:tid 19216] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Nov 20 09:27:01.547050 2019] [proxy:error] [pid 5924:tid 19216] AH00940: HTTP: disabled connection for (192.168.175.61) [Thu Nov 21 13:41:50.310057 2019] [proxy_http:error] [pid 5924:tid 18416] (70008)Partial results are valid but processing is incomplete: [client 181.53.112.189:51303] AH01110: error reading response, referer: http://indicadoresoab.ambientebogota.gov.co/admin/login.php [Tue Jan 21 12:29:56.999870 2020] [proxy_http:error] [pid 672:tid 15736] (70008)Partial results are valid but processing is incomplete: [client 172.58.239.76:28132] AH01110: error reading response, referer: http://indicadoresoab.ambientebogota.gov.co/admin/login.php [Sat Feb 29 09:49:33.490219 2020] [proxy:error] [pid 4140:tid 17900] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Sat Feb 29 09:49:33.490219 2020] [proxy:error] [pid 4140:tid 17900] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Sat Feb 29 09:49:33.490219 2020] [proxy_http:error] [pid 4140:tid 17900] [client 190.27.98.109:53920] AH01114: HTTP: failed to make connection to backend: 192.168.175.61, referer: http://indicadoresoab.ambientebogota.gov.co/admin/edit_indicador.php [Sat Feb 29 09:49:33.490219 2020] [proxy:error] [pid 4140:tid 17900] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:15:59.336573 2020] [proxy:error] [pid 11612:tid 21056] (OS 10055)An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Wed Oct 07 07:15:59.336573 2020] [proxy:error] [pid 11612:tid 21056] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Wed Oct 07 07:15:59.336573 2020] [proxy_http:error] [pid 11612:tid 21056] [client 181.57.107.221:58912] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Wed Oct 07 07:15:59.336573 2020] [proxy:error] [pid 11612:tid 21056] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:15:59.851374 2020] [proxy:error] [pid 11612:tid 20980] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:15:59.851374 2020] [proxy:error] [pid 11612:tid 20980] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:17:51.095169 2020] [proxy:error] [pid 11612:tid 21060] (OS 10055)An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Wed Oct 07 07:17:51.095169 2020] [proxy:error] [pid 11612:tid 21060] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Wed Oct 07 07:17:51.095169 2020] [proxy_http:error] [pid 11612:tid 21060] [client 181.57.107.221:2634] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Wed Oct 07 07:17:51.095169 2020] [proxy:error] [pid 11612:tid 21060] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:17:51.407170 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:17:51.407170 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:01.377420 2020] [proxy:error] [pid 11612:tid 20892] (OS 10055)An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Wed Oct 07 07:24:01.377420 2020] [proxy:error] [pid 11612:tid 20892] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Wed Oct 07 07:24:01.377420 2020] [proxy_http:error] [pid 11612:tid 20892] [client 191.89.32.124:53924] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Wed Oct 07 07:24:01.377420 2020] [proxy:error] [pid 11612:tid 20892] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:01.549020 2020] [proxy:error] [pid 11612:tid 20892] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:01.549020 2020] [proxy:error] [pid 11612:tid 20892] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:55.805915 2020] [proxy:error] [pid 11612:tid 21060] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:55.805915 2020] [proxy:error] [pid 11612:tid 21060] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:57.038317 2020] [proxy:error] [pid 11612:tid 21060] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:24:57.038317 2020] [proxy:error] [pid 11612:tid 21060] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:25:46.038003 2020] [proxy:error] [pid 11612:tid 20996] (OS 10055)An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. : AH00957: HTTP: attempt to connect to 192.168.175.61:80 (192.168.175.61) failed [Wed Oct 07 07:25:46.038003 2020] [proxy:error] [pid 11612:tid 20996] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.61) for 60s [Wed Oct 07 07:25:46.038003 2020] [proxy_http:error] [pid 11612:tid 20996] [client 191.106.138.101:23649] AH01114: HTTP: failed to make connection to backend: 192.168.175.61 [Wed Oct 07 07:25:46.038003 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:25:46.318804 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:25:46.318804 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:26:20.373664 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:26:20.373664 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:26:20.576464 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) [Wed Oct 07 07:26:20.576464 2020] [proxy:error] [pid 11612:tid 20996] AH00940: HTTP: disabled connection for (192.168.175.61) |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0936 ]-- |