Re: Rpm for Haproxy 2.0
On 13/11/2019 13:51, N Seto wrote: Hi, We are looking for the official / reputable RPM for haproxy v 2.0 . Can you suggest where we can obtain this? Best regards, N Seto There aren't any official rpm's for haproxy, but here's a repo for centos7: http://haproxy.hongens.nl/ Angelo.
Re: Does anyone still use examples/haproxy.spec ?
On 19-06-2019 04:08, William Lallemand wrote: That's an interesting feedback. Indeed the changelog was up to date because of the automated release script, but the latest change on this file was 4 years ago and it only updated the URLs in the file. The spec was using an old TARGET, with few features, and was never updated to work on recent RHEL release. If we want to reintroduce it, we really need to update it. Regards, I only read this list with half an eye, but in case anyone is interested, I got some updated spec files for recent haproxy versions here: https://github.com/AxisNL/haproxy-rpmbuild/tree/master/SPECS (not updated for a while though) -- -- met vriendelijke groet, Angelo Höngens
Re: Problem installing 1.8.7 -- systemd changes
On 13-04-2018 03:58, Shawn Heisey wrote: I have a script on my system that I use to handle compiling and installing a new haproxy version. That script has "EXTRA=haproxy-systemd-wrapper"on the line that does the install. It looks like that's no longer part of haproxy, and that the systemd service definition (included in contrib) just calls haproxy directly. USE_SYSTEMD must be set on the compile command when using the contrib systemd script, and the systemd development library must be present. But I don't see anything in CHANGELOG or README that talks about it at all, and definitely nothing saying that the wrapper has been removed, and nothing mentioning the new compile requirements. Was there somewhere else that I should have looked for information about how to get 1.8 working with systemd? Shawn, I ran into the same thing a while back. I don't know what OS you are using, but you might want to check these SPEC files I wrote for inspiratoin. I'm no expert packager, but it works for me: https://github.com/AxisNL/haproxy-rpmbuild I upload the packages I build here: https://haproxy.hongens.nl -- -- met vriendelijke groet, Angelo Höngens
Re: [ANNOUNCE] haproxy-1.8.7
On 08-04-2018 15:33, Aleksandar Lazic wrote: Am 07.04.2018 um 00:39 schrieb Willy Tarreau: Subject: [ANNOUNCE] haproxy-1.8.7 To: haproxy@formilux.org Hi, HAProxy 1.8.7 was released on 2018/04/07. It added 2 new commits after version 1.8.6. Updated images: https://hub.docker.com/r/me2digital/haproxy18/ https://hub.docker.com/r/me2digital/openshift-ocp-router-hap18/ As have the centos rpm packages: https://haproxy.hongens.nl Have a nice Sunday you all ;) -- met vriendelijke groet, Angelo Höngens
Re: haproxy 1.8 on CentOS with wrapper and SystemD
On 02-02-2018 17:44, garb...@gmx.de wrote: I`m having problems with running haproxy 1.8 on CentOS 7.4 and originally I planned to post my setup, logs and more. But while thinking about this I started to doubt that what I am trying is correct. Let me explain what I'm doing, perhaps there is a better approach which solves my problem automatically. I start with a plain install of CentOS 7.4 on which I "yum install" the current version that CentOS provides (1.5). Then I replace /usr/sbin/haproxy with a statically linked version of haproxy 1.8.3 (statically because I want a newer version of openssl 1.1 for example). This new haproxy runs fine as long as I don't run it with systemd. When I do a "systemctl start haproxy" it silently fails to load haproxy. So my basic first question is: shall I try to (with your help) fix this or should I remove the then current haproxy wrapper and have systemd run haproxy directly ? If necessary / helpful I can provide information about my logs and the way I compile haproxy, but first I wanted to hear your opinions. I would take the prebuilt packages in this repo I built: https://haproxy.hongens.nl Or look at the github page for the spec files and systemd patches if you want to build them yourself ;) Doing an rpm install and then modifying files sounds like a bad idea to me, I want consistency. If rpm -q haproxy tells me I'm running 1.5, I want to have 1.5 running, and vice versa. -- met vriendelijke groet, Angelo Höngens
Re: haproxy without balancing
Hey Aleksandar, On 05-01-2018 22:05, Aleksandar Lazic wrote: We run a lot of balancers with varnish+hitch+haproxy+corosync for high-available loadbalancing. Perhaps high-availability is not a requirement, but it's also nice to be able to do maintenance during the day and have your standby node take over.. Just for my curiosity why hitch and not only haproxy for ssl termination? I use varnish as a single point of entry for requests and for caching. I guess because it's a really good product, and we've been using it for a long time. It has some custom business logic built in our vcl as well, and allows for a lot of http magic. I got training on varnish tuning and monitoring, and all of our scripts revolve around varnish and its logs. And they have very cool real-time analysis tools like varnishlog, varnishhist, varnishstat, etc. Varnish passes all requests to a local haproxy instance, which passes requests to the right backends based on hostname. So we use haproxy for balancing to backends. When the time came we needed ssl termination, I wanted a simple solution that does that one thing well, and I still wanted varnish as entry point. We played around with different products (squid, nginx), but then the varnish team forked stud and called it hitch. And the nice thing is almost all varnish users use hitch for ssl termination, and the varnish team is willing to offer commercial support for both. I've been thinking about different setups as well, such as running one haproxy instance for ssl termination, passing requests to varnish and then pass it to another instance of haproxy that sends requests to the backends, but I think my current setup serves us best and we use the best tool for the jobs at hand. I think hitch is a great ssl terminator, varnish is a great cache/spoonfeeder, and haproxy is the best balancer. -- met vriendelijke groet, Angelo Höngens
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 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 over 4000 lines of acl rules. and I do not know if haproxy can deal with that or if it will slowdown request to much. Maybe there are other options I did not think about? For me the second config is the best option because of the single IP, but i do not know if haproxy can handle 2000 acl rules. I would choose the second option. I don't think the 2000 acls is a problem. I've been running with more than that without any problems. A single point of entry is easiest. We run a lot of balancers with varnish+hitch+haproxy+corosync for high-available loadbalancing. Perhaps high-availability is not a requirement, but it's also nice to be able to do maintenance during the day and have your standby node take over.. -- met vriendelijke groet, Angelo Höngens
Re: Haproxy 1.8 version help
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 compilation fails. You can disable thread support, by adding USE_THREAD= to the make command (nothing comes after the equal sign): I'm no packaging expert, but 1.8 seems to build fine on my CentOS6 build box without any errors. I'm running gcc version 4.4.7 20120313 on CentOS 6.9. Here's my spec file for building RPM packages: https://github.com/AxisNL/haproxy-rpmbuild/blob/master/SPECS/haproxy-1.8.3.el6.spec Am I doing something strange?? :-) -- met vriendelijke groet, Angelo Höngens
centos packages built
FYI, I built haproxy packages for centos6 and centos7, and intend to keep the repo up to date. I run haproxy on dozens of machines, and I manage them using spacewalk. So I want recent RPM's ;) See https://haproxy.hongens.nl/ I built the spec files by gathering them from around the internet and adjusting them for init.d and systemd. I wrote a python script to glue together rpmbuild and other stuff. Here's the code and spec files: https://github.com/AxisNL/haproxy-rpmbuild I'm no packaging guru, so if any of you guys notice me doing strange stuff, let me know! Have a nice Christmas, or whats left of it! -- met vriendelijke groet, Angelo Höngens
