[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-users
Subject:    Re: [users@httpd] BalancerMember returns 500 internal server error before failover
From:       Wayne W <waynemailinglists () gmail ! com>
Date:       2016-04-20 14:42:59
Message-ID: CAO9-Pr5L4my-Co=U3KP78yyaSVoL77u0cjOPKphDFOhvMyBhJw () mail ! gmail ! com
[Download RAW message or body]

It would appear from this post:

http://apache-http-server.18135.x6.nabble.com/Help-regarding-mod-proxy-balancer-failover-and-failonstatus-td4998183.html


that failover (with no error message) will only occur when a connection to
the instance cannot be made. I suppose as the instance was shutting down it
returned/cut the current connection the proxy and hence the internal server
error message.



On Wed, Apr 20, 2016 at 3:17 PM, Wayne W <waynemailinglists@gmail.com>
wrote:

> I did see the ping parameter for the Balancemember element could be used
> to test the connection - should we be using this? I'm worried about more
> load on the tomcat instances though using this.
> 
> On Wed, Apr 20, 2016 at 3:07 PM, Wayne W <waynemailinglists@gmail.com>
> wrote:
> 
> > Hi Jim,
> > 
> > I did't know that - is there any documentation around this? what should I
> > search for?
> > 
> > So are you saying what I'm experiencing is normal?
> > 
> > On Wed, Apr 20, 2016 at 2:05 PM, Jim Jagielski <jim@jagunet.com> wrote:
> > 
> > > Upgrading to 2.4.20 allow you to disable the one node dynamically
> > > on the httpd side and then bring down the node.
> > > > On Apr 20, 2016, at 8:10 AM, Wayne W <waynemailinglists@gmail.com>
> > > wrote:
> > > > 
> > > > Hi,
> > > > 
> > > > I'm seeing that with Apache 2.4.12 on Solaris when setup with
> > > mod_proxy to 2 tomcat instances when we bring down 1 node for maintenance
> > > the first client to try and access that node gets a Internal Server Error.
> > > Any requests after that (and for other sessions) are balanced correctly
> > > onto the other node.
> > > > 
> > > > Is this normal?
> > > > Is there a way for it to just balance over to the other node without
> > > returning the error?
> > > > 
> > > > My conf:
> > > > <VirtualHost *:80>
> > > > ServerName
> > > > somedomain.com
> > > > 
> > > > ProxyPass /share
> > > > http://127.0.0.1:8181/share
> > > > 
> > > > 
> > > > ProxyPass / balancer://cluster/ stickysession=JSESSIONID
> > > nofailover=Off
> > > > 
> > > > # define the balancer, with http and/or ajp connections
> > > > <Proxy balancer://cluster/>
> > > > Order allow,deny
> > > > Allow from all
> > > > BalancerMember ajp://
> > > > 127.0.0.1:8010
> > > > route=g1
> > > > BalancerMember ajp://
> > > > 127.0.0.1:8011
> > > > route=g2
> > > > </Proxy>
> > > > </VirtualHost>
> > > > 
> > > > 
> > > > I see in the apache logs the following:
> > > > 
> > > > Wed Apr 20 11:04:11.739700 2016] [proxy_ajp:error] [pid 58313] [client
> > > 10.12.32.251:56869] AH00992: ajp_read_header: ajp_ilink_receive failed,
> > > referer: https://example.com
> > > > [Wed Apr 20 11:04:11.739713 2016] [proxy_ajp:error] [pid 58313]
> > > (120006)APR does not understand this error code: [client
> > > 10.12.32.251:56869] AH00878: read response failed from 127.0.0.1:8010
> > > (127.0.0.1), referer: http://example.com
> > > > [
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> > > 
> > > 
> > 
> 


[Attachment #3 (text/html)]

<div dir="ltr">It would appear from this post:<div><br></div><div><a \
href="http://apache-http-server.18135.x6.nabble.com/Help-regarding-mod-proxy-balancer- \
failover-and-failonstatus-td4998183.html">http://apache-http-server.18135.x6.nabble.co \
m/Help-regarding-mod-proxy-balancer-failover-and-failonstatus-td4998183.html</a><br></div><div><br></div><div>that \
failover (with no error message) will only occur when a connection to the instance \
cannot be made. I suppose as the instance was shutting down it returned/cut the \
current connection the proxy and hence the internal server error \
message.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Apr 20, 2016 at 3:17 PM, Wayne W <span dir="ltr">&lt;<a \
href="mailto:waynemailinglists@gmail.com" \
target="_blank">waynemailinglists@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">I did see the ping parameter for the \
Balancemember element could be used to test the connection - should we be using this? \
I&#39;m worried about more load on the tomcat instances though using this.</div><div \
class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Apr 20, 2016 at 3:07 PM, Wayne W <span dir="ltr">&lt;<a \
href="mailto:waynemailinglists@gmail.com" \
target="_blank">waynemailinglists@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Hi Jim,<div><br></div><div>I did&#39;t know \
that - is there any documentation around this? what should I search \
for?</div><div><br></div><div>So are you saying what I&#39;m experiencing is \
normal?</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On \
Wed, Apr 20, 2016 at 2:05 PM, Jim Jagielski <span dir="ltr">&lt;<a \
href="mailto:jim@jagunet.com" target="_blank">jim@jagunet.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">Upgrading to 2.4.20 allow you to disable the one node \
dynamically<br> on the httpd side and then bring down the node.<br>
<div><div>&gt; On Apr 20, 2016, at 8:10 AM, Wayne W &lt;<a \
href="mailto:waynemailinglists@gmail.com" \
target="_blank">waynemailinglists@gmail.com</a>&gt; wrote:<br> &gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; I&#39;m seeing that with Apache 2.4.12 on Solaris when setup with mod_proxy to 2 \
tomcat instances when we bring down 1 node for maintenance the first client to try \
and access that node gets a Internal Server Error. Any requests after that (and for \
other sessions) are balanced correctly onto the other node.<br> &gt;<br>
&gt; Is this normal?<br>
&gt; Is there a way for it to just balance over to the other node without returning \
the error?<br> &gt;<br>
&gt; My conf:<br>
&gt; &lt;VirtualHost *:80&gt;<br>
&gt;   ServerName<br>
&gt; <a href="http://somedomain.com" rel="noreferrer" \
target="_blank">somedomain.com</a><br> &gt;<br>
&gt;   ProxyPass /share<br>
&gt; <a href="http://127.0.0.1:8181/share" rel="noreferrer" \
target="_blank">http://127.0.0.1:8181/share</a><br> &gt;<br>
&gt;<br>
&gt;   ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off<br>
&gt;<br>
&gt;   # define the balancer, with http and/or ajp connections<br>
&gt;   &lt;Proxy balancer://cluster/&gt;<br>
&gt;           Order allow,deny<br>
&gt;           Allow from all<br>
&gt;           BalancerMember ajp://<br>
&gt; <a href="http://127.0.0.1:8010" rel="noreferrer" \
target="_blank">127.0.0.1:8010</a><br> &gt;   route=g1<br>
&gt;           BalancerMember ajp://<br>
&gt; <a href="http://127.0.0.1:8011" rel="noreferrer" \
target="_blank">127.0.0.1:8011</a><br> &gt;   route=g2<br>
&gt;   &lt;/Proxy&gt;<br>
&gt; &lt;/VirtualHost&gt;<br>
&gt;<br>
&gt;<br>
&gt; I see in the apache logs the following:<br>
&gt;<br>
&gt; Wed Apr 20 11:04:11.739700 2016] [proxy_ajp:error] [pid 58313] [client <a \
href="http://10.12.32.251:56869" rel="noreferrer" \
target="_blank">10.12.32.251:56869</a>] AH00992: ajp_read_header: ajp_ilink_receive \
failed, referer: <a href="https://example.com" rel="noreferrer" \
target="_blank">https://example.com</a><br> &gt; [Wed Apr 20 11:04:11.739713 2016] \
[proxy_ajp:error] [pid 58313] (120006)APR does not understand this error code: \
[client <a href="http://10.12.32.251:56869" rel="noreferrer" \
target="_blank">10.12.32.251:56869</a>] AH00878: read response failed from <a \
href="http://127.0.0.1:8010" rel="noreferrer" target="_blank">127.0.0.1:8010</a> \
(127.0.0.1), referer: <a href="http://example.com" rel="noreferrer" \
target="_blank">http://example.com</a><br> &gt; [<br>
<br>
<br>
</div></div>---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a href="mailto:users-unsubscribe@httpd.apache.org" \
target="_blank">users-unsubscribe@httpd.apache.org</a><br> For additional commands, \
e-mail: <a href="mailto:users-help@httpd.apache.org" \
target="_blank">users-help@httpd.apache.org</a><br> <br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic