eginning to troubleshoot 2.0.5 at this point does not make a lot of
sense inmho considering the amount and importance of the fixes
committed after 2.0.5.
Regards,
Lukas
[1] (git clone) http://git.haproxy.org/git/haproxy-2.0.git/
[2] http://www.haproxy.org/download/2.0/src/snapshot/haproxy-ss-20190911.tar.gz
oops.
I did have a look at https://hub.docker.com/search?q=haproxytech=image
(built from https://github.com/haproxytech )
so... there are many many many docker images.
when should I use either of these images?
ср, 11 сент. 2019 г. в 23:48, Илья Шипицин :
> Hello,
>
> it was a surprize for me
Hi.
I have updated the image to the latest OpenSSL version 1.1.1d
https://hub.docker.com/r/me2digital/haproxy20-centos
```
$ docker run --rm --entrypoint /usr/local/sbin/haproxy
[MASKED]/haproxy20-centos -vv
HA-Proxy version 2.0.5 2019/08/16 - https://haproxy.org/
Build options :
TARGET =
Hello,
it was a surprize for me that official images are also available (I used to
think your images are only available)
https://hub.docker.com/_/haproxy
is there some documentation when your images should be used (instead of
official) ?
ср, 11 сент. 2019 г. в 22:58, Aleksandar Lazic :
> Hi.
Hi.
Am 11.09.2019 um 20:48 schrieb Илья Шипицин:
> Hello,
>
> it was a surprize for me that official images are also available (I used to
> think your images are only available)
>
> https://hub.docker.com/_/haproxy
>
> is there some documentation when your images should be used (instead of
>
чт, 12 сент. 2019 г. в 01:01, Aleksandar Lazic :
> Hi.
>
> Am 11.09.2019 um 20:48 schrieb Илья Шипицин:
> > Hello,
> >
> > it was a surprize for me that official images are also available (I used
> to
> > think your images are only available)
> >
> > https://hub.docker.com/_/haproxy
> >
> > is
Hello Artur,
On Wed, Sep 11, 2019 at 1:22 PM Artur wrote:
>
> Hello,
>
> My current 2.0.5 haproxy logs a lot of "useless" messages such as :
>
> Sep 11 13:10:08 server haproxy[28163]: Connect from 127.0.0.1:39951 to
> 127.0.0.1:6379 (r1_front/TCP)
>
> My configuration is something like (I
> On Tue, Sep 10, 2019 at 08:29:38PM +0500, ??? wrote:
> > those findings are mostly mess (maybe, except few real bugs).
> > I do not mind sharing those findings with community, Willy ?
> > we need more manpower here.
>
> Oh no problem! I'm not the one asking to hide bugs, the more
On Tue, Sep 10, 2019 at 08:29:38PM +0500, ??? wrote:
> those findings are mostly mess (maybe, except few real bugs).
> I do not mind sharing those findings with community, Willy ?
> we need more manpower here.
Oh no problem! I'm not the one asking to hide bugs, the more eyeballs
on bug
it depends on how haproxy is built (number of flags)
we use most of available options when testing on coverity
https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8
can you share build command ? we may also set up sonar in travis-ci
schedules.
(personally, I find sonar too much noisy,
On Tue, Sep 10, 2019 at 03:56:43PM +0200, Tim Düsterhus wrote:
> Luca,
>
> Am 10.09.19 um 15:48 schrieb Schimweg, Luca:
> > sorry, didn't know about these guidelines. I packed all changes into one
> > commit in the patch file in the attachments.
>
> One more thing: Do not leave out the body of
Hi Ilya,
On Thu, Aug 08, 2019 at 12:45:33PM +0500, ??? wrote:
> Hello,
>
> coverity found tens of "null pointer dereference".
> also, there's a good correlation, after "now fixed, good catch" coverity
> usually dismiss some bug.
>
> should we revisit those findings ?
Not necessarily.
Hey,
thanks for the feedback. I included the changes in the updated patch.
Best regards
Luca
On 11.09.19, 08:52, "Willy Tarreau" wrote:
On Tue, Sep 10, 2019 at 03:56:43PM +0200, Tim Düsterhus wrote:
> Luca,
>
> Am 10.09.19 um 15:48 schrieb Schimweg, Luca:
> > sorry,
Hi!
I have an issue which I've don't know how to go ahead with.
So first I will describe my setup.
We have a pair of haproxy v2.0.5 that only takes HTTP traffic and relays
HTTPS traffic down to a pair of haproxys v1.7.11 doing SSL termination.
Here is a more "graphical" layout:
Internet
Luca,
Am 11.09.19 um 09:40 schrieb Schimweg, Luca:
> thanks for the feedback. I included the changes in the updated patch.
>
Something went wrong with the commit message:
> Subject: [PATCH] MINOR: sample: Add UUID-fetch Adds the fetch uuid(int). New
> feature, but could be backported
Did you
Hey Tim,
Thanks, I missed the empty line. Fixed it
Yeah, the email is correct. There is no github.com account associated with this
email, so I'll use my private email to commit, which has a github.com account.
Best regards
Luca
On 11.09.19, 12:26, "Tim Düsterhus" wrote:
Luca,
On Wed, Sep 11, 2019 at 10:08:46AM +0200, GARDAIS Ionel wrote:
> Please note that Sonarqube is scanning haproxy code too.
> Results are available at https://sonarcloud.io/dashboard?id=haproxy
Ah indeed.
> Some results are false positive but some are worth looking at.
Well, I've already lost one
Greetings,
I'm Senad from HAProxy Technologies, one of the organizers of
HAProxyConf in Amsterdam on November 12-13.
We just announced the full speaker line-up and the agenda
(https://haproxyconf.com/agenda/).
Thanks to our selection committee that included several members from the
it depends on how haproxy is built (number of flags)
BQ_BEGIN
we use most of available options when testing on coverity
[ https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8 |
https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8 ]
can you share build command ? we may
Hello,
My current 2.0.5 haproxy logs a lot of "useless" messages such as :
Sep 11 13:10:08 server haproxy[28163]: Connect from 127.0.0.1:39951 to
127.0.0.1:6379 (r1_front/TCP)
My configuration is something like (I removed lines not related to
logging) :
global
log /dev/log local0
Hi.
Am 11.09.2019 um 13:22 schrieb Artur:
> Hello,
>
> My current 2.0.5 haproxy logs a lot of "useless" messages such as :
>
> Sep 11 13:10:08 server haproxy[28163]: Connect from 127.0.0.1:39951 to
> 127.0.0.1:6379 (r1_front/TCP)
>
> My configuration is something like (I removed lines not
Hey again,
sorry for reviving an old(ish) thread, but I would love to get some
kind of feedback, even if it's just that this will stay this way and I
need to deal with it.
I also tried with the payload syntax in the meantime, but to no avail.
Is there any supported way of adding patterns with
22 matches
Mail list logo
