Hi Pavlos! On Thu, Dec 07, 2017 at 07:16:54PM +0100, Pavlos Parissis wrote: > Hi, > > OK, I haven't read the ML for ~2 weeks and a quick scan didn't reveal > anything. > So, here I am asking something that may have been addressed already. > > Today, I decided to switch my dev env to haproxy-1.8 using current master and > I > started haproxy in the same way as I have been doing with older releases: > > sudo ./haproxy -f /etc/haproxy/haproxy-ams4-dc.cfg > [WARNING] 340/173007 (3104) : parsing [/etc/haproxy/haproxy-ams4-dc.cfg:103] > : a > 'http-request' rule placed after a 'use_backend' rule will still be processed > before. > > above it didn't return and wasn't printing, expect the warning. I curled > against > the IPs and got back connection error, see attached file for process output, > lsof > info, build verion and haproxy.cfg. > > I also started in the way it is mentioned in section 3 of management document: > sudo ./haproxy -f /etc/haproxy/haproxy-ams4-dc.cfg -D -p > /run/haproxy-ams4.pid > -sf $(cat /run/haproxy-ams4.pid) > cat: /run/haproxy-ams4.pid: No such file or directory > [WARNING] 340/173007 (3104) : parsing [/etc/haproxy/haproxy-ams4-dc.cfg:103] > : a > 'http-request' rule placed after a 'use_backend' rule will still be processed > before. > > but same result, haproxy didn't return and I had to CTRL-C it. > > I am pretty sure I am doing something stupid but I can't find it. > > Any ideas?
It looks like it doesn't finish to startup in fact. Are you seeing it spin on the CPU maybe ? Otherwise probably that starting it by hand in gdb and stopping it to see what it's doing will help. Cheers, Willy
