send/accept-proxy over unix socket not working
Hi, I'm currently trying to find the most efficient way to pass traffic from one frontend to another (and later to another process altogether) so I've tried using unix sockets but this does not seem to work. In the first frontend I set: server clear /var/lib/haproxy/test send-proxy In the second frontend I set: bind /var/lib/haproxy/test accept-proxy This results in a 503 error (the log shows the flags "SC--"). If instead I use this in the first frontend: server clear 127.0.0.1:8081 send-proxy and this in the second: bind 127.0.0.1:8081 accept-proxy then everything starts working fine. Is there anything else that needs to be specified to make this work over unix sockets? Regards, Dennis
Magento Users 2015
Hi, Would you be interested in Magento Users 2015 for your email marketing campaign? We can provide data from North America, Latin America, EMEA and APAC. Information Fields - Name, Title, Email, Phone Numbers, Company Name, and Company Details like Physical Address, Web Address, Revenue Size, Employee Size and industry. We also have other technology users like Informatica, Cognos, Microstrategy, Teradata, and Pentaho. We can provide titles like CIO, CTO, IT VP, IT Director, IT Manager, IT Head, etc. Please let me know your thoughts on it. Regards Anna Peterson Digital Data Co-Ordinator To remove please reply with "Opt-Out" in the subject line
Re: HAProxy loses stick tables on reload
On 12.03.2015 19:00, Lukas Tribus wrote: >> Hi, >> until a moment ago I was under the impression that when performing a >> reload using the init script (which uses the -sf option for the reload) >> the stick tables would survive but apparently I was mistaken. >> >> Is there a better way to perform a graceful restart that maintains the >> stick table or a way to manually dump+reload the table so that sessions >> survive the reload? > > Did you declare you local host in the peers section? If I recall correctly, > that will make sure that the stick tables are synched form the old to the > new process. Unfortunately that leads to an error: [ALERT] 070/192546 (2839) : Proxy 'back1': peers can't be used in multi-process mode (nbproc > 1). Is this a hard limitation? I only use multi-process mode for a ssl-offloading frontend. This forwards to a http frontend bound to one process and that uses a backend also bound to that same process. Regards, Dennis
RE: HAProxy loses stick tables on reload
> Hi, > until a moment ago I was under the impression that when performing a > reload using the init script (which uses the -sf option for the reload) > the stick tables would survive but apparently I was mistaken. > > Is there a better way to perform a graceful restart that maintains the > stick table or a way to manually dump+reload the table so that sessions > survive the reload? Did you declare you local host in the peers section? If I recall correctly, that will make sure that the stick tables are synched form the old to the new process. Lukas
HAProxy loses stick tables on reload
Hi, until a moment ago I was under the impression that when performing a reload using the init script (which uses the -sf option for the reload) the stick tables would survive but apparently I was mistaken. Is there a better way to perform a graceful restart that maintains the stick table or a way to manually dump+reload the table so that sessions survive the reload? Regards, Dennis
Élu Produit de l'Année, Satisfait ou Remboursé
** Vous pourrez exercer vos droits d´accès, annulation, rectification et opposition concernant vos données à caractère personnel, en cliquant * annulation //www.mdirector.com/track/pre-unsubscribe/category/EMAIL/empId/26225/subId/15/listId/11/conId/70218/signature/a01dab6d06f661870779928fc3b6017b/conEmail/haproxy@formilux.org/conMovil/-
Re: [PATCH] Compress HTTP responses with status codes 201,202,203 in addition to 200
On Wed, Mar 11, 2015 at 5:25 PM, Willy Tarreau wrote: > Your mailer has wrapped long lines. You'll have to configure it to prevent > it from doing so. This time I could fix it, it wasn't difficult. I will do that in the future, thanks for munging it for me this time.
Re: Debian (wheezy) official backport stuck at 1.5.8?
On 10 March 2015 at 16:36, Vincent Bernat wrote: > ❦ 10 mars 2015 15:48 GMT, Jonathan Matthews : > >> http://backports.debian.org/wheezy-backports/overview/ reports that >> it's up to date with 1.5, but is only making 1.5.8 available. Does >> anyone have any insight into why this might be and how/if one might >> help the situation? > > To be in "wheezy-backports" a package has to be in "jessie" (the next > version of Debian). Currently, "jessie" is frozen because the release is > imminent, so it is not possible to push newer versions. Once "jessie" is > released, it will be possible to get more recent versions for "wheezy" > through "wheezy-backports-sloppy" (or "jessie-backports" if you upgrade > to "jessie"). > > Also note that critical fixes have been integrated in this version (in > "wheezy-backports"). See the changelog: > > https://tracker.debian.org/media/packages/h/haproxy/changelog-1.5.8-2~bpo70%2B1 > > Once 1.6~dev1 is released, I will push more repositories to give more > choices (1.4, 1.5, 1.6, all distributions, "stable" or "latest" > versions). Thank you, that's cleared it up. I had wondered if it was jessie-related - it's good to get confirmation :-) Jonathan
Re: Debian (wheezy) official backport stuck at 1.5.8?
❦ 10 mars 2015 15:48 GMT, Jonathan Matthews : > http://backports.debian.org/wheezy-backports/overview/ reports that > it's up to date with 1.5, but is only making 1.5.8 available. Does > anyone have any insight into why this might be and how/if one might > help the situation? To be in "wheezy-backports" a package has to be in "jessie" (the next version of Debian). Currently, "jessie" is frozen because the release is imminent, so it is not possible to push newer versions. Once "jessie" is released, it will be possible to get more recent versions for "wheezy" through "wheezy-backports-sloppy" (or "jessie-backports" if you upgrade to "jessie"). Also note that critical fixes have been integrated in this version (in "wheezy-backports"). See the changelog: https://tracker.debian.org/media/packages/h/haproxy/changelog-1.5.8-2~bpo70%2B1 Once 1.6~dev1 is released, I will push more repositories to give more choices (1.4, 1.5, 1.6, all distributions, "stable" or "latest" versions). -- Patch griefs with proverbs. -- William Shakespeare, "Much Ado About Nothing"
Debian (wheezy) official backport stuck at 1.5.8?
Hi all - http://backports.debian.org/wheezy-backports/overview/ reports that it's up to date with 1.5, but is only making 1.5.8 available. Does anyone have any insight into why this might be and how/if one might help the situation? Cheers, Jonathan
