Hmmm, I thought I typed more text...
On 22.05.2012 11:06, Sander Klein wrote:
Hi,
When I reload haproxy I get this message:
May 22 11:02:45 lb01-a haproxy: *** glibc detected ***
/usr/sbin/haproxy: double free or corruption (out):
0x01ef41a0
***
I'm running haproxy 1.5-dev10
I read through the last 6 months of archive and the usual answer
for SSL support is put nginx/stunnel/stud in front. This, as far
as I can tell, means a single server handling SSL, and this is
the what http://haproxy.1wt.eu/#desi suggest is a non-scalable
solution.
You can obviously
Dear Reader,
Invitation to attend - web event led by Deepak Malhotra, Chief Legal
Administrative Officer and Global Counsel, Fusion Universal, UK
Topic: Value Based Fee Arrangement – Chief Counsel’s Approach to
Structuring Relationships
Venue: At your desk: On your Laptop/PC or Phone
Date: 23
OoO Lors de la soirée naissante du mardi 22 mai 2012, vers 17:52, Bar
Ziony bar...@gmail.com disait :
You need to place a packet load balancer such as LVS in front of
haproxy, which directs SSL traffic to an SSL farm (which saves the
client IP), and regular HTTP access to haproxy.
That's
On 2012-05-22 19:46:45, Vincent Bernat wrote:
Yes. And solve session problem by using some kind of persistence, for
example source hashing load balancing algorithm.
Persistence here meaning ssl packets for a given session goes to
the same ssl server? If so what happens if that ssl server
A recommended upgrade for all production users. While we are not
(generally) affected by the bugs fixed in haproxy stable version. I
recommend updating haproxy.
I can update haproxy bin in puppet and can check it in (we distribute
haproxy binary via puppetmaster).
Aiman,
Please update
if a SSL server dies, LVS can direct the traffic to another server.
Alternatively you can save SSL sessions in memcached for example, to share
between SSL servers in the SSL farm. I once stumbled upon a patch for nginx
that can do that.
Regards,
Bar.
On Tue, May 22, 2012 at 9:16 PM, Allan Wind
7 matches
Mail list logo
