Hi Willy, Thank you for the response and for all your excellent work on HAproxy. I just started working with it this week but I've quickly come to appreciate and enjoy working with it.
I tried moving the -L before the -f and there was no change in the behavior. Thank you, Mike On Wed, Jan 13, 2016 at 1:10 AM, Willy Tarreau <[email protected]> wrote: > Hi Mike, > > On Tue, Jan 12, 2016 at 02:53:21PM -0600, Mike Pastore wrote: > > Hi all, > > > > I'm running HAproxy 1.6.3 on Ubuntu Server 14.04 LTS. I'm having a very > > minor issue with my peer configuration. Essentially, even though I'm > > specifying -L peername on the command line, it still seems to be looking > > for a peer named hostname in the configuration, and I get the following > > warning on startup: > > > > [WARNING] 011/202228 (6257) : Removing incomplete section 'peers > > edgeservers' (no peer named 'atl-edge-000'). > > > > > > The quick fix is to just set the names of the peers to the local > hostnames, > > but I have a naming scheme that I'd like to preserve. Is it safe to > ignore > > this warning? Are there any other options to resolve this problem? Thanks > > in advance. > > > > Here's the startup command: /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg > > -D -p /var/run/haproxy.pid -L edge_000 > > It's not normal, it should work. Furthermore I'm using the same method > when testing foreign configs. > > Could you please check what happens if you set -L *before* -f ? I don't > remember if the local peer name is resolved during the parsing or at > the end. It could be an explanation. > > Willy > >
