Software: Apache. PHP/5.5.15 uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 SYSTEM Safe-mode: OFF (not secure) E:\nuevo\apache\logs\ drwxrwxrwx | |
| Viewing file: Select action/file-type: [Mon May 20 14:40:47.305010 2019] [proxy:error] [pid 8052:tid 18588] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 192.168.175.44:80 (192.168.175.44) failed [Mon May 20 14:40:47.305010 2019] [proxy:error] [pid 8052:tid 18588] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon May 20 14:40:47.305010 2019] [proxy_http:error] [pid 8052:tid 18588] [client 190.145.43.210:55722] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon May 20 14:40:47.305010 2019] [proxy:error] [pid 8052:tid 18588] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:40:53.701021 2019] [proxy:error] [pid 8052:tid 18588] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:40:53.701021 2019] [proxy:error] [pid 8052:tid 18588] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.250669 2019] [proxy:error] [pid 8052:tid 18664] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.250669 2019] [proxy:error] [pid 8052:tid 18664] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.406670 2019] [proxy:error] [pid 8052:tid 18716] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.406670 2019] [proxy:error] [pid 8052:tid 18716] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.562670 2019] [proxy:error] [pid 8052:tid 18716] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:21.562670 2019] [proxy:error] [pid 8052:tid 18716] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:22.810672 2019] [proxy:error] [pid 8052:tid 18600] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:22.810672 2019] [proxy:error] [pid 8052:tid 18600] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:22.982272 2019] [proxy:error] [pid 8052:tid 18352] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:22.982272 2019] [proxy:error] [pid 8052:tid 18352] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:23.153873 2019] [proxy:error] [pid 8052:tid 18676] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:41:23.153873 2019] [proxy:error] [pid 8052:tid 18676] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:42:00.250738 2019] [proxy:error] [pid 8052:tid 18352] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 192.168.175.44:80 (192.168.175.44) failed [Mon May 20 14:42:00.250738 2019] [proxy:error] [pid 8052:tid 18352] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon May 20 14:42:00.250738 2019] [proxy_http:error] [pid 8052:tid 18352] [client 201.245.192.253:61539] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon May 20 14:42:00.250738 2019] [proxy:error] [pid 8052:tid 18352] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 14:54:13.592426 2019] [proxy:error] [pid 8052:tid 18660] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Mon May 20 14:54:13.592426 2019] [proxy:error] [pid 8052:tid 18660] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon May 20 14:54:13.592426 2019] [proxy_http:error] [pid 8052:tid 18660] [client 201.245.192.253:61295] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon May 20 14:54:13.592426 2019] [proxy:error] [pid 8052:tid 18660] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 15:01:20.675376 2019] [proxy:error] [pid 8052:tid 18756] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to 192.168.175.44:80 (192.168.175.44) failed [Mon May 20 15:01:20.675376 2019] [proxy:error] [pid 8052:tid 18756] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon May 20 15:01:20.675376 2019] [proxy_http:error] [pid 8052:tid 18756] [client 201.245.192.253:61411] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon May 20 15:01:20.675376 2019] [proxy:error] [pid 8052:tid 18756] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 15:02:08.661060 2019] [proxy:error] [pid 8052:tid 18516] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 15:02:08.661060 2019] [proxy:error] [pid 8052:tid 18516] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 15:02:08.754661 2019] [proxy:error] [pid 8052:tid 18516] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon May 20 15:02:08.754661 2019] [proxy:error] [pid 8052:tid 18516] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 08:18:18.996450 2019] [proxy:error] [pid 11004:tid 18680] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Mon Jul 08 08:18:18.996450 2019] [proxy:error] [pid 11004:tid 18680] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon Jul 08 08:18:18.996450 2019] [proxy_http:error] [pid 11004:tid 18680] [client 186.28.206.48:58452] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon Jul 08 08:18:18.996450 2019] [proxy:error] [pid 11004:tid 18680] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 08:18:20.993254 2019] [proxy:error] [pid 11004:tid 17476] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 08:18:20.993254 2019] [proxy:error] [pid 11004:tid 17476] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 10:58:25.106323 2019] [proxy:error] [pid 11004:tid 18608] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Mon Jul 08 10:58:25.106323 2019] [proxy:error] [pid 11004:tid 18608] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon Jul 08 10:58:25.106323 2019] [proxy_http:error] [pid 11004:tid 18608] [client 66.249.88.79:58242] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon Jul 08 10:58:25.106323 2019] [proxy:error] [pid 11004:tid 18608] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 16:45:39.916117 2019] [proxy:error] [pid 11004: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 192.168.175.44:80 (192.168.175.44) failed [Mon Jul 08 16:45:39.916117 2019] [proxy:error] [pid 11004:tid 18092] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon Jul 08 16:45:39.916117 2019] [proxy_http:error] [pid 11004:tid 18092] [client 66.249.88.79:49203] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon Jul 08 16:45:39.916117 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 18:00:46.968834 2019] [proxy:error] [pid 11004:tid 18364] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Mon Jul 08 18:00:46.968834 2019] [proxy:error] [pid 11004:tid 18364] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon Jul 08 18:00:46.968834 2019] [proxy_http:error] [pid 11004:tid 18364] [client 66.249.88.77:62661] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon Jul 08 18:00:46.968834 2019] [proxy:error] [pid 11004:tid 18364] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Jul 08 19:20:52.043473 2019] [proxy:error] [pid 11004:tid 17752] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Mon Jul 08 19:20:52.043473 2019] [proxy:error] [pid 11004:tid 17752] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Mon Jul 08 19:20:52.043473 2019] [proxy_http:error] [pid 11004:tid 17752] [client 66.249.88.79:49601] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Mon Jul 08 19:20:52.043473 2019] [proxy:error] [pid 11004:tid 17752] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 10:43:06.807465 2019] [proxy:error] [pid 11004:tid 18512] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 10:43:06.807465 2019] [proxy:error] [pid 11004:tid 18512] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 10:43:06.807465 2019] [proxy_http:error] [pid 11004:tid 18512] [client 66.249.88.75:62930] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 10:43:06.807465 2019] [proxy:error] [pid 11004:tid 18512] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:35.534520 2019] [proxy:error] [pid 11004:tid 18912] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:21:35.534520 2019] [proxy:error] [pid 11004:tid 18912] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:21:35.534520 2019] [proxy_http:error] [pid 11004:tid 18912] [client 201.245.192.253:65223] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:21:35.534520 2019] [proxy:error] [pid 11004:tid 18912] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:35.799720 2019] [proxy:error] [pid 11004:tid 18624] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:35.799720 2019] [proxy:error] [pid 11004:tid 18624] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:43.178533 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:43.178533 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:43.272133 2019] [proxy:error] [pid 11004:tid 18036] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:43.272133 2019] [proxy:error] [pid 11004:tid 18036] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.208135 2019] [proxy:error] [pid 11004:tid 18348] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.208135 2019] [proxy:error] [pid 11004:tid 18348] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.286135 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.286135 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.442135 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.442135 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.863336 2019] [proxy:error] [pid 11004:tid 18348] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:21:44.863336 2019] [proxy:error] [pid 11004:tid 18348] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:00.619364 2019] [proxy:error] [pid 11004:tid 18036] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:00.619364 2019] [proxy:error] [pid 11004:tid 18036] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:00.728564 2019] [proxy:error] [pid 11004:tid 18412] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:00.728564 2019] [proxy:error] [pid 11004:tid 18412] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:04.035770 2019] [proxy:error] [pid 11004:tid 18448] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:04.035770 2019] [proxy:error] [pid 11004:tid 18448] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:04.129370 2019] [proxy:error] [pid 11004:tid 18696] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:22:04.129370 2019] [proxy:error] [pid 11004:tid 18696] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:32.032768 2019] [proxy:error] [pid 11004:tid 18412] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:31:32.032768 2019] [proxy:error] [pid 11004:tid 18412] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:31:32.032768 2019] [proxy_http:error] [pid 11004:tid 18412] [client 201.245.192.253:65269] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:31:32.032768 2019] [proxy:error] [pid 11004:tid 18412] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:33.499170 2019] [proxy:error] [pid 11004:tid 18148] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:33.499170 2019] [proxy:error] [pid 11004:tid 18148] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.149576 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.149576 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.227577 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.227577 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.383577 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.383577 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.461577 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.461577 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.711177 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.711177 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.742378 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.742378 2019] [proxy:error] [pid 11004:tid 18092] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.851578 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:37.851578 2019] [proxy:error] [pid 11004:tid 18824] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:38.959180 2019] [proxy:error] [pid 11004:tid 17740] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:38.959180 2019] [proxy:error] [pid 11004:tid 17740] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:39.037180 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:31:39.037180 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:33:20.203357 2019] [proxy:error] [pid 11004:tid 18672] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:33:20.203357 2019] [proxy:error] [pid 11004:tid 18672] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:33:20.203357 2019] [proxy_http:error] [pid 11004:tid 18672] [client 201.245.192.253:65283] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:33:20.203357 2019] [proxy:error] [pid 11004:tid 18672] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:33:20.967759 2019] [proxy:error] [pid 11004:tid 17932] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:33:20.967759 2019] [proxy:error] [pid 11004:tid 17932] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:18.170765 2019] [proxy:error] [pid 11004:tid 18656] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:35:18.170765 2019] [proxy:error] [pid 11004:tid 18656] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:35:18.170765 2019] [proxy_http:error] [pid 11004:tid 18656] [client 201.245.192.253:65295] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:35:18.170765 2019] [proxy:error] [pid 11004:tid 18656] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:20.666769 2019] [proxy:error] [pid 11004:tid 18044] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:20.666769 2019] [proxy:error] [pid 11004:tid 18044] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:26.391979 2019] [proxy:error] [pid 11004:tid 18236] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:26.391979 2019] [proxy:error] [pid 11004:tid 18236] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:26.625980 2019] [proxy:error] [pid 11004:tid 18864] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:35:26.625980 2019] [proxy:error] [pid 11004:tid 18864] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:40:45.942940 2019] [proxy:error] [pid 11004:tid 18392] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:40:45.942940 2019] [proxy:error] [pid 11004:tid 18392] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:40:45.942940 2019] [proxy_http:error] [pid 11004:tid 18392] [client 201.245.192.253:65314] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:40:45.942940 2019] [proxy:error] [pid 11004:tid 18392] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:40:46.192541 2019] [proxy:error] [pid 11004:tid 18392] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:40:46.192541 2019] [proxy:error] [pid 11004:tid 18392] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:41:38.468233 2019] [proxy:error] [pid 11004:tid 17924] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:41:38.468233 2019] [proxy:error] [pid 11004:tid 17924] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:41:41.354238 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:41:41.354238 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:46:07.833906 2019] [proxy:error] [pid 11004:tid 18140] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 11:46:07.833906 2019] [proxy:error] [pid 11004:tid 18140] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 11:46:07.833906 2019] [proxy_http:error] [pid 11004:tid 18140] [client 190.130.66.83:20566] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 11:46:07.833906 2019] [proxy:error] [pid 11004:tid 18140] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:46:08.520307 2019] [proxy:error] [pid 11004:tid 18300] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 11:46:08.520307 2019] [proxy:error] [pid 11004:tid 18300] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:06:46.976282 2019] [proxy:error] [pid 11004:tid 17848] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 12:06:46.976282 2019] [proxy:error] [pid 11004:tid 17848] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 12:06:46.976282 2019] [proxy_http:error] [pid 11004:tid 17848] [client 201.245.192.253:65414] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 12:06:46.976282 2019] [proxy:error] [pid 11004:tid 17848] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:06:47.194683 2019] [proxy:error] [pid 11004:tid 17848] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:06:47.194683 2019] [proxy:error] [pid 11004:tid 17848] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:07:07.958319 2019] [proxy:error] [pid 11004:tid 18756] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:07:07.958319 2019] [proxy:error] [pid 11004:tid 18756] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:07:08.036319 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:07:08.036319 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:24:02.365701 2019] [proxy:error] [pid 11004:tid 18148] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 12:24:02.365701 2019] [proxy:error] [pid 11004:tid 18148] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 12:24:02.365701 2019] [proxy_http:error] [pid 11004:tid 18148] [client 201.245.192.253:65478] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 12:24:02.365701 2019] [proxy:error] [pid 11004:tid 18148] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:24:03.504503 2019] [proxy:error] [pid 11004:tid 18148] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 12:24:03.504503 2019] [proxy:error] [pid 11004:tid 18148] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 14:15:18.773827 2019] [proxy:error] [pid 11004:tid 18164] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:15:18.773827 2019] [proxy:error] [pid 11004:tid 18164] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 14:15:18.773827 2019] [proxy_http:error] [pid 11004:tid 18164] [client 201.245.192.253:49642] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 14:15:18.773827 2019] [proxy:error] [pid 11004:tid 18164] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 14:15:24.764238 2019] [proxy:error] [pid 11004:tid 18756] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 14:15:24.764238 2019] [proxy:error] [pid 11004:tid 18756] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 09 14:44:24.573894 2019] [proxy:error] [pid 11004:tid 17588] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:44:24.573894 2019] [proxy:error] [pid 11004:tid 17752] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:44:24.573894 2019] [proxy_http:error] [pid 11004:tid 17752] [client 201.245.192.253:53881] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 14:44:24.573894 2019] [proxy:error] [pid 11004:tid 17588] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 14:44:24.573894 2019] [proxy_http:error] [pid 11004:tid 17588] [client 201.245.192.253:53880] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 14:44:45.602731 2019] [proxy:error] [pid 11004:tid 17588] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:44:45.602731 2019] [proxy:error] [pid 11004:tid 17588] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 14:44:45.602731 2019] [proxy_http:error] [pid 11004:tid 17588] [client 201.245.192.253:53880] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 14:44:45.602731 2019] [proxy:error] [pid 11004:tid 17752] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:44:45.602731 2019] [proxy_http:error] [pid 11004:tid 17752] [client 201.245.192.253:53881] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 09 14:45:06.787568 2019] [proxy:error] [pid 11004:tid 17752] (OS 10060)A connection attempt failed because the connected party did not 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.44:80 (192.168.175.44) failed [Tue Jul 09 14:45:06.787568 2019] [proxy:error] [pid 11004:tid 17752] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 09 14:45:06.787568 2019] [proxy_http:error] [pid 11004:tid 17752] [client 201.245.192.253:53923] AH01114: HTTP: failed to make connection to backend: 192.168.175.44, referer: http://rmcab-ginventario.ambientebogota.gov.co/ [Tue Jul 09 14:45:06.787568 2019] [proxy:error] [pid 11004:tid 17752] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:31.147749 2019] [proxy:error] [pid 12024: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 192.168.175.44:80 (192.168.175.44) failed [Tue Jul 16 16:26:31.147749 2019] [proxy:error] [pid 12024:tid 17944] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Tue Jul 16 16:26:31.147749 2019] [proxy_http:error] [pid 12024:tid 17944] [client 201.245.192.253:55091] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Tue Jul 16 16:26:31.147749 2019] [proxy:error] [pid 12024:tid 17944] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:35.297356 2019] [proxy:error] [pid 12024:tid 18908] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:35.297356 2019] [proxy:error] [pid 12024:tid 18908] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:36.404958 2019] [proxy:error] [pid 12024:tid 18468] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:36.404958 2019] [proxy:error] [pid 12024:tid 18468] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:37.746560 2019] [proxy:error] [pid 12024:tid 18056] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:37.746560 2019] [proxy:error] [pid 12024:tid 18056] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:39.727764 2019] [proxy:error] [pid 12024:tid 17640] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:39.727764 2019] [proxy:error] [pid 12024:tid 17640] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:59.929799 2019] [proxy:error] [pid 12024:tid 18056] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:26:59.929799 2019] [proxy:error] [pid 12024:tid 18056] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:27:02.347803 2019] [proxy:error] [pid 12024:tid 17928] AH00940: HTTP: disabled connection for (192.168.175.44) [Tue Jul 16 16:27:02.347803 2019] [proxy:error] [pid 12024:tid 17928] AH00940: HTTP: disabled connection for (192.168.175.44) [Wed Oct 07 07:09:22.534276 2020] [proxy:error] [pid 11612:tid 21108] (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.44:80 (192.168.175.44) failed [Wed Oct 07 07:09:22.549876 2020] [proxy:error] [pid 11612:tid 21108] AH00959: ap_proxy_connect_backend disabling worker for (192.168.175.44) for 60s [Wed Oct 07 07:09:22.549876 2020] [proxy_http:error] [pid 11612:tid 21108] [client 181.57.107.221:58888] AH01114: HTTP: failed to make connection to backend: 192.168.175.44 [Wed Oct 07 07:09:22.549876 2020] [proxy:error] [pid 11612:tid 21108] AH00940: HTTP: disabled connection for (192.168.175.44) [Wed Oct 07 07:09:23.314277 2020] [proxy:error] [pid 11612:tid 21108] AH00940: HTTP: disabled connection for (192.168.175.44) [Wed Oct 07 07:09:23.314277 2020] [proxy:error] [pid 11612:tid 21108] AH00940: HTTP: disabled connection for (192.168.175.44) [Mon Apr 12 11:16:15.484584 2021] [proxy_http:error] [pid 5508:tid 20244] (20014)Internal error: [client 186.30.31.42:27708] AH01102: error reading status line from remote server 192.168.175.44:80, referer: http://rmcab-ginventario.ambientebogota.gov.co/ [Mon Apr 12 11:16:15.500184 2021] [proxy_http:error] [pid 5508:tid 21044] (20014)Internal error: [client 186.30.31.42:9112] AH01102: error reading status line from remote server 192.168.175.44:80, referer: http://rmcab-ginventario.ambientebogota.gov.co/ [Mon Apr 12 11:16:15.500184 2021] [proxy:error] [pid 5508:tid 21044] [client 186.30.31.42:9112] AH00898: Error reading from remote server returned by /icons/openlogo-75.png, referer: http://rmcab-ginventario.ambientebogota.gov.co/ |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0468 ]-- |