Re: [PATCH] BUILD/CLEANUP: systemd: avoid a warning due to mixed code and declaration

On Tue, Mar 03, 2015 at 11:26:14PM +0100, Cyril Bonté wrote: > Gcc complains because the systemd wrapper mixed code and declaration : > "warning: ISO C90 forbids mixed declarations and code > [-Wdeclaration-after-statement]". (...) both patches applied, thanks Cyril. Willy

Re: Lua patchset merged

On Tue, 03 Mar 2015 19:35:34 +0100 Cyril Bonté wrote: > Hi Thierry, > > Le 01/03/2015 13:47, Thierry FOURNIER a écrit : > > > > HAProxy Lua Hello world > > > > HAProxy configuration file (hello_world.conf): > > > > global > > lua-load hello_world.lua > > > > listen proxy > > bind 127

Re: Lua patchset merged

Hi Thierry, Le 04/03/2015 11:51, Thierry FOURNIER a écrit : Thank you Cyril for the bug repport. I join the patch that fix this issue. Great ! I didn't have time to investigate further. I can confirm that the patch works well ;-) -- Cyril Bonté

Peers with long hostnames

Hi All, I'm having some difficulty in getting my peers working with a two node setup. Here the config section in question: peers PRSPEERS peer prod-portal-rest-hap-1 prod-portal-rest-hap-2.xxx.xxx.com:4000 peer prod-portal-rest-hap-2 prod-portal-rest-hap-2.xxx.xxx

CABSAT 2015.

Hi, Wishing you all the best for International CABSAT 2015. I understand that you are one of the exhibitors in the International CABSAT 2015, would you be interested to avail an opt-in email list of CABSAT 2015 Digital Media and Broadcasts Professionals data? Below are the lists o

Re: Peers with long hostnames

Hi, Le 04/03/2015 21:52, James Candalino a écrit : Hi All, I'm having some difficulty in getting my peers working with a two node setup. Here the config section in question: peers PRSPEERS peer prod-portal-rest-hap-1 prod-portal-rest-hap-2.xxx.xxx.com:4000

Re: Peers with long hostnames

Le 04/03/2015 23:18, Cyril Bonté a écrit : Le 04/03/2015 23:10, James Candalino a écrit : Cool, solution 1 worked. It seems as though the peer name is limited to only 32 characters yet hostnames as reported by the system can be much longer. Right, and it has been extended to 64 characters in t

agent-check sets status "DRAIN" for no apparent reason.

Using HA-Proxy version 1.5.6 2014/10/18 on CentOS 6, recently updated, etc. I'm trying to use agent-check to add/remove http servers on the back end, and it will *not* enable a web-server; instead it marks its status as DRAIN even though it's working fine and responding to requests. I've set

Re: Peers with long hostnames

Hi Cyril, On Wed, Mar 04, 2015 at 11:20:38PM +0100, Cyril Bonté wrote: > Le 04/03/2015 23:18, Cyril Bonté a écrit : > >Le 04/03/2015 23:10, James Candalino a écrit : > >>Cool, solution 1 worked. It seems as though the peer name is limited to > >>only 32 characters yet hostnames as reported by the

Re: Peers with long hostnames

Le 5 mars 2015 07:47, "Willy Tarreau" a écrit : > > Hi Cyril, > > On Wed, Mar 04, 2015 at 11:20:38PM +0100, Cyril Bonté wrote: > > Le 04/03/2015 23:18, Cyril Bonté a écrit : > > >Le 04/03/2015 23:10, James Candalino a écrit : > > >>Cool, solution 1 worked. It seems as though the peer name is limit

Re: bug? rand based acl keep re-evaluating

Hi Vivek, On Sun, Mar 01, 2015 at 12:21:57AM -0600, Vivek Malik wrote: > Hi, > > I spent last few hours scratching my head and wondering where my > configuration was wrong and why was it acting weird. Sending this to > ML to see if this is a bug or expected behavior. I expected ACL to > evaluate

Re: Lua patchset merged

On Mon, Mar 02, 2015 at 11:33:39PM +0100, Baptiste wrote: > I love it ! > > Just wrote, as a proof of concept, a forward proxy... > That said, it seems my lua script is "blocking"... I mean, if the > remote server is slow to deliver the response, then HAProxy doesn't > process any

Re: bug? rand based acl keep re-evaluating

Hi Willy, I am using haproxy/rand to simulate A/B/C... testing between multiple environments. Each backend emits a long expiry cookie to put the session into their experiment. If a request comes with a cookie of the experiment, the request goes to that backend. If a session comes without a cookie,