Re: [PATCH] BUG/MEDIUM: email-alert: don't set server check status from a email-alert task

Hi Pieter, CCing Emeric since these parts have changed a bit for threads and there may be some subtle things we oversee. thanks for this! Willy On Wed, Dec 06, 2017 at 02:11:53AM +0100, PiBa-NL wrote: > Hi List, Simon and Baptiste, > > Sending to both of you guys as its both tcp-check and

Audio Transcription Service (AA2)

Hello,Need someone reliable to transcribe both your short term and long term projects? Need an accurate transcript for your audio or video?   Allow me to transcribe your audio and provide you accurate transcripts and let me help you reach your business/project goals through the help of my

Re: server DOWN and can not auto restore to MAINT state when use DNS SRV resolvers

>1. running two container and publish port 80 but not really listening >to 80. I simulate a service fault. (eg: port missed config). And in step 2 the health check has layer4 failed: Connection refused. > As you writen in 3 there is "DNS NX" (=> no dns entry) for all 3 servers, what do you expect

[PATCH] BUG/MEDIUM: email-alert: don't set server check status from a email-alert task

Hi List, Simon and Baptiste, Sending to both of you guys as its both tcp-check and email related and you are the maintainers of those parts. Patch subject+content basically says it all (i hope.). It is intended to fixes yesterdays report:

Re: server DOWN and can not auto restore to MAINT state when use DNS SRV resolvers

Hi. -- Originalnachricht -- Von: "slene" An: haproxy@formilux.org Gesendet: 05.12.2017 11:36:27 Betreff: server DOWN and can not auto restore to MAINT state when use DNS SRV resolvers I'm a new fisher of haproxy. I have some question when I use consul and

Re: Failed checks issue

-- Originalnachricht -- Von: "Haim Ari" An: "haproxy@formilux.org" Gesendet: 05.12.2017 10:31:36 Betreff: Failed checks issue Hello, After upgrading to 1.8.1 i'm now facing this issue... (screenshot attached) [snipp] After

Re: [PATCH 1/2] DOC: mworker: Update messages referencing exit-on-failure

William, Am 04.12.2017 um 16:09 schrieb William Lallemand: > I prefer to leave this one, because otherwise the user won't understand why it > killed the workers, and a grep on "exit-on-failure" in the documentation will > find "no-exit-on-failure" so that's not a problem. > Okay, updated patch

[PATCH v2 2/2] DOC: mworker: Improve wording in `void mworker_wait()`

Replace "left" / "leaving" with "exit" / "exiting". --- src/haproxy.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/haproxy.c b/src/haproxy.c index df8d34e74..108a02ab0 100644 --- a/src/haproxy.c +++ b/src/haproxy.c @@ -739,7 +739,7 @@ restart_wait:

[PATCH v2 1/2] DOC: mworker: Update messages referencing exit-on-failure

Commit 4cfede87a313456fcbce7a185312460b4e1d05b7 removed `exit-on-failure` in favor of `no-exit-on-failure`, but failed to update references to the former in user facing messages. This should be backported to haproxy 1.8. --- src/cfgparse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

AdWords Software for Increasing Revenue

Hi, We are one of the Google's Premium partner and leading Google Shopping automation software provider for e-commerce companies/ other sectors across Globe. Our software completely automates the steps in Google Shopping and consistently delivers at-least 50% more conversions than your

server DOWN and can not auto restore to MAINT state when use DNS SRV resolvers

I'm a new fisher of haproxy. I have some question when I use consul and registrator for service discovery. And use haproxy as balancer. My steps: 1. running two container and publish port 80 but not really listening to 80. 2. haproxy found two server failed status: 0/9 DOWN. (not tried times,