190.27.245.106 - c99shell

!C99Shell v. 1.0 pre-release build #13!
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 Free 9.41 GB of 239.26 GB (3.93%) Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ] Encoder Tools Proc. FTP brute Sec. SQL PHP-code Update Feedback Self remove Logout
!C99Shell v. 1.0 pre-release build #13!
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
Free 9.41 GB of 239.26 GB (3.93%)
Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ]
Encoder Tools Proc. FTP brute Sec. SQL PHP-code Update Feedback Self remove Logout
Viewing file: argis-sda-error.log (25.98 KB) -rw-rw-rw-
Select action/file-type:
(+) | (+) |
(+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |
[Thu Feb 08 14:57:47.949237 2018] [proxy:error] [pid 8356:tid 17048] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Thu Feb 08 14:57:47.949237 2018] [proxy:error] [pid 8356:tid 17048] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Thu Feb 08 14:57:47.949237 2018] [proxy_http:error] [pid 8356:tid 17048] [client 201.245.192.253:51335] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Thu Feb 08 14:58:02.438066 2018] [proxy:error] [pid 8356:tid 17048] AH00940: HTTP: disabled connection for (172.22.1.51)
[Thu Feb 08 14:58:17.495927 2018] [proxy:error] [pid 8356:tid 17384] AH00940: HTTP: disabled connection for (172.22.1.51)
[Thu Feb 08 14:58:21.302145 2018] [proxy:error] [pid 8356:tid 17296] AH00940: HTTP: disabled connection for (172.22.1.51)
[Thu Feb 08 14:58:23.597276 2018] [proxy:error] [pid 8356:tid 16724] AH00940: HTTP: disabled connection for (172.22.1.51)
[Thu Feb 08 15:05:20.527123 2018] [proxy:error] [pid 8356:tid 17124] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Thu Feb 08 15:05:20.527123 2018] [proxy:error] [pid 8356:tid 17124] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Thu Feb 08 15:05:20.527123 2018] [proxy_http:error] [pid 8356:tid 17124] [client 201.245.192.253:56331] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Thu Feb 08 15:40:00.598096 2018] [proxy:error] [pid 8356: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.51:8399 (172.22.1.51) failed
[Thu Feb 08 15:40:00.598096 2018] [proxy:error] [pid 8356:tid 16928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Thu Feb 08 15:40:00.598096 2018] [proxy_http:error] [pid 8356:tid 16928] [client 201.245.192.253:62477] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Thu Feb 08 15:40:35.410087 2018] [proxy:error] [pid 8356:tid 16388] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 09:40:47.015099 2018] [proxy:error] [pid 6812: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.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:40:47.022100 2018] [proxy:error] [pid 6812:tid 17292] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:40:47.022100 2018] [proxy_http:error] [pid 6812:tid 17292] [client 201.245.192.253:53630] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:40:50.889321 2018] [proxy:error] [pid 6812:tid 16804] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:40:50.889321 2018] [proxy_http:error] [pid 6812:tid 16804] [client 201.245.192.253:53633] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:42:36.783378 2018] [proxy:error] [pid 6812:tid 17436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:42:36.783378 2018] [proxy:error] [pid 6812:tid 17436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:42:36.783378 2018] [proxy_http:error] [pid 6812:tid 17436] [client 201.245.192.253:53415] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:42:55.476447 2018] [proxy:error] [pid 6812:tid 17088] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:42:55.476447 2018] [proxy_http:error] [pid 6812:tid 17088] [client 201.245.192.253:53416] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:45:16.344504 2018] [proxy:error] [pid 6812:tid 16160] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:45:16.344504 2018] [proxy:error] [pid 6812:tid 16160] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:45:16.344504 2018] [proxy_http:error] [pid 6812:tid 16160] [client 201.245.192.253:53678] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:48:57.829172 2018] [proxy:error] [pid 3724:tid 17536] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:48:57.836173 2018] [proxy:error] [pid 3724:tid 17536] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:48:57.836173 2018] [proxy_http:error] [pid 3724:tid 17536] [client 201.245.192.253:53741] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:49:26.648821 2018] [proxy:error] [pid 2352:tid 17632] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:49:26.660821 2018] [proxy:error] [pid 2352:tid 17632] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:49:26.660821 2018] [proxy_http:error] [pid 2352:tid 17632] [client 201.245.192.253:53754] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:49:27.923894 2018] [proxy:error] [pid 2352:tid 17620] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:49:27.923894 2018] [proxy_http:error] [pid 2352:tid 17620] [client 201.245.192.253:53755] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:50:01.276801 2018] [proxy:error] [pid 2352:tid 17800] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:50:01.276801 2018] [proxy:error] [pid 2352:tid 17800] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:50:01.276801 2018] [proxy_http:error] [pid 2352:tid 17800] [client 201.245.192.253:53766] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:50:05.688054 2018] [proxy:error] [pid 2352:tid 17340] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:50:05.688054 2018] [proxy_http:error] [pid 2352:tid 17340] [client 201.245.192.253:53767] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:52:39.929876 2018] [proxy:error] [pid 2352:tid 17424] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:52:39.929876 2018] [proxy:error] [pid 2352:tid 17424] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:52:39.929876 2018] [proxy_http:error] [pid 2352:tid 17424] [client 201.245.192.253:53804] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:54:10.680066 2018] [proxy:error] [pid 16872:tid 17436] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 09:54:10.685067 2018] [proxy:error] [pid 16872:tid 17436] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 09:54:10.685067 2018] [proxy_http:error] [pid 16872:tid 17436] [client 201.245.192.253:53774] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 09:54:31.278244 2018] [proxy:error] [pid 16872:tid 17564] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 09:54:31.278244 2018] [proxy_http:error] [pid 16872:tid 17564] [client 201.245.192.253:53783] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 14:16:52.852611 2018] [proxy:error] [pid 16872:tid 16856] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 14:16:52.852611 2018] [proxy:error] [pid 16872:tid 16856] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 14:16:52.852611 2018] [proxy_http:error] [pid 16872:tid 16856] [client 186.31.117.57:46400] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Fri Feb 09 14:16:56.649828 2018] [proxy:error] [pid 16872:tid 17664] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:16:58.992962 2018] [proxy:error] [pid 16872:tid 16776] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:00.903071 2018] [proxy:error] [pid 16872:tid 17664] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:05.712346 2018] [proxy:error] [pid 16872:tid 16244] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:08.018478 2018] [proxy:error] [pid 16872:tid 16244] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:25.597484 2018] [proxy:error] [pid 16872:tid 17628] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:29.498707 2018] [proxy:error] [pid 16872:tid 17628] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:41.685404 2018] [proxy:error] [pid 16872:tid 17020] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:17:50.531910 2018] [proxy:error] [pid 16872:tid 17020] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 14:19:42.247300 2018] [proxy:error] [pid 16872:tid 17036] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Feb 09 14:19:42.247300 2018] [proxy:error] [pid 16872:tid 17036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 14:19:42.247300 2018] [proxy_http:error] [pid 16872:tid 17036] [client 186.31.117.57:46568] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Fri Feb 09 14:19:48.941683 2018] [proxy:error] [pid 16872:tid 16212] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 14:19:48.941683 2018] [proxy_http:error] [pid 16872:tid 16212] [client 186.31.117.57:46570] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Fri Feb 09 14:20:01.580406 2018] [proxy:error] [pid 16872:tid 17080] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 14:20:01.580406 2018] [proxy_http:error] [pid 16872:tid 17080] [client 186.31.117.57:46572] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 14:45:52.026086 2018] [proxy:error] [pid 16872:tid 16856] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 14:45:52.026086 2018] [proxy:error] [pid 16872:tid 16856] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 14:45:52.026086 2018] [proxy_http:error] [pid 16872:tid 16856] [client 186.31.117.57:47122] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Feb 09 16:45:15.894836 2018] [proxy:error] [pid 16872:tid 16772] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 16:45:15.894836 2018] [proxy:error] [pid 16872:tid 16772] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 16:45:15.894836 2018] [proxy_http:error] [pid 16872:tid 16772] [client 201.245.192.253:50574] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Fri Feb 09 16:45:22.632221 2018] [proxy:error] [pid 16872:tid 17012] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:24.686339 2018] [proxy:error] [pid 16872:tid 16416] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:26.058417 2018] [proxy:error] [pid 16872:tid 17148] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:26.819461 2018] [proxy:error] [pid 16872:tid 17148] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:28.130536 2018] [proxy:error] [pid 16872:tid 16468] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:30.135650 2018] [proxy:error] [pid 16872:tid 16360] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 09 16:45:34.250886 2018] [proxy:error] [pid 16872:tid 16708] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 16:45:34.250886 2018] [proxy_http:error] [pid 16872:tid 16708] [client 201.245.192.253:50585] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/service
[Fri Feb 09 16:50:10.771702 2018] [proxy:error] [pid 16872:tid 17148] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 09 16:50:10.771702 2018] [proxy:error] [pid 16872:tid 17148] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 09 16:50:10.771702 2018] [proxy_http:error] [pid 16872:tid 17148] [client 201.245.192.253:50641] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Mon Feb 12 16:27:07.841995 2018] [proxy:error] [pid 16872:tid 16432] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Mon Feb 12 16:27:07.841995 2018] [proxy:error] [pid 16872:tid 16432] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Mon Feb 12 16:27:07.841995 2018] [proxy_http:error] [pid 16872:tid 16432] [client 201.245.192.253:63596] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://www.arcgis.com/home/webmap/viewer.html?featurecollection=http%3A%2F%2Fargis.ambientebogota.gov.co%2Farcgis%2Frest%2Fservices%3Ff%3Djson%26option%3Dfootprints&supportsProjection=true&supportsJSONP=true
[Mon Feb 12 16:27:23.594896 2018] [proxy:error] [pid 16872:tid 16364] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Mon Feb 12 16:27:23.594896 2018] [proxy_http:error] [pid 16872:tid 16364] [client 201.245.192.253:63605] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://cdn-a.arcgis.com/cdn/180EF7B/js/jsapi/esri/core/request/iframe.html
[Tue Feb 13 23:21:31.866933 2018] [proxy:error] [pid 16872:tid 16084] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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
[Tue Feb 13 23:21:31.866933 2018] [proxy:error] [pid 16872:tid 16084] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Tue Feb 13 23:21:31.866933 2018] [proxy_http:error] [pid 16872:tid 16084] [client 186.31.117.57:46828] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Tue Feb 13 23:21:45.229697 2018] [proxy:error] [pid 16872:tid 16084] AH00940: HTTP: disabled connection for (172.22.1.51)
[Tue Feb 13 23:21:46.955796 2018] [proxy:error] [pid 16872:tid 16196] AH00940: HTTP: disabled connection for (172.22.1.51)
[Tue Feb 13 23:21:49.472940 2018] [proxy:error] [pid 16872:tid 16196] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 16 09:31:11.814781 2018] [proxy:error] [pid 17536:tid 16892] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 16 09:31:11.822781 2018] [proxy:error] [pid 17536:tid 16892] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 16 09:31:11.822781 2018] [proxy_http:error] [pid 17536:tid 16892] [client 201.245.192.253:44836] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Fri Feb 16 09:31:27.980706 2018] [proxy:error] [pid 17536:tid 17780] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Feb 16 09:34:03.404595 2018] [proxy:error] [pid 17536:tid 16404] (OS 10060)A connection attempt failed because the connected party did not properly respond after 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 Feb 16 09:34:03.404595 2018] [proxy:error] [pid 17536:tid 16404] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Feb 16 09:34:03.404595 2018] [proxy_http:error] [pid 17536:tid 16404] [client 201.245.192.253:44860] AH01114: HTTP: failed to make connection to backend: 172.22.1.51, referer: http://argis.ambientebogota.gov.co/rest/services
[Tue Mar 06 12:08:03.408841 2018] [proxy:error] [pid 12904:tid 17932] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 192.168.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:03.413842 2018] [proxy:error] [pid 12904:tid 17932] AH00959: ap_proxy_connect_backend disabling worker for (192.168.250.52) for 60s
[Tue Mar 06 12:08:03.413842 2018] [proxy_http:error] [pid 12904:tid 17932] [client 201.245.192.253:65222] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:08:03.413842 2018] [proxy:error] [pid 12904:tid 17932] AH00940: HTTP: disabled connection for (192.168.250.52)
[Tue Mar 06 12:08:03.985874 2018] [proxy:error] [pid 12904:tid 18312] (OS 10060)A connection attempt failed because the connected party did not 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.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:03.985874 2018] [proxy_http:error] [pid 12904:tid 18312] [client 201.245.192.253:65224] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:08:07.396070 2018] [proxy:error] [pid 12904:tid 15812] (OS 10060)A connection attempt failed because the connected party did not 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.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:07.396070 2018] [proxy:error] [pid 12904:tid 15812] AH00959: ap_proxy_connect_backend disabling worker for (192.168.250.52) for 60s
[Tue Mar 06 12:08:07.396070 2018] [proxy_http:error] [pid 12904:tid 15812] [client 201.245.192.253:65223] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:08:07.396070 2018] [proxy:error] [pid 12904:tid 15812] AH00940: HTTP: disabled connection for (192.168.250.52)
[Tue Mar 06 12:08:22.796950 2018] [proxy:error] [pid 12904:tid 16884] (OS 10060)A connection attempt failed because the connected party did not 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.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:22.796950 2018] [proxy_http:error] [pid 12904:tid 16884] [client 186.80.191.236:50717] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:08:24.997076 2018] [proxy:error] [pid 12904:tid 18312] (OS 10060)A connection attempt failed because the connected party did not 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.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:24.997076 2018] [proxy:error] [pid 12904:tid 18312] AH00959: ap_proxy_connect_backend disabling worker for (192.168.250.52) for 60s
[Tue Mar 06 12:08:24.997076 2018] [proxy_http:error] [pid 12904:tid 18312] [client 201.245.192.253:65224] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:08:25.009077 2018] [proxy:error] [pid 12904:tid 18312] AH00940: HTTP: disabled connection for (192.168.250.52)
[Tue Mar 06 12:08:25.009077 2018] [proxy:error] [pid 12904:tid 18312] AH00940: HTTP: disabled connection for (192.168.250.52)
[Tue Mar 06 12:08:43.885157 2018] [proxy:error] [pid 12904:tid 16884] (OS 10060)A connection attempt failed because the connected party did not 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.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:08:43.885157 2018] [proxy_http:error] [pid 12904:tid 16884] [client 186.80.191.236:50717] AH01114: HTTP: failed to make connection to backend: 192.168.250.52
[Tue Mar 06 12:09:05.385386 2018] [proxy:error] [pid 12904: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 192.168.250.52:6080 (192.168.250.52) failed
[Tue Mar 06 12:09:05.385386 2018] [proxy:error] [pid 12904:tid 18132] AH00959: ap_proxy_connect_backend disabling worker for (192.168.250.52) for 60s
[Tue Mar 06 12:09:05.385386 2018] [proxy_http:error] [pid 12904:tid 18132] [client 186.80.191.236:50725] AH01114: HTTP: failed to make connection to backend: 192.168.250.52, referer: http://argis.ambientebogota.gov.co/
[Tue Mar 06 12:09:05.385386 2018] [proxy:error] [pid 12904:tid 18132] AH00940: HTTP: disabled connection for (192.168.250.52)
:: Command execute ::
Enter:	Select:
:: Search ::
:: Upload ::
:: Make Dir ::
:: Make File ::
:: Go Dir ::
:: Go File ::
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0468 ]--