On 11/05/2013 2:26 AM, "jerome.m" wrote:
>
> Has anyone ever experience an HTTPD (mpm worker) just suddenly stop
accepting connection?
>
> I did a telnet on the port it was listening from the local machine and
its not responding..
>
> the fix was stop it and then start it...
>
> i looked at the er
On 5/10/2013 11:26 AM, jerome.m wrote:
> Has anyone ever experience an HTTPD (mpm worker) just suddenly stop
> accepting connection?
>
> I did a telnet on the port it was listening from the local machine and
> its not responding..
>
> the fix was stop it and then start it...
>
> i looked at the err
Hi,
have you done a tcpdump? Might be that the connections are filtered by a
firewall. Could also be a problem with DNS. Are you able to connect
locally (to localhost) using an IP adress only? Does the access log tell
you anything?
bye
David
Am 10.05.2013 18:26, schrieb jerome.m:
Has anyon
Has anyone ever experience an HTTPD (mpm worker) just suddenly stop
accepting connection?
I did a telnet on the port it was listening from the local machine and its
not responding..
the fix was stop it and then start it...
i looked at the error logs and found nothing..
the load on the 16 core b
Hi List,
I'm using Apache 2.2.11 on CentOS, arch - x86 as write-through subversion
proxy.
Server version: Apache/2.2.11 (Unix)
Server built: Apr 10 2010 16:04:54
I have started getting the following error for last few days, which I
really find strange :
(20014)Internal error: proxy: error re
Daniel,In Apache 2.4 a previously third-party module mod_proxy_http (
http://httpd.apache.org/docs/2.4/mod/mod_proxy_html.html ) was included. The
original module: http://apache.webthing.com/mod_proxy_html/ presumably works
with Apache 2.2. This module seems to be focused on modifying URL's. I'v
