Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED8C8C754 for ; Mon, 24 Jun 2013 15:52:14 +0000 (UTC) Received: (qmail 61812 invoked by uid 500); 24 Jun 2013 15:52:08 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 61768 invoked by uid 500); 24 Jun 2013 15:52:08 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 61670 invoked by uid 99); 24 Jun 2013 15:52:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jun 2013 15:52:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ephemeric@gmail.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jun 2013 15:52:02 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so11023406pbb.8 for ; Mon, 24 Jun 2013 08:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0z2mP+b5wzlbbCCpnSUHZtvivdjUHsWAgXw6Dl0UDaY=; b=ZLD86lyDxE9USeSgwXEu1UJ7GXsU4H8owdku3Ck3TWj3Gzxt767CMxWej00KKa9z3v FpBzMhzO/ovwqv12KQU2wpz0j0S1MtuVyRZySj+4tDmf4sxjjbOCUIMxOXUEXfyzLJ3D 0707yjVZHCBLuqHU3Y41vUXf5W/yZdum0UjdeB4h/pc/AlWrKNfhlSJiiTt31BZqtkQn +QFasZan5VpeKBClBiP2L7VbSaOdy66hOh/ZEodMdjmF+zGE2TSIRqlskXiYxKfOIItr sK8Gw65VVxREETZT3bTfh6S34U+7X7RpJC0c4+b3u3L5DUb92LD+RqlfYe2t5BW5XSeC p/Lw== MIME-Version: 1.0 X-Received: by 10.68.252.67 with SMTP id zq3mr24521085pbc.66.1372089101461; Mon, 24 Jun 2013 08:51:41 -0700 (PDT) Received: by 10.66.221.68 with HTTP; Mon, 24 Jun 2013 08:51:41 -0700 (PDT) In-Reply-To: References: Date: Mon, 24 Jun 2013 17:51:41 +0200 Message-ID: From: Robert Gabriel To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=047d7b2e0a697f4da604dfe8635b X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Mod_proxy Slow After a Week --047d7b2e0a697f4da604dfe8635b Content-Type: text/plain; charset=ISO-8859-1 On 24 June 2013 17:49, David Guerra wrote: > You are receiving 304's? > That doesn't make sense. Maybe 504's which many times will point to a > load issue on the backend server. > > > On Mon, Jun 24, 2013 at 9:03 AM, Robert Gabriel wrote: > >> Hello all, >> >> We have: >> >> Apache 2.2.3 >> CentOS 5.5 x86_64 >> Splunk 5.0.2 >> >> I only know the basics but Apache has been serving us very well with the >> below config >> >> and only after about a week did pages refresh very slowly, up to a minute >> to reload >> >> sometimes. >> >> I tailed both httpd and splunkd logs and saw a consistent delay of 30s >> between proxy >> >> and origin server (both on same host) along with plenty of 304s, followed >> by what >> >> appeared to be some timeout and then slowly the 200s started coming back >> in. >> >> A restart of httpd cleared up the issue. >> >> I'm lost, please help. >> >> Could this be a caching problem? >> >> Thank you. >> >> >> SSLEngine on >> SSLCertificateFile /etc/httpd/conf/server.crt >> SSLCertificateKeyFile /etc/httpd/conf/server.key >> SSLProxyEngine On >> SSLCACertificateFile /etc/httpd/conf/gsoc.pem >> SSLProtocol all -SSLv2 >> SSLVerifyClient require >> SSLVerifyDepth 1 >> SSLOptions +StrictRequire >> >> RequestHeader set X-Remote-User %{REMOTE_USER}s >> >> ServerName dashboards.gsoc.co.za:443 >> ServerAdmin admin@gsoc.co.za >> DocumentRoot /srv/http/gdf/ >> CustomLog /var/log/httpd/gdf/access combined >> ErrorLog /var/log/httpd/gdf/error >> LogLevel debug >> >> ProxyRequests Off >> ProxyPreserveHost Off >> ProxyPass /gdf https://172.20.67.2:8000/gdf >> ProxyPassReverse /gdf https://172.20.67.2:8000/gdf >> >> >> SSLRequireSSL >> AllowOverride none >> AuthName "GDF" >> AuthType Basic >> AuthDigestProvider file >> AuthUserFile /etc/httpd/conf/passwd >> Require ssl-verify-client >> Require valid-user >> Require ssl >> Satisfy All >> >> >> >> SSLRequireSSL >> AuthName "GDF" >> AuthType Basic >> AuthDigestProvider file >> AuthUserFile /etc/httpd/conf/passwd >> Require ssl-verify-client >> Require valid-user >> Require ssl >> Satisfy All >> >> >> >> > > > -- > Take Care, > > David Guerra > http://frustratedtech.com/ > 304s for sure, no doubt. --047d7b2e0a697f4da604dfe8635b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 24 June 2013 17:49, David Guerra <= imdavidguerra@= gmail.com> wrote:
You are receiving 304's= ?
That doesn't make sense. =A0Maybe 504's which many times will= point to a load issue on the backend server.


On Mon, Jun 24, 2013 at 9:03 AM, Robert Gabriel <ephemeric@gmail.com= > wrote:
Hello all,

We have:

Apache 2.2.3
CentO= S 5.5 x86_64
Splunk 5.0.2

I only know the basic= s but Apache has been serving us very well with the below config

and only after about a week did pages refresh very slowly, up to = a minute to reload

sometimes.

I tailed both httpd and = splunkd logs and saw a consistent delay of 30s between proxy

and origin server (both on same host) along with plenty of 304s, followed b= y what

appeared to be some timeout and then slowly the 200s started= coming back in.

A restart of httpd cleared up the issue.

I'm lost, please help.

Could this be a cach= ing problem?

Thank you.
<VirtualHost *:4=
43>
        SSLEngine on
        SSLCertificateFile      /etc/httpd/conf/server.crt
        SSLCertificateKeyFile   /etc/httpd/conf/server.key
	SSLProxyEngine On
	SSLCACertificateFile	/etc/httpd/conf/gsoc.pem
	SSLProtocol all -SSLv2
	SSLVerifyClient require
	SSLVerifyDepth 1
	SSLOptions +StrictRequire

	RequestHeader set X-Remote-User %{REMOTE_USER}s

        ServerName      dashboards.gsoc.co.za:443
	ServerAdmin	admin@gs=
oc.co.za
        DocumentRoot    /srv/http/gdf/
        CustomLog       /var/log/httpd/gdf/access combined
        ErrorLog        /var/log/httpd/gdf/error
	LogLevel	debug

	ProxyRequests Off
	ProxyPreserveHost Off
	ProxyPass /gdf =
https://172.20.67.2:8000/gdf
	ProxyPassReverse /gdf https://172.20.67.2:8000/gdf

       <Directory />
		SSLRequireSSL
        	AllowOverride none
		AuthName "GDF"
		AuthType Basic
		AuthDigestProvider file
		AuthUserFile /etc/httpd/conf/passwd
		Require ssl-verify-client
		Require valid-user
		Require ssl
		Satisfy All
        </Directory>

        <Location /gdf>
		SSLRequireSSL
		AuthName "GDF"
		AuthType Basic
		AuthDigestProvider file
		AuthUserFile /etc/httpd/conf/passwd
		Require ssl-verify-client
		Require valid-user
		Require ssl
		Satisfy All
        </Location>
</VirtualHost>



--
Take Care,<= div>
David Guerra
304s for sure, no d= oubt.
--047d7b2e0a697f4da604dfe8635b--