Re: Problem starting HaProxy after reboot

> I don't know the startup sequence of systemd, but if haproxy happens to > be stared before the network it could definitely explain it. At the very > least you could enable net.ipv4.ip_nonlocal_bind to let it start even > when the IP addresses are missing, it would help a lot. OK, I've done that

Re: Problem starting HaProxy after reboot

>>> Are you sure the IPs configured in frontends are available during boot? >> >> Well, that's exactly what I don't know. Why shouldn't they? > > I don't know, but I think it is better to find out. But, it could be > unrelated to the problem. Here is what is in the bootlog before the HaProxy serv

Re: Problem starting HaProxy after reboot

On Tue, Nov 22, 2016 at 11:31:43AM +0100, Pavlos Parissis wrote: > On 22/11/2016 10:09 , Jürgen Haas wrote: > >> What do you mean by 'not operating at all'? > > > > It doesn't respond to requests. > > > >> Are you sure the IPs configured in frontends are available during boot? > > > > Well,

Re: compiling ip6range on centos7

Hi Jarno, On Tue, Nov 22, 2016 at 09:58:30AM +0200, Jarno Huuskonen wrote: > Hi, > > Does anybody else have problems compiling contrib/ip6range/ip6range.c > on centos7 ? > Compile fails with: > ip6range.c:31:3: error: ???struct in6_addr??? has no member named ???in6_u??? > a->in6_u.u6_addr32[0]

Re: [PATCH] MEDIUM : regex : draft of pcre2 support

I admit I did not spend time on this part, especially I did most of the development on OpenBSD where pcre2 is compiled without jit support (due to sljit W^X "policy violation", I believe a couple of security oriented linux distros do the same ...), plus couple of quick tests on ubuntu. Small detai

rewrite and redirect with haproxy

Hi Guys, We have a tough url rewrite we are struggling with: I want http://foo.bar.bin/ blah.com to redirect to http://foo-bar-bin. blah.com I want that last dash-domain to also redirect to SSL. The order is important. B

Re: Problem starting HaProxy after reboot

On 22/11/2016 10:09 πμ, Jürgen Haas wrote: >> What do you mean by 'not operating at all'? > > It doesn't respond to requests. > >> Are you sure the IPs configured in frontends are available during boot? > > Well, that's exactly what I don't know. Why shouldn't they? I don't know, but I think it

Re: [PATCH] MEDIUM : regex : draft of pcre2 support

Hi David, On Mon, Nov 21, 2016 at 09:42:10PM +, David CARLIER wrote: > Hi, > > this patch attempts to bring pcre2 support to address the fact that pcre2 > is installed more and more over pcre due to its security flaws. If > accepted, it will be for 1.8, but I think somehow this is the good ti

Re: Problem starting HaProxy after reboot

> What do you mean by 'not operating at all'? It doesn't respond to requests. > Are you sure the IPs configured in frontends are available during boot? Well, that's exactly what I don't know. Why shouldn't they? It's a shared hosting environment like with the other HaProxy hosts as well, just th

Re: Problem starting HaProxy after reboot

On 22/11/2016 09:43 πμ, Jürgen Haas wrote: > Hi all, > > we do run HaProxy on 4 different hosts, all of which got configured by > Ansible the same way and for 3 of them I don't have any issues. On one > of them - which runs on Ubuntu 16.04 and the others on older version - > starting HaProxy after

Problem starting HaProxy after reboot

Hi all, we do run HaProxy on 4 different hosts, all of which got configured by Ansible the same way and for 3 of them I don't have any issues. On one of them - which runs on Ubuntu 16.04 and the others on older version - starting HaProxy after reboot is failing. Browsing the journal I found the l