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 5.02 GB of 239.26 GB (2.1%)
Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ]
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     error.2018.03.09.log (33.48 KB)      -rw-rw-rw-

[Fri Mar 09 01:07:50.497543 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 01:11:01.269455 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 01:25:26.183925 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 02:09:39.815704 2018] [proxy:error] [pid 5704:tid 16864] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Mar 09 02:09:39.815704 2018] [proxy:error] [pid 5704:tid 16864] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Mar 09 02:09:39.815704 2018] [proxy_http:error] [pid 5704:tid 16864] [client 152.61.128.50:37394] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Mar 09 02:09:40.065718 2018] [proxy:error] [pid 5704:tid 16864] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 09 02:09:40.313732 2018] [proxy:error] [pid 5704:tid 16864] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 09 02:43:18.567170 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 02:57:47.128849 2018] [core:error] [pid 5704:tid 16352] (20024)The given path is misformatted or contained invalid characters: [client 188.165.233.34:56462] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 03:16:07.022759 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 03:34:42.177542 2018] [proxy:error] [pid 5704:tid 17076] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.51:8399 (172.22.1.51) failed
[Fri Mar 09 03:34:42.177542 2018] [proxy:error] [pid 5704:tid 17076] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.51) for 60s
[Fri Mar 09 03:34:42.177542 2018] [proxy_http:error] [pid 5704:tid 17076] [client 152.61.192.232:57948] AH01114: HTTP: failed to make connection to backend: 172.22.1.51
[Fri Mar 09 03:34:42.464559 2018] [proxy:error] [pid 5704:tid 17076] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 09 03:34:42.716573 2018] [proxy:error] [pid 5704:tid 17076] AH00940: HTTP: disabled connection for (172.22.1.51)
[Fri Mar 09 04:26:22.912894 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 04:31:03.554946 2018] [proxy:error] [pid 5704: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.31:80 (172.22.1.31) failed
[Fri Mar 09 04:31:03.554946 2018] [proxy:error] [pid 5704:tid 17036] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 04:31:03.554946 2018] [proxy_http:error] [pid 5704:tid 17036] [client 40.77.167.81:9112] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 04:45:23.973159 2018] [core:error] [pid 5704:tid 17332] (20024)The given path is misformatted or contained invalid characters: [client 207.46.13.42:3150] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 05:27:51.850889 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 07:10:23.262730 2018] [core:error] [pid 5704:tid 17464] (20024)The given path is misformatted or contained invalid characters: [client 207.182.140.210:51326] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 07:35:37.909363 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 07:47:55.754565 2018] [proxy:error] [pid 5704:tid 17544] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 07:47:55.754565 2018] [proxy:error] [pid 5704:tid 17544] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 07:47:55.754565 2018] [proxy_http:error] [pid 5704:tid 17544] [client 186.154.52.113:14377] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 07:48:17.918833 2018] [proxy:error] [pid 5704:tid 17544] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 07:51:25.754577 2018] [proxy:error] [pid 5704:tid 17704] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 07:51:25.754577 2018] [proxy:error] [pid 5704:tid 17704] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 07:51:25.754577 2018] [proxy_http:error] [pid 5704:tid 17704] [client 186.154.52.113:14769] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 08:05:22.077412 2018] [proxy:error] [pid 5704:tid 17324] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 08:05:22.077412 2018] [proxy:error] [pid 5704:tid 17324] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 08:05:22.077412 2018] [proxy_http:error] [pid 5704:tid 17324] [client 66.249.88.33:55913] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 08:38:08.476883 2018] [proxy:error] [pid 5704:tid 17044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 08:38:08.476883 2018] [proxy:error] [pid 5704:tid 17044] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 08:38:08.476883 2018] [proxy_http:error] [pid 5704:tid 17044] [client 186.154.52.113:17501] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 08:39:43.954344 2018] [proxy:error] [pid 5704:tid 17076] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 08:39:43.954344 2018] [proxy:error] [pid 5704:tid 17076] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 08:39:43.954344 2018] [proxy_http:error] [pid 5704:tid 17076] [client 172.22.2.1:32971] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 08:46:50.505741 2018] [proxy:error] [pid 5704:tid 17168] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 08:46:50.505741 2018] [proxy:error] [pid 5704:tid 17168] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 08:46:50.505741 2018] [proxy_http:error] [pid 5704:tid 17168] [client 201.245.192.253:50387] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 08:46:50.642749 2018] [proxy:error] [pid 5704:tid 17168] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 08:54:35.675348 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 08:54:57.477595 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 09:01:45.576937 2018] [proxy:error] [pid 5704:tid 17988] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 09:01:45.576937 2018] [proxy:error] [pid 5704:tid 17988] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 09:01:45.576937 2018] [proxy_http:error] [pid 5704:tid 17988] [client 201.245.192.253:28103] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 09:23:58.156156 2018] [proxy:error] [pid 5704:tid 16604] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 09:23:58.156156 2018] [proxy:error] [pid 5704:tid 16604] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 09:23:58.156156 2018] [proxy_http:error] [pid 5704:tid 16604] [client 201.245.192.253:49798] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 09:43:00.081470 2018] [proxy:error] [pid 5704:tid 16356] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 09:43:00.081470 2018] [proxy:error] [pid 5704:tid 16356] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 09:43:00.081470 2018] [proxy_http:error] [pid 5704:tid 16356] [client 66.249.88.62:64389] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 09:50:48.894285 2018] [proxy:error] [pid 5704:tid 16796] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 09:50:48.894285 2018] [proxy:error] [pid 5704:tid 16796] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 09:50:48.894285 2018] [proxy_http:error] [pid 5704:tid 16796] [client 201.245.192.253:63925] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 09:51:25.621385 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 09:56:02.641230 2018] [core:error] [pid 5704:tid 16844] (20024)The given path is misformatted or contained invalid characters: [client 190.24.136.210:65522] AH00127: Cannot map GET /.../Lista%20de%20Chequeo%20Informe%20Mov%20AU.xls HTTP/1.1 to file, referer: http://guiatramitesyservicios.bogota.gov.co/tramite_entidad/tramites-establecimientos-almacenan-distribuyen-combustibles-liquidos-y-movilicen-aceites-usados/
[Fri Mar 09 10:08:48.626042 2018] [proxy:error] [pid 5704:tid 16464] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 10:08:48.626042 2018] [proxy:error] [pid 5704:tid 16464] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 10:08:48.626042 2018] [proxy_http:error] [pid 5704:tid 16464] [client 201.245.192.253:49849] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 10:09:33.150589 2018] [proxy:error] [pid 5704:tid 17960] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 10:09:36.428776 2018] [proxy:error] [pid 5704:tid 15980] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 10:34:07.817935 2018] [proxy_http:error] [pid 5704:tid 16376] (20014)Internal error: [client 186.155.66.157:29911] AH01102: error reading status line from remote server 172.22.1.43:80, referer: http://190.27.245.106/desprendiblespago/controlador
[Fri Mar 09 10:51:07.384251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:51:07.385251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:51:07.385251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:51:07.385251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:51:07.385251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:51:07.386251 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 10:58:29.820556 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 11:35:27.711413 2018] [proxy:error] [pid 5704:tid 16964] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 11:35:27.711413 2018] [proxy:error] [pid 5704:tid 16964] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 11:35:27.711413 2018] [proxy_http:error] [pid 5704:tid 16964] [client 201.245.192.253:59182] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 11:35:27.872422 2018] [proxy:error] [pid 5704:tid 16964] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 11:39:14.074360 2018] [proxy:error] [pid 5704:tid 17928] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 11:39:14.074360 2018] [proxy:error] [pid 5704:tid 17928] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 11:39:14.074360 2018] [proxy_http:error] [pid 5704:tid 17928] [client 201.245.192.253:51147] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 11:47:28.021612 2018] [proxy:error] [pid 5704:tid 16552] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 11:47:28.021612 2018] [proxy:error] [pid 5704:tid 16552] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 11:47:28.021612 2018] [proxy_http:error] [pid 5704:tid 16552] [client 190.26.126.120:51684] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 11:47:29.706708 2018] [proxy:error] [pid 5704:tid 16332] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 11:47:29.706708 2018] [proxy_http:error] [pid 5704:tid 16332] [client 190.26.126.120:51685] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 11:50:38.045481 2018] [proxy:error] [pid 5704:tid 17300] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 11:50:38.045481 2018] [proxy:error] [pid 5704:tid 17300] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 11:50:38.045481 2018] [proxy_http:error] [pid 5704:tid 17300] [client 201.245.192.253:56379] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 11:51:39.399990 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 12:05:37.307916 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 12:22:33.875060 2018] [proxy:error] [pid 5704:tid 17028] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 12:22:33.875060 2018] [proxy:error] [pid 5704:tid 17028] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 12:22:33.875060 2018] [proxy_http:error] [pid 5704:tid 17028] [client 201.245.192.253:60712] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 12:37:41.180955 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 12:38:49.327853 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 12:40:10.225480 2018] [proxy:error] [pid 5704:tid 17068] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 12:40:10.225480 2018] [proxy:error] [pid 5704:tid 17068] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 12:40:10.225480 2018] [proxy_http:error] [pid 5704:tid 17068] [client 190.157.197.252:57183] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 13:30:01.594576 2018] [core:error] [pid 5704:tid 17208] (20024)The given path is misformatted or contained invalid characters: [client 54.227.201.85:29860] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 13:43:28.453726 2018] [core:error] [pid 5704:tid 16860] (20024)The given path is misformatted or contained invalid characters: [client 34.229.72.89:36378] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 13:48:29.579949 2018] [proxy:error] [pid 5704:tid 16452] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 13:48:29.579949 2018] [proxy:error] [pid 5704:tid 16452] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 13:48:29.579949 2018] [proxy_http:error] [pid 5704:tid 16452] [client 170.254.229.44:51475] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W&
[Fri Mar 09 13:48:44.390796 2018] [proxy:error] [pid 5704:tid 17028] AH00940: HTTP: disabled connection for (172.22.1.31)
[Fri Mar 09 13:51:15.080415 2018] [proxy:error] [pid 5704:tid 17060] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 13:51:15.080415 2018] [proxy:error] [pid 5704:tid 17060] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 13:51:15.080415 2018] [proxy_http:error] [pid 5704:tid 17060] [client 170.254.229.44:51605] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W&
[Fri Mar 09 13:54:35.658888 2018] [proxy:error] [pid 5704:tid 17524] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 13:54:35.658888 2018] [proxy:error] [pid 5704:tid 17524] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 13:54:35.658888 2018] [proxy_http:error] [pid 5704:tid 17524] [client 170.254.229.44:51644] AH01114: HTTP: failed to make connection to backend: 172.22.1.31, referer: http://www.ambientebogota.gov.co/c/iframe/proxy?p_l_id=3791540&p_p_id=48_INSTANCE_cn9W&
[Fri Mar 09 14:15:13.194671 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 14:19:47.108338 2018] [proxy:error] [pid 5704: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 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 14:19:47.108338 2018] [proxy:error] [pid 5704:tid 17932] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 14:19:47.108338 2018] [proxy_http:error] [pid 5704:tid 17932] [client 186.154.52.113:24217] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:34:41.792419 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 15:35:14.813308 2018] [proxy:error] [pid 5704:tid 17484] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:35:14.813308 2018] [proxy:error] [pid 5704:tid 17484] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 15:35:14.813308 2018] [proxy_http:error] [pid 5704:tid 17484] [client 66.249.88.75:39274] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:35:20.125612 2018] [proxy:error] [pid 5704:tid 16044] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:35:20.125612 2018] [proxy_http:error] [pid 5704:tid 16044] [client 181.61.173.226:49048] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:35:47.283165 2018] [proxy:error] [pid 5704:tid 17544] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:35:47.283165 2018] [proxy:error] [pid 5704:tid 17544] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 15:35:47.283165 2018] [proxy_http:error] [pid 5704:tid 17544] [client 66.249.88.75:56346] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:35:52.382457 2018] [proxy:error] [pid 5704:tid 16828] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:35:52.382457 2018] [proxy_http:error] [pid 5704:tid 16828] [client 181.61.173.226:49055] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:35:59.812882 2018] [proxy:error] [pid 5704:tid 16740] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:35:59.812882 2018] [proxy_http:error] [pid 5704:tid 16740] [client 66.249.88.73:57717] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 15:36:05.126185 2018] [proxy:error] [pid 5704:tid 15980] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 15:36:05.126185 2018] [proxy_http:error] [pid 5704:tid 15980] [client 181.61.173.226:49067] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 16:08:59.222097 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 16:09:02.729298 2018] [core:error] [pid 5704:tid 18000] (20024)The given path is misformatted or contained invalid characters: [client 34.229.72.89:6986] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 16:11:19.086097 2018] [proxy:error] [pid 5704:tid 16456] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 16:11:19.086097 2018] [proxy:error] [pid 5704:tid 16456] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 16:11:19.086097 2018] [proxy_http:error] [pid 5704:tid 16456] [client 201.245.192.253:54648] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 16:28:24.288735 2018] [proxy:error] [pid 5704:tid 16596] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 16:28:24.288735 2018] [proxy:error] [pid 5704:tid 16596] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 16:28:24.288735 2018] [proxy_http:error] [pid 5704:tid 16596] [client 66.249.88.73:53241] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 16:33:45.891130 2018] [proxy:error] [pid 5704:tid 17380] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 16:33:45.891130 2018] [proxy:error] [pid 5704:tid 17380] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 16:33:45.891130 2018] [proxy_http:error] [pid 5704:tid 17380] [client 186.154.52.113:15631] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 16:37:10.068808 2018] [proxy:error] [pid 5704:tid 16916] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 16:37:10.068808 2018] [proxy:error] [pid 5704:tid 16916] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 16:37:10.068808 2018] [proxy_http:error] [pid 5704:tid 16916] [client 181.49.77.189:14830] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 16:44:18.544316 2018] [proxy:error] [pid 5704:tid 17748] (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
[Fri Mar 09 16:44:18.544316 2018] [proxy:error] [pid 5704:tid 17748] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.32) for 60s
[Fri Mar 09 16:44:18.544316 2018] [proxy_http:error] [pid 5704:tid 17748] [client 190.146.195.31:60426] 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
[Fri Mar 09 16:56:14.581271 2018] [proxy:error] [pid 5704:tid 16820] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 16:56:14.581271 2018] [proxy:error] [pid 5704:tid 16820] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 16:56:14.581271 2018] [proxy_http:error] [pid 5704:tid 16820] [client 201.245.192.253:57187] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 17:17:02.087624 2018] [proxy:error] [pid 5704:tid 17852] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : AH00957: HTTP: attempt to connect to 172.22.1.31:80 (172.22.1.31) failed
[Fri Mar 09 17:17:02.087624 2018] [proxy:error] [pid 5704:tid 17852] AH00959: ap_proxy_connect_backend disabling worker for (172.22.1.31) for 60s
[Fri Mar 09 17:17:02.087624 2018] [proxy_http:error] [pid 5704:tid 17852] [client 201.245.192.253:61333] AH01114: HTTP: failed to make connection to backend: 172.22.1.31
[Fri Mar 09 19:15:10.674068 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 19:31:51.326302 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 20:12:30.815833 2018] [core:error] [pid 5704:tid 18064] (20024)The given path is misformatted or contained invalid characters: [client 138.197.3.255:60250] AH00127: Cannot map GET /galeria/carrusel/Carrusel/jquery-ui-%0A%0A1.8.13.custom.min.js HTTP/1.1 to file
[Fri Mar 09 20:16:04.839074 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 20:49:02.190172 2018] [core:error] [pid 5704:tid 17844] (20024)The given path is misformatted or contained invalid characters: [client 54.86.16.196:56682] AH00127: Cannot map GET /www.ambientebogota.gov.co:81/ HTTP/1.1 to file
[Fri Mar 09 20:53:35.086781 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Fri Mar 09 23:14:59.684072 2018] [ssl:error] [pid 5704:tid 16184] AH02032: Hostname 190.27.245.106 provided via SNI and hostname dama.gov.co provided via HTTP are different
[Fri Mar 09 23:57:01.265298 2018] [mpm_winnt:warn] [pid 5704:tid 19184] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.