Hi.
-- Originalnachricht --
Von: "Ryan O'Hara"
An: "Aleksandar Lazic"
Cc: haproxy@formilux.org
Gesendet: 05.01.2018 23:35:10
Betreff: Re: haproxy-1.8 in Fedora
On Fri, Jan 5, 2018 at 3:12 PM, Aleksandar Lazic
wrote:
Hi Ryan.
-- Originalnachricht --
Von: "Ryan O'Hara"
An
On Fri, Jan 5, 2018 at 3:12 PM, Aleksandar Lazic wrote:
> Hi Ryan.
>
> -- Originalnachricht --
> Von: "Ryan O'Hara"
> An: haproxy@formilux.org
> Gesendet: 05.01.2018 17:19:15
> Betreff: haproxy-1.8 in Fedora
>
> Just wanted to inform Fedora users that haproxy-1.8.3 is now in the master
>
Hi Ryan
Copr is an easy-to-use automatic build system providing a package
repository as its output.
Start with making your own repository in these three steps:
choose a system and architecture you want to build for
provide Copr with src.rpm packages available online
let Copr do all the work and
Hi.
-- Originalnachricht --
Von: "Kuldip Madnani"
An: haproxy@formilux.org
Gesendet: 05.01.2018 17:32:25
Betreff: How can i use proxy server for my backend servers.
Hi,
I would like to use a http proxy, to access my backends that are
defined in my haproxy configuration. Is there a wa
Hi Ryan.
-- Originalnachricht --
Von: "Ryan O'Hara"
An: haproxy@formilux.org
Gesendet: 05.01.2018 17:19:15
Betreff: haproxy-1.8 in Fedora
Just wanted to inform Fedora users that haproxy-1.8.3 is now in the
master branch and built for Rawhide. I will not be updating haproxy to
1.8 in c
Hi Angelo.
-- Originalnachricht --
Von: "Angelo Hongens"
An: haproxy@formilux.org
Gesendet: 05.01.2018 11:49:55
Betreff: Re: haproxy without balancing
On 05-01-2018 11:28, Johan Hendriks wrote:
Secondly we could use a single ip and use ACL to route the traffic to
the right backend ser
Hi,
I would like to use a http proxy, to access my backends that are defined in
my haproxy configuration. Is there a way we can define http_proxy in
HAProxy configuration?
Thanks,
Kuldip
Just wanted to inform Fedora users that haproxy-1.8.3 is now in the master
branch and built for Rawhide. I will not be updating haproxy to 1.8 in
current stable releases of Fedora since I received some complaints about
doing major updates (eg. 1.6 to 1.7) is previous stables releases. That
said, th
On 05/01/2018 16:44, William Lallemand wrote:
> I'm able to reproduce, looks like it happens with the nbthread parameter only,
Exact, I observe the same.
At least I have a workaround for now to perform the upgrade.
> I'll try to find the problem in the code.
>
Thanks !
Pierre
On Fri, Jan 05, 2018 at 03:52:22PM +0100, Pierre Cheynier wrote:
> OK so now that I've applied all of Lukas recos (I kept the -x added ) :
>
> * I don't see any ALERT log anymore.. Only the WARNs
>
I'm still seing a few of them in journalctl. Maybe you don't see those emitted
by the workers, the
Op 05/01/2018 om 11:46 schreef Jonathan Matthews:
> On 5 January 2018 at 10:28, Johan Hendriks wrote:
>> BTW if this is the wrong list please excuse me.
> This looks to me like it might be the right list :-)
>
>> We have an application running over multiple servers which all have
>> there own su
>> Hi,
>>
>>> Your systemd configuration is not uptodate.
>>>
>>> Please:
>>> - make sure haproxy is compiled with USE_SYSTEMD=1
>>> - update the unit file: start haproxy with -Ws instead of -W (ExecStart)
>>> - update the unit file: use Type=notify instead of Type=forking
>> In fact that should w
> Hi,
>
>>> $ cat /usr/lib/systemd/system/haproxy.service
>>> [Unit]
>>> Description=HAProxy Load Balancer
>>> After=syslog.target network.target
>>>
>>> [Service]
>>> EnvironmentFile=/etc/sysconfig/haproxy
>>> ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q
>>> ExecStart=/usr/sbin/haproxy -W -f $
Hi,
> > $ cat /usr/lib/systemd/system/haproxy.service
> > [Unit]
> > Description=HAProxy Load Balancer
> > After=syslog.target network.target
> >
> > [Service]
> > EnvironmentFile=/etc/sysconfig/haproxy
> > ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q
> > ExecStart=/usr/sbin/haproxy -W -f $CONF
Hello Pierre,
On Fri, Jan 5, 2018 at 11:48 AM, Pierre Cheynier wrote:
> Hi list,
>
> We've recently tried to upgrade from 1.8.0 to 1.8.1, then 1.8.2, 1.8.3
> on a preprod environment and noticed that the reload is not so seamless
> since 1.8.1 (easily getting TCP RSTs while reloading).
>
> Havin
On 05-01-2018 11:28, Johan Hendriks wrote:
Secondly we could use a single ip and use ACL to route the traffic to
the right backend server.
The problem with the second option is that we have around 2000 different
subdomains and this number is still growing. So my haproxy config will
then consists
Hi list,
We've recently tried to upgrade from 1.8.0 to 1.8.1, then 1.8.2, 1.8.3
on a preprod environment and noticed that the reload is not so seamless
since 1.8.1 (easily getting TCP RSTs while reloading).
Having a short look on the haproxy-1.8 git remote on the changes
affecting haproxy.c, c2b2
On Thu, Jan 04, 2018 at 02:14:41PM -0500, Jeffrey J. Persch wrote:
> Hi William,
>
> Verified.
>
> Thanks for the quick fix,
Great, patch now merged. Thanks!
Willy
On 5 January 2018 at 10:28, Johan Hendriks wrote:
> BTW if this is the wrong list please excuse me.
This looks to me like it might be the right list :-)
> We have an application running over multiple servers which all have
> there own subdomain, there are about 12 of them.
> We can live without
Hello.
First off all I wish everyone a really good 2018. And hopefully 2018
will serve a lot of good memory's.
BTW if this is the wrong list please excuse me.
We have an application running over multiple servers which all have
there own subdomain, there are about 12 of them.
We can live without l
On Thu, Jan 04, 2018 at 06:03:05PM +0100, Olivier Houchard wrote:
> The rbtree implementation as found in haproxy, is currently unused, and has
> been for quite some time.
> I don't think we will need it again, so the attached patch just removes it.
I'm pretty sure we planned to remove it a very l
Hi guys,
On Thu, Jan 04, 2018 at 11:20:32PM +0100, Lukas Tribus wrote:
> On Thu, Jan 4, 2018 at 11:11 PM, Angelo Hongens wrote:
> > On 03-01-2018 17:39, Lukas Tribus wrote:
> >>
> >> To compile Haproxy 1.8 with threads, at least GCC 4.7 is needed.
> >> CentOs 6 only ships GCC 4.4.7, therefor comp
22 matches
Mail list logo
