On Sat, Oct 8, 2016 at 12:19 PM, Igor Cicimov <
ig...@encompasscorporation.com> wrote:
>
>
> On Sat, Oct 8, 2016 at 12:46 AM, cloud maverick
> wrote:
>
>> haproxy check is
>> like
>> option httpchk HEAD /HTTP/1.1\r\nHOST:.com
>> /api/checkusername/zabbix
>> http-check expect rstring true
On Sat, Oct 8, 2016 at 12:46 AM, cloud maverick
wrote:
> haproxy check is
> like
> option httpchk HEAD /HTTP/1.1\r\nHOST:.
> com/api/checkusername/zabbix
> http-check expect rstring true
>
> Response in status log
>
> Health check for server BE_Services_HTTPS_VIP/node1 failed, reason: Lay
On Sat, Oct 8, 2016 at 9:52 AM, vi...@abinnovative.com <
vi...@abinnovative.com> wrote:
> Hi All,
>
> Thanks, I have changed the options like check port 22 rise falls
> retries re-dispatch etc.. nothing works.
>
> As my client utility is written in apache camel, so it is retrying 3 times
> min
Hi All,
Thanks, I have changed the options like check port 22 rise falls
retries re-dispatch etc.. nothing works.
As my client utility is written in apache camel, so it is retrying 3
times min, I have only two nodes for the haproxy, so one node gets
alternatively failure and the second r
On 8 Oct 2016 2:16 am, "Willy Tarreau" wrote:
>
> Hi Igor,
>
> On Fri, Oct 07, 2016 at 08:41:12PM +1100, Igor Cicimov wrote:
> > > Listen
> > > ...
> > > ...
> > > Retries 3
> > > Option redispatch
> >
> > Vijay, did you read Lukas's email? Did you do as he suggested? Without
> > health check noth
We have a website that is setup like this:
CDN -> HAPROXY -> ELB -> APACHE -> TOMCAT
We are seeing with IE11 and Edge clients they will randomly lose their session
and get kicked out to a login screen. Firefox, Chrome and older IE clients
appear unaffected. Testing at all the different layers,
The documentation doesn't mention the sample fetcher `51d.all`, nor the
converter `51d.single`. The only place they're mentioned is the repo README.
Also the documentation for `51degrees-property-name-list` indicates it
takes an optional single string argument (`[]`), rather than
multiple string a
Hello,
shsess_store() has this odd looking code sequence (including line numbers):
333 /* it returns the already existing node
334or current node if none, never returns null */
335 oldshsess = shsess_tree_insert(shsess);
336 if (oldshsess != shsess) {
337
Hi Igor,
On Fri, Oct 07, 2016 at 08:41:12PM +1100, Igor Cicimov wrote:
> > Listen
> > ...
> > ...
> > Retries 3
> > Option redispatch
>
> Vijay, did you read Lukas's email? Did you do as he suggested? Without
> health check nothing will work, how do you expect for haproxy to know that
> a backend
haproxy check is
like
option httpchk HEAD /HTTP/1.1\r\nHOST:.com/api/checkusername/zabbix
http-check expect rstring true
Response in status log
Health check for server BE_Services_HTTPS_VIP/node1 failed, reason: Layer7
invalid response, info: "b'
{<22>success<22>:true}
'", check duration
On 07/10/2016 7:52 pm, "Vijay .D.R" wrote:
>
> Hi Willy,
>
> I read it in a forum and I do the changes in haproxy.cfg like below and
it's not working as expected.
>
> Listen
> ...
> ...
> Retries 3
> Option redispatch
Vijay, did you read Lukas's email? Did you do as he suggested? Without
health c
Hi Willy,
I read it in a forum and I do the changes in haproxy.cfg like below and it's not working as expected.
Listen
...
...
Retries 3
Option redispatch
12 matches
Mail list logo
