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 266A3D66F for ; Sun, 29 Jul 2012 21:50:40 +0000 (UTC) Received: (qmail 17943 invoked by uid 500); 29 Jul 2012 21:50:37 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 17901 invoked by uid 500); 29 Jul 2012 21:50:37 -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 17892 invoked by uid 99); 29 Jul 2012 21:50:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jul 2012 21:50:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paulojjs@gmail.com designates 209.85.214.173 as permitted sender) Received: from [209.85.214.173] (HELO mail-ob0-f173.google.com) (209.85.214.173) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jul 2012 21:50:31 +0000 Received: by obbta14 with SMTP id ta14so10700441obb.18 for ; Sun, 29 Jul 2012 14:50:10 -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=oeuxqwhOXIi77JOWsANv1jmGp7BJYSbP7NmdtiQ/ET8=; b=ugYrUr/AX/QaiIPKhDJO7JC2Va9BYh+uZk8rmDe/VU3i79CjjTeMHf54hQJePDsA20 jicG54uU163OV5tjRi3hXBpWwI8l8A4+UZ9GkbcYkCAA42+YciGTufKFVxiokY3YoYE5 TD3sXhP/z9V3XJRwz7WA+FxWoQ4L5d0owukzxxrZ/FZLGqgx9/IbRJPwDXyoH+ZasTnv FfepS8mSrDknt8KEljUJVSF6UXqTr2DxpMhRt+rYZdBoEllHJz39FRgGdY9Qtm0n3z84 lDr9tEOiMPnQeSieoi7oqYPT3PRfh1vWKgyNkaX6A+xW45gQTNjNmxk0Tp/XXbpTKNih AjsA== MIME-Version: 1.0 Received: by 10.182.226.41 with SMTP id rp9mr14285622obc.22.1343598609891; Sun, 29 Jul 2012 14:50:09 -0700 (PDT) Received: by 10.76.20.242 with HTTP; Sun, 29 Jul 2012 14:50:09 -0700 (PDT) In-Reply-To: <4F57205D.7020207@eris.qinetiq.com> References: <4F57205D.7020207@eris.qinetiq.com> Date: Sun, 29 Jul 2012 22:50:09 +0100 Message-ID: From: Paulo Silva To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=f46d04446ab3dd000804c5feed0d Subject: Re: [users@httpd] mod_proxy_balancer error state causes --f46d04446ab3dd000804c5feed0d Content-Type: text/plain; charset=ISO-8859-1 Hi, Anyone knows if this is documented somewhere? Thanks 2012/3/7 Mark Watts > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > When using mod_proxy_balancer there are several 'events' that will > place a given worker into the Err state for "retry=" seconds. > > These 'events' don't all appear to be explicitly documented in once place. > > Clearly any HTTP response code matching the list given in > "failonstatus=" as well as any request exceeding "timeout=" seconds > will place the worker into the Err state. > > With this in mind, I have a load balancer which balances across two > IIS servers. I do not have "failonstatus=" set so I assumed that only > timeouts would cause workers to go into Err. > However, when one of the IIS boxes returns a 500, this also seems to > trigger the Err state. > > Two questions: > > 1. Is this expected behaviour? > 2. If so, do any other HTTP response codes trigger the Err state as well? > > Regards, > > Mark. > > - -- > Mark Watts BSc RHCE > Senior Systems Engineer, MSS Secure Managed Hosting > www.QinetiQ.com > QinetiQ - Delivering customer-focused solutions > GPG Key: http://www.linux-corner.info/mwatts.gpg > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk9XIF0ACgkQBn4EFUVUIO0chQCePSW3IaKMt31b+sYw8EfJDMx+ > 1ZkAoOzxWiMMRTCwO0lAref+m5mXqSHL > =Fknx > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > -- Paulo Silva --f46d04446ab3dd000804c5feed0d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Anyone knows if this is documented somewhere?
<= div>
Thanks

2012/3/7 Mark W= atts <m.watts@eris.qinetiq.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


When using mod_proxy_balancer there are several 'events' that will<= br> place a given worker into the Err state for "retry=3D" seconds.
These 'events' don't all appear to be explicitly documented in = once place.

Clearly any HTTP response code matching the list given in
"failonstatus=3D" as well as any request exceeding "timeout= =3D" seconds
will place the worker into the Err state.

With this in mind, I have a load balancer which balances across two
IIS servers. I do not have "failonstatus=3D" set so I assumed tha= t only
timeouts would cause workers to go into Err.
However, when one of the IIS boxes returns a 500, this also seems to
trigger the Err state.

Two questions:

1. Is this expected behaviour?
2. If so, do any other HTTP response codes trigger the Err state as well?
Regards,

Mark.

- --
Mark Watts BSc RHCE
Senior Systems Engineer, MSS Secure Managed Hosting
www.QinetiQ.com QinetiQ - Delivering customer-focused solutions
GPG Key: http://www.linux-corner.info/mwatts.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9XIF0ACgkQBn4EFUVUIO0chQCePSW3IaKMt31b+sYw8EfJDMx+
1ZkAoOzxWiMMRTCwO0lAref+m5mXqSHL
=3DFknx
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




--
Paulo Silva = <paulojjs@gmail.com>
--f46d04446ab3dd000804c5feed0d--