Hi Maksim,
On Tue, May 21, 2019 at 01:47:30PM +0300, ?? ? wrote:
> Hi!
>
> I've run into some weird problem of many connections failed with SD status
> in log. And I have no idea how to discover the source of the problem.
>
> >From the point of client it looks like this:
> * Client
Hi Ilya,
On Thu, May 23, 2019 at 01:29:53AM +0500, ??? wrote:
> Hello,
>
> if we do not like using github PR and Willy receives 2k emails a day...
> do we consider using something like that
> https://patchwork.openvpn.net/project/openvpn2/list/ ?
At least not now, please let's slow
Hello,
if we do not like using github PR and Willy receives 2k emails a day...
do we consider using something like that
https://patchwork.openvpn.net/project/openvpn2/list/ ?
cheers,
Ilya Shipitsin
Hi,
HAProxy 2.0-dev4 was released on 2019/05/22. It added 83 new commits
after version 2.0-dev3.
This release completes the integration of a few pending features and
the ongoing necessary cleanups before 2.0.
A few bugs were addressed in the way to deal with certain connection
errors, but
Hi Eduardo.
That's a pretty interesting question, at least for me.
First why do you restart all haproxies at the same time and don't use rolling
updates ?
https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/
Maybe you can add a init container to update the peers in the
On Wed, May 22, 2019 at 03:24:25PM +0500, ??? wrote:
> Hello,
>
> someone is reviewing this https://github.com/haproxy/haproxy/runs/133866993
> ?
So apparently we don't have _POSIX_C_SOURCE >= 199309L there, which
contradicts the promise in my linux man pages :-/ The docs on opengroup
Hi Willy,
Finally got sometime to have the patch revised.
I am reusing the "send_proxy_ofs" right now.
Due to it was used as some kind of flag for send Proxy Protocol in some places.
I have to replace those usage to check the srv->pp_opts.
Please help to have a look into it, thank you!
On Wed, May 22, 2019 at 08:14:11PM +0500, ??? wrote:
> done
thank you :-)
By the way I was thinking that we should probably start to use the
"ci" tag on patch subject lines to cover travis and cirrus. This way
even if you perform cross-ci changes (build options etc) you can put
them in
done
ср, 22 мая 2019 г. в 19:18, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote:
> > build is green now, we can apply this patch (I skipped "linux-ppc64le"
> for
> > a while)
>
> It's really easier for me if you attach it again. I'm getting about 2k
>
ср, 22 мая 2019 г. в 19:18, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote:
> > build is green now, we can apply this patch (I skipped "linux-ppc64le"
> for
> > a while)
>
> It's really easier for me if you attach it again. I'm getting about 2k
>
Hi Ilya,
On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote:
> build is green now, we can apply this patch (I skipped "linux-ppc64le" for
> a while)
It's really easier for me if you attach it again. I'm getting about 2k
emails a day and having to do dig through archives to pick one
Hi all!
As a few of you may remember, we had a small-group HAProxy workshop 3
years ago to see if it would be useful to meet from time to time and it
was a great success that we've been impatient to re-edit but much wider,
and not limited to developers.
Well, time flies, I'm a terrible organizer
build is green now, we can apply this patch (I skipped "linux-ppc64le" for
a while)
ср, 22 мая 2019 г. в 18:37, :
> From: Ilya Shipitsin
>
> full list of changes:
>
> use TARGET=osx instead of generic for osx builds,
> add USE_PCRE_JIT=1, USE_GETADDRINFO=1 to build matrix,
> enable address
From: Ilya Shipitsin
full list of changes:
use TARGET=osx instead of generic for osx builds,
add USE_PCRE_JIT=1, USE_GETADDRINFO=1 to build matrix,
enable address sanitizer for clang
---
v2 skip sanitizer on linux-ppc64le
.travis.yml | 21 +++--
1 file changed, 11
Hi,
I'm using HAProxy to support a system that was initially developed for
Apache (AJP) and JBoss. Now we are migrating it's infrastructure to a
Kubernetes cluster with HAProxy as ingress (load balancer).
The big problem is this system depends strict to JSESSIONID. Some internal
requests made in
Wed May 22 13:00:58 GMT+02:00 2019 Mortada, Mahmoud :
> Haproxy in the debug mode and I tried to access the 3 link https and http:80
> and http:8080 and it doesn’t report anything on the console of the haproxy.
>
> [root@ies-esd-jiradc-loadb-stage haproxy]# haproxy -f
>
You need to add `accept-proxy` keyword in receiving haproxy bind line.
https://cbonte.github.io/haproxy-dconv/1.9/configuration.html#5.1-accept-proxy
Hth
Aleks
Wed May 22 14:03:26 GMT+02:00 2019 praveen kumar :
>
> have a haproxy setup as follow:
>
> Client --> Haproxy (LOCATION A)-->
Hi Massimiliano,
On Tue, May 21, 2019 at 05:23:16PM +0200, Massimiliano Bellomi wrote:
> Hi All.
>
> Here attached you may find a new set of patches related to WURFL module
> that should address Christopher and Willy suggestion.
Thank you, I've applied them. I tried to add some info to the
have a haproxy setup as follow:
Client --> Haproxy (LOCATION A)--> HAProxy(LOCATION B)> Server
Both HA Proxy are running in TCP mode in both frontend and backend. My
server wants to see actual client ip connecting to it, so I have enabled
*send-proxy* on location A haproxy and sending it
Good day Guys
I am busy building a mail gateway for the corp I work for, but with
haproxy in front of the MTAs (TLS).
The problem we are experiencing is, we are getting the following error
message:
2019-05-22 12:23:15 SMTP protocol synchronization error (input sent
without waiting for
Haproxy in the debug mode and I tried to access the 3 link https and http:80
and http:8080 and it doesn’t report anything on the console of the haproxy.
[root@ies-esd-jiradc-loadb-stage haproxy]# haproxy -f /etc/haproxy/haproxy.cfg
[WARNING] 141/115311 (1114) : parsing
Hello,
someone is reviewing this https://github.com/haproxy/haproxy/runs/133866993
?
thanks,
Ilya Shipitcin
Am 22.05.2019 um 11:24 schrieb Mortada, Mahmoud:
> Sorry there was a space missing in the if statement after adding the space
> service become up normally
>
> Redirection happened as before with port :8080 in the link
can you run haproxy in debug mode and see what's returned by jira.
>
more findings
https://travis-ci.org/chipitsine/haproxy-1/jobs/535709949#L1938-L1948
ср, 22 мая 2019 г. в 15:12, Илья Шипицин :
> here's build with patch applied
>
> https://travis-ci.org/chipitsine/haproxy-1/jobs/535709947#L604-L608
>
> ср, 22 мая 2019 г. в 14:43, William Lallemand :
>
>> Hi
here's build with patch applied
https://travis-ci.org/chipitsine/haproxy-1/jobs/535709947#L604-L608
ср, 22 мая 2019 г. в 14:43, William Lallemand :
> Hi Tim,
>
> Sorry for the delay.
>
> I added 2 new lines in your patch:
>
> On Thu, May 16, 2019 at 08:23:22PM +0200, Tim Duesterhus wrote:
> >
Hi Tim,
Sorry for the delay.
I added 2 new lines in your patch:
On Thu, May 16, 2019 at 08:23:22PM +0200, Tim Duesterhus wrote:
> +void mworker_free_child(struct mworker_proc *child) {
> + if (child == NULL) return;
> +
Which became:
> +void mworker_free_child(struct mworker_proc *child)
Sorry there was a space missing in the if statement after adding the space
service become up normally
Redirection happened as before with port :8080 in the link
[cid:image001.png@01D51090.F99DC8A0]
Regards,
Mahmoud Mortada
-Original Message-
From: Mortada, Mahmoud
Sent:
Hi Aleksandar,
Yes I do Jira redirection configuration.
After adding the below line haproxy service not able to start.
http-response set-header location %[res.hdr(location),regsub(:8080/,/)] if {
res.hdr(location) -m found }
May 22 10:06:59 ies-esd-jiradc-loadb-stage
Hi Mahmoud.
Am 21.05.2019 um 14:57 schrieb Mortada, Mahmoud:
> Hi Aleksandar,
>
> Thanks for your reply.
>
> My main issue when I tried to access
> http://ies-esd-jiradc-loadb-stage.ies.mentorg.com:8080 it works but redirect
> me
> to https://ies-esd-jiradc-loadb-stage.ies.mentorg.com:8080
>
29 matches
Mail list logo
