Glad you found a solution that works for you. I personally don't see any
issues with this since lua is lightweight and haproxy is famous for
efficient resource management. So all should be good under "normal" usage
and by normal I mean a traffic and usage pattern you expect from your app
users
Willy,
Am 11.06.20 um 11:06 schrieb Willy Tarreau:
> So we're getting pretty good for a release very soon. I think that this
> might be the last development release so it can be considered almost as a
> release candidate, and that if everything goes well, we could release by the
> end of next
Bjoern,
Willy,
Am 11.06.20 um 11:24 schrieb bjun...@gmail.com:
> i have a Travis CI job that is pulling/cloning a repo from git.haproxy.org,
> but unfortunately this isn't working anymore (i believe since May, 12).
>
> Output Travis CI job:
>
> [...]
>
> Is there any IP blocking or something
On Thu, Jun 11, 2020 at 12:01:32PM +0200, Tim Düsterhus wrote:
> Willy,
>
> Am 11.06.20 um 11:06 schrieb Willy Tarreau:
> > So we're getting pretty good for a release very soon. I think that this
> > might be the last development release so it can be considered almost as a
> > release candidate,
we had to change libslz url as well
https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3
however, I did not investigate deeper (traceroute, etc, ...)
чт, 11 июн. 2020 г. в 14:59, Tim Düsterhus :
> Bjoern,
> Willy,
>
> Am
On Thu, Jun 11, 2020 at 03:17:07PM +0500, ??? wrote:
> we had to change libslz url as well
>
> https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3
Fine!
> however, I did not investigate deeper (traceroute, etc, ...)
Hi,
HAProxy 2.2-dev9 was released on 2020/06/11. It added 205 new commits
after version 2.2-dev8.
Among the user-visible changes, we've now integrated Emeric's work on
the "ring" sections which allow to forward ring contents to remote servers
over TCP. This is directly usable to send syslog over
Hi list,
haproxy-1.8 is missing two backports, and can't be built with recent gcc
as a result.
72d9f3351 BUILD: chunk: properly declare pool_head_trash as extern
2231b6388 BUILD: cache: avoid a build warning with some compilers/linkers
regards,
Jérôme
Hello,
I have a question regarding Peers . I am currently trying to set up 2 HaProxy
instances as Docker containers. Please see my peers configuration below:
resolvers dns-resolver
parse-resolv-conf
nameserver dns1 127.0.0.11:53
resolve_retries 3
timeout resolve 1s
Hello Willy,
i have a Travis CI job that is pulling/cloning a repo from git.haproxy.org,
but unfortunately this isn't working anymore (i believe since May, 12).
Output Travis CI job:
$ ping -c 4 git.haproxy.org
PING ipv4.haproxy.org (51.15.8.218) 56(84) bytes of data.
--- ipv4.haproxy.org ping
Hi Tim,
On Thu, Jun 11, 2020 at 12:01:32PM +0200, Tim Düsterhus wrote:
> Willy,
>
> Am 11.06.20 um 11:06 schrieb Willy Tarreau:
> > So we're getting pretty good for a release very soon. I think that this
> > might be the last development release so it can be considered almost as a
> > release
On Thu, Jun 11, 2020 at 01:09:37PM +0200, bjun...@gmail.com wrote:
> Hello Willy,
>
> just for clarity, it's not only port 80. I've looked at it, it's
> definitely some issue/blocking within the travis infrastructure, routing
> from GCE Cloud (us-east1) is fine.
OK, that's good to know.
Thanks,
Willy,
William
Am 29.05.20 um 14:35 schrieb Tim Duesterhus:
> These two patches re-enable some build warnings in the Makefile. The first one
> only enables those that did not trigger for me at all.
>
> The second one re-enables -Wimplicit-fallthrough. I could not adjust all
> places, because I
pushing to github is not related to Travis. Those are different clouds:)
On Thu, Jun 11, 2020, 3:23 PM Willy Tarreau wrote:
> On Thu, Jun 11, 2020 at 03:17:07PM +0500, ??? wrote:
> > we had to change libslz url as well
> >
> >
>
Hi,
one more question. Now that i have to use the github mirror, how can i get
the latest changes of the 2.1 tree? (as possible with "
https://git.haproxy.org/git/haproxy-2.1.git/;).
There is no branch or tag on github with which i can get the latest changes
of the 2.1 tree.
Best regards / Mit
On Thu, Jun 11, 2020 at 01:35:34PM +0200, bjun...@gmail.com wrote:
> Hi,
>
> one more question. Now that i have to use the github mirror, how can i get
> the latest changes of the 2.1 tree? (as possible with "
> https://git.haproxy.org/git/haproxy-2.1.git/;).
>
> There is no branch or tag on
On Thu, Jun 11, 2020 at 04:06:52PM +0500, ??? wrote:
> pushing to github is not related to Travis. Those are different clouds:)
Sure but what I wanted to say was that travis seems to be the only
point experiencing such difficulties and we don't know how it works
nor what are the rules in
Hello Willy,
just for clarity, it's not only port 80. I've looked at it, it's
definitely some issue/blocking within the travis infrastructure, routing
from GCE Cloud (us-east1) is fine.
Best regards / Mit freundlichen Grüßen
Bjoern
Am Do., 11. Juni 2020 um 12:23 Uhr schrieb Willy Tarreau :
>
On Thu, Jun 11, 2020 at 03:04:39PM +0200, Tim Düsterhus wrote:
> > Tim Düsterhus (2):
> > BUILD: Remove nowarn for warnings that do not trigger
> > BUILD: Re-enable -Wimplicit-fallthrough
>
> With the new -dev9 I'd like to move this thread up the INBOX again, in
> case you want to resolve
By the way if that helps I've re-added the records for
{git,www}.haproxy.org. It will take one hour or so to propagate, but
you'll be able to see if using IPv6 causes the same issue or not. I'd
guess it would work better since the routes are likely different.
Willy
Am Do., 11. Juni 2020 um 15:00 Uhr schrieb Willy Tarreau :
> By the way if that helps I've re-added the records for
> {git,www}.haproxy.org. It will take one hour or so to propagate, but
> you'll be able to see if using IPv6 causes the same issue or not. I'd
> guess it would work better
Hello, list
We got a very high CPU constantly while using 2.2dev. Any suggestion? Thanks.
Config like:
global
log 127.0.0.1 local0
maxconn 4096
daemon
ssl-server-verify none
defaults
log global
modehttp
option httplog
timeout check 3000
timeout connect
Hello Igor,
On Thu, Jun 11, 2020 at 5:25 PM Igor Pav wrote:
> We got a very high CPU constantly while using 2.2dev. Any suggestion? Thanks.
Do you have more inputs of what you are doing to trigger that?
does it end at some point with an abort? e.g do you have in logs
things like "Thread X is
On Thu, Jun 11, 2020 at 07:27:26PM +0200, William Lallemand wrote:
> On Thu, Jun 11, 2020 at 12:41:51PM +0200, Jerome Magnin wrote:
> > 72d9f3351 BUILD: chunk: properly declare pool_head_trash as extern
> > 2231b6388 BUILD: cache: avoid a build warning with some compilers/linkers
> >
> The 1.8
Dear list!
Author: Peter Gervai
Number of patches: 1
This is an automated relay of the Github pull request:
Unindent non-code sentences in the protobuf example
Patch title(s):
Unindent non-code sentences in the protobuf example
Link:
https://github.com/haproxy/haproxy/pull/677
Edit
Dear list!
Author: Peter Gervai
Number of patches: 1
This is an automated relay of the Github pull request:
http-check send was missing from matrix
Patch title(s):
http-check send was missing from matrix
Link:
https://github.com/haproxy/haproxy/pull/678
Edit locally:
wget
On Thu, Jun 11, 2020 at 12:41:51PM +0200, Jerome Magnin wrote:
> Hi list,
>
> haproxy-1.8 is missing two backports, and can't be built with recent gcc
> as a result.
> 72d9f3351 BUILD: chunk: properly declare pool_head_trash as extern
> 2231b6388 BUILD: cache: avoid a build warning with some
Hello,
Just FYI: the build is broken since this commit:
https://github.com/haproxy/haproxy/commit/7c18b54106ec21273aea3fe59ba23280e86821f5
https://travis-ci.com/github/haproxy/haproxy/builds
Regards,
Martin
28 matches
Mail list logo
