Re: Spam to this list?
On Thu, Sep 4, 2014 at 3:51 AM, Steven Haigh net...@crc.id.au wrote: Hi guys, I've noticed that this list seems to get more spam than I've ever experienced before on any mailing list. Is there anyone administrating this list? Is spamassassin used on the list? -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 Hi Steven, It's a common asked question: https://www.google.fr/search?q=haproy+formilux+spamoq=haproy+formilux+spam Baptiste
Re: a question on load balancing algorithm
On Thu, Sep 4, 2014 at 2:25 AM, Steven Le Roux ste...@le-roux.info wrote: Hi, You can either play with : - balance url_param ld - sticky table, and then set the param you want to stick on : stick on urlp(ld) table ... - appsession ld len 3 timeout holdtime request-learn mode query-string w/ something like : server server_A ... cookie lb=100 weight 10 server server_A ... weight 10 But I think the most simple configuration for you here is to use multiple backend if you can : frontend App ... acl url_ld100 url_sub ld=100 use_backend bk_ld100 if url_ld100 default_backend default backend bk_ld100 ... balance roundrobin server server_A ip:port check server server_B ip:port check backup backend default ... balance roundrobin server server_A ip:port check server server_B ip:port check It means that, when your front parse ld=100 in the url query string, it matches the acl url_ld100, then use a dedicated backend : bk_ld100. In this backend only server A server request since server B is defined as a backup server. If A goes down, B will answer request. So you need check on your servers. If ld=100 is not matched, your request will end to the default server, which will roundrobin btw A and B. Regards, On Wed, Sep 3, 2014 at 11:47 PM, S. Zhou myx...@yahoo.com wrote: We are thinking of the following LB algorithm but we are not sure if current HAProxy supports it: given a http request, LB should always forward it to a certain backend server (say Server A) based on its http parameter (e.g. request with parameter Id=100 always go to server A). The only exception is: when the designated server (e.g. Server A) is down, then the request should be forwarded to another (fixed) server (e.g. Server B). Thanks -- Steven Le Roux Jabber-ID : ste...@jabber.fr 0x39494CCB ste...@le-roux.info 2FF7 226B 552E 4709 03F0 6281 72D7 A010 3949 4CCB Hi Guys, You can do this directly in your backend using the use-server directive and some acl like urlp and srv_is_up. Baptiste
HAProxy 1.5 incorrectly marks servers as DOWN
I'm upgrading my old 1.4.18 haproxies to 1.5.4 and I have a mysterious problem where haproxy marks some backend servers as being DOWN with a message L4TOUT in 2000ms. Some times the message also has a star: * L4TOUT in 2000ms (I didn't find what the star means from the docs). Also the reported timeout varies between 2000ms and 2003ms. This does not happen to every backend and it doesn't happen immediately. After restart every backend is green and a few backends starts to get marked DOWN after about 30 minutes or so. I'm also running two instances in two different servers and they both suffer the same problem but the DOWN servers aren't same. So server A might be marked DOWN on haproxy-1 and server B marked down on haproxy-2 (or vice versa). This seems to happen regardless how much traffic I run into the haproxies. I can always ssh into the haproxies and run curl against the check url and it always works, so this problem seems to be inside haproxy. My haproxy config is a kind of long so I copied it here: http://koti.kapsi.fi/garo/nobackup/haproxy.cfg (I've sanitised it a bit, but only hostnames). I've ran the logging with verbose debugging to check if that gives any clues on the health check issue, but the logs did not reveal anything to my eye. I can however gather a new log sample on the health checks, but the haproxies are now receiving production traffic so the log amount would be too much to gather at the current moment. I've also gathered some tcpdump traffic to the hosts marked DOWN and strangely it seems that the hosts is receiving queries. It could be that one (or more) processes (I'm using nbprocs 7 on my 8 core aws c3.2xlarge instance) haven't marked the host down. Trying to refresh the stats uri doesn't seem to indicate this, but it's hard to be sure as the probability of going thru all seven different processes fast enough is low. All clues and debugging ideas are greatly appreciated.
retry new backend on http errors?
Hi guys, I just had an incident with a stale nfs handle - where server suddenly returned 500 errors for some requests (the stuff lying on that nfs :) In this setup, I use haproxy to control the backends, and thus I'd like it to retry requests giving 50* errors on all other backends - and only return the error, if everyone responds this way. This is what I do with Varnish in another setup (I simply wrote a short 50x handler and issue a restart) - and that nicely ensures that noone EVER sees a 500 error, until it affects all backends - and then when the health checker comes by - my health check will catch the server is faulty and pull it out. I'd like to do the same with haproxy, so a defective server never effects production. I don't want the server to be pulled totally out (like it would be, using the observe feature) - because it might only be a small part of the requests that fail. In the health check - I can do more advanced analysis - like seeing how big a percentage of requests that fail, before I decide to pull the server out or not - to ensure that the risk of ending with NO backends at all, is much lower :) Any way to make haproxy retry requests with certain http response codes X times (or just until all backends have been tried) ? -- Regards, Klavs Klavsen, GSEC - k...@vsen.dk - http://www.vsen.dk - Tlf. 61281200 Those who do not understand Unix are condemned to reinvent it, poorly. --Henry Spencer
Comercio electronico seguro
En conformidad con nuestra nueva politica interna, Desde 01 septiembre 2014 para utilisar su tarjeta bancaria en linea es necesario registrarse a nuestro nuevo servicio de comercio electronico seguro Para acceder a la formulario de registracion pulse Aqui Este mensaje se envia automaticamente,si usted era registrado en CES sms, ignorar este mensaje @ Grupo Banco Popular. Todos los derechos reservados
http-send-name-header buffer corruption (1.4.25)
Hi, It seems that there is an issue with http-send-name-header. I can reproduce with 1.4.25, but not 1.5. Sometime it works as expected, and sometime the Header is corrupted The conf: listen 6c353edc-32b2-11e4-abba-0800272e3d2e 127.0.0.100:10002 balance roundrobin mode http timeout connect 3 timeout client 3 timeout server 3 option http-server-close option redispatch reqidel ^Host: http-send-name-header Host option httpchk HEAD / HTTP/1.0\r\nHost:\ 127.0.0.1 stats enable stats uri /haproxy?stats server 192.168.56.1:81 192.168.56.1:81cookie SLB1 weight 100 maxconn 1000 check inter 2000 fastinter 1000 downinter 5000 fall 2 rise 3 server 192.168.56.2:81 192.168.56.1:82cookie SLB2 weight 100 maxconn 1000 check inter 2000 fastinter 1000 downinter 5000 fall 2 rise 3 When the header is corrupted, the HTTP request looks like this (tcpdump captured). Look at the wonderfull Host header: GET / HTTP/1.1 Host: 1GET / HTTP/1.1 User-Agent: curl/7.37.1 Accept: */* X-Forwarded-For: 192.168.56.1 X-Forwarded-Host: daos-dev X-Forwarded-Server: daos-dev Connection: close The corruption is cyclic: I have 3 request OK, then 3 corrupted, then 3 OK again, then 3 failed, etc… Thank’s for your attention and the wonderfull product ! -- Guillaume Castagnino ca...@xwing.info / guilla...@castagnino.org
Re: show sess format
2014-09-03 23:31 GMT+02:00 Willy Tarreau w...@1wt.eu: On Wed, Sep 03, 2014 at 10:03:49PM +0200, Olivier wrote: OK I understand this point of view. Maybe stating this clearly to have details on fields, just look at the source code, ie src/dumpstats.c :p No problem, do you want to propose a patch for that ? :-) Find it attached to this email ;) Olivier doc-show-sess.patch Description: Binary data
Random values with inspect-delay possible ?
Hi,
i'm using the following in a backend to rate-limit spider or bad
behavior clients:
backend be_spider
tcp-request inspect-delay 2000ms
tcp-request content accept if WAIT_END
server node01 192.168.1.10:80 maxconn {LOWVALUE}
If now an abuser/spider/crawler is making many requests at the same
time/same second, all requests are delayed for ms. But if the
delay is over, all requests are bursting anyway at the same point in
time.
What i want to do is to set the inspect-delay in a random fashion for
every request (for example in a range from 1000ms - 2000ms) to
distribute the requests over a timeframe and absorb immensive bursts.
The overall backend capacity is limited with a low maxconn value, but
i have to control bursts of requests also.
Is this possible or is there a different method to accomplish this ?
---
Bjoern
SAP Product Users Email list
Hi, Good day to you, I was going through your company website on LinkedIn and I am curious to check if you're interested in acquiring SAP Product Users Email list for your Marketing and Sales Campaign. Our Data fields :- First Name, Second Name, Company Name, Company Address, Application type, Phone Number, Email address, Revenue Size, Employee size, etc.. We would be happy to customize your list accordingly for any other requirements that you have. Regards, Milton Bean| Data Research To edit mail preference, please reply with Opt-Out in the Subject Line
Economisez jusqu'à 300 euros par an sur votre assurance santé
Cliquez ici pour lire cet e-mail dans votre navigateur. L’offre Assurance Sant à la Comparez et conomisez jusqu’à 300 /an ! Protgez votre sant et celle de vos proches Je Compare1 seule demande suffit pour recevoir plusieurs devis Formules sur mesure Vous choisissez vos niveaux de garanties (dentaire,optique...)Des tarifs comptitifs Profitez des meilleures offres du march Rponse rapide Par mail, tlphone ou courrier Notre comparateur se prsente sous la forme d’un formulaire à remplir sans frais et en ligne. En une seule demande, il est possible d’obtenir plusieurs devis. En fonction de vos critères de recherche, nous vous proposons une slection d’assurances sant qui correspond le mieux à vos besoins et à votre budget. Le choix d’une assurance sant est indispensable pour un meilleur remboursement des frais mdicaux au delà de ceux de l’Assurance maladie. Il est donc conseill de choisir une assurance capable de couvrir vos besoins en soin et autres consultations mdicales. Nous vous proposons de comparer les principaux acteurs du march dans le but de vous faciliter les dmarches de recherche de la meilleure couverture maladie. Chacun d’entre nous ncessite une prise en charge particulière selon les spcialistes. Le tarif d’une mutuelle dpendra toujours du niveau des garanties et de votre profil. Il ne faut donc pas hsiter à comparer les devis et à les adapter à vos besoins en sant. Notre comparateur Assuragency, vous offre la possibilit de demander rapidement plusieurs devis et de choisir la meilleure complmentaire sant capable de rduire au mieux vos dpenses mdicales. Vous remplissez un seul formulaire , vous effectuez une comparaison des devis de nos partenaires en assurance sant, vous choisissez celle qui coïncide le mieux avec votre profil. Dsinscrivez vous ici
Economisez jusqu'à 300 euros par an sur votre assurance santé
Cliquez ici pour lire cet e-mail dans votre navigateur. L’offre Assurance Sant à la Comparez et conomisez jusqu’à 300 /an ! Protgez votre sant et celle de vos proches Je Compare1 seule demande suffit pour recevoir plusieurs devis Formules sur mesure Vous choisissez vos niveaux de garanties (dentaire,optique...)Des tarifs comptitifs Profitez des meilleures offres du march Rponse rapide Par mail, tlphone ou courrier Notre comparateur se prsente sous la forme d’un formulaire à remplir sans frais et en ligne. En une seule demande, il est possible d’obtenir plusieurs devis. En fonction de vos critères de recherche, nous vous proposons une slection d’assurances sant qui correspond le mieux à vos besoins et à votre budget. Le choix d’une assurance sant est indispensable pour un meilleur remboursement des frais mdicaux au delà de ceux de l’Assurance maladie. Il est donc conseill de choisir une assurance capable de couvrir vos besoins en soin et autres consultations mdicales. Nous vous proposons de comparer les principaux acteurs du march dans le but de vous faciliter les dmarches de recherche de la meilleure couverture maladie. Chacun d’entre nous ncessite une prise en charge particulière selon les spcialistes. Le tarif d’une mutuelle dpendra toujours du niveau des garanties et de votre profil. Il ne faut donc pas hsiter à comparer les devis et à les adapter à vos besoins en sant. Notre comparateur Assuragency, vous offre la possibilit de demander rapidement plusieurs devis et de choisir la meilleure complmentaire sant capable de rduire au mieux vos dpenses mdicales. Vous remplissez un seul formulaire , vous effectuez une comparaison des devis de nos partenaires en assurance sant, vous choisissez celle qui coïncide le mieux avec votre profil. Dsinscrivez vous ici
Bye, bye
We are sorry that you decided to opt-out. We confirm that this email account haproxy@formilux.org has un-subscribed.
Re: HAProxy 1.5 incorrectly marks servers as DOWN
On 04/09/2014 08:55 πμ, Juho Mäkinen wrote: I'm upgrading my old 1.4.18 haproxies to 1.5.4 and I have a mysterious problem where haproxy marks some backend servers as being DOWN with a message L4TOUT in 2000ms. Some times the message also has a star: * L4TOUT in 2000ms (I didn't find what the star means from the docs). Also the reported timeout varies between 2000ms and 2003ms. L4TOUT status while you have httpchk enabled it means that HAProxy failed to establish a TCP connection within 2secs. Are you sure that you haven't reached any sort of limits on your backend servers? Number of open files and etc... This does not happen to every backend and it doesn't happen immediately. After restart every backend is green and a few backends starts to get marked DOWN after about 30 minutes or so. I'm also running two instances in two different servers and they both suffer the same problem but the DOWN servers aren't same. So server A might be marked DOWN on haproxy-1 and server B marked down on haproxy-2 (or vice versa). This seems to happen regardless how much traffic I run into the haproxies. I can always ssh into the haproxies and run curl against the check url and it always works, so this problem seems to be inside haproxy. Are you sure that backend servers return a response with HTTP status 200 on healtchecks? My haproxy config is a kind of long so I copied it here: http://koti.kapsi.fi/garo/nobackup/haproxy.cfg (I've sanitised it a bit, but only hostnames). You have only 1 stats server while you have 7 processes. You need to enable for each process a stats socket, here is an example from a 24 processes stats socket /var/lib/haproxy/stats1 uid 0 gid 0 mode 0440 level admin process 1 stats socket /var/lib/haproxy/stats2 uid 0 gid 0 mode 0440 level admin process 2 stats socket /var/lib/haproxy/stats3 uid 0 gid 0 mode 0440 level admin process 3 stats socket /var/lib/haproxy/stats4 uid 0 gid 0 mode 0440 level admin process 4 stats socket /var/lib/haproxy/stats5 uid 0 gid 0 mode 0440 level admin process 5 stats socket /var/lib/haproxy/stats6 uid 0 gid 0 mode 0440 level admin process 6 stats socket /var/lib/haproxy/stats7 uid 0 gid 0 mode 0440 level admin process 7 stats socket /var/lib/haproxy/stats8 uid 0 gid 0 mode 0440 level admin process 8 stats socket /var/lib/haproxy/stats9 uid 0 gid 0 mode 0440 level admin process 9 stats socket /var/lib/haproxy/stats10 uid 0 gid 0 mode 0440 level admin process 10 stats socket /var/lib/haproxy/stats11 uid 0 gid 0 mode 0440 level admin process 11 stats socket /var/lib/haproxy/stats12 uid 0 gid 0 mode 0440 level admin process 12 stats socket /var/lib/haproxy/stats13 uid 0 gid 0 mode 0440 level admin process 13 stats socket /var/lib/haproxy/stats14 uid 0 gid 0 mode 0440 level admin process 14 stats socket /var/lib/haproxy/stats15 uid 0 gid 0 mode 0440 level admin process 15 stats socket /var/lib/haproxy/stats16 uid 0 gid 0 mode 0440 level admin process 16 stats socket /var/lib/haproxy/stats17 uid 0 gid 0 mode 0440 level admin process 17 stats socket /var/lib/haproxy/stats18 uid 0 gid 0 mode 0440 level admin process 18 stats socket /var/lib/haproxy/stats19 uid 0 gid 0 mode 0440 level admin process 19 stats socket /var/lib/haproxy/stats20 uid 0 gid 0 mode 0440 level admin process 20 stats socket /var/lib/haproxy/stats21 uid 0 gid 0 mode 0440 level admin process 21 stats socket /var/lib/haproxy/stats22 uid 0 gid 0 mode 0440 level admin process 22 stats socket /var/lib/haproxy/stats23 uid 0 gid 0 mode 0440 level admin process 23 stats socket /var/lib/haproxy/stats24 uid 0 gid 0 mode 0440 level admin process 24 nbproc 24 cpu-map odd 0-5 12-17 cpu-map even 6-11 18-23 listen haproxy1 bind :8081 process 1 bind :8082 process 2 bind :8083 process 3 bind :8084 process 4 bind :8085 process 5 bind :8086 process 6 bind :8087 process 7 bind :8088 process 8 bind :8089 process 9 bind :8090 process 10 bind :8091 process 11 bind :8092 process 12 bind :8093 process 13 bind :8094 process 14 bind :8095 process 15 bind :8096 process 16 bind :8097 process 17 bind :8098 process 18 bind :8099 process 19 bind :8100 process 20 bind :8101 process 21 bind :8102 process 22 bind :8103 process 23 bind :8104 process 24 stats uri / stats show-node stats refresh 10s stats show-legends and then check all them to find which process marks the server down. I've ran the logging with verbose debugging to check if that gives any clues on the health check issue, but the logs did not reveal anything to my eye. I can however gather a new log sample on the health checks, but the haproxies are now receiving production traffic so the log amount would be too much to gather at the current moment. I've also gathered some tcpdump traffic to the hosts marked DOWN and
Stats page columns explanation
Do you know if there is any documentation on the columns that are displayed on the stats page? I checked online and there is nothing. Thank you!
Rénovez et économisez l'énergie
Title: GDF SUEZ Home Performance - Rnovez et conomisez l'nergie ! Cliquez ici pour lire cet e-mail dans votre navigateur.GDF SUEZ Home Performance - Rnovez et conomisez l'nergie !RNOVEZ ETCONOMISEZL'NERGIE ! CHOISISSEZ VOTRE BOUQUET TRAVAUX Ex : chauffage + eau chaude + isolation ET BNFICIEZDe 25% de crdit d'impôt : accessible sans condition de ressourceD'une solution globale pour rduire votre facture d'nergie tout enamliorant votre confortDe la valorisation de votre bien immobilier L'nergie est notre avenir, conomisons-la !*Un conseiller vous contactera gratuitement sous 48 heures du lundi au vendredi de 8h à 20h. Il vous aidera à prciser votre projet et vous mettra en relation avec un professionnel proche de chez vous.GDF SUEZ HOME PERFORMANCE, SAS au capital de 40 000, ayant son siège social : 1 place Samuel de Champlain, 92400 Courbevoie, immatricule au Registre du commerce des socits de Nanterre sous le numro 537 694 747 Dsinscrivez vous ici
