I actually messed up testing last week; reverting Tim's commit appears to fix it.
On Fri, Apr 3, 2020 at 5:41 AM Willy Tarreau <[email protected]> wrote: > On Fri, Apr 03, 2020 at 02:27:05PM +0200, Willy Tarreau wrote: > > On Thu, Apr 02, 2020 at 12:32:32PM -0700, James Brown wrote: > > > I reverted that commit, but it doesn't appear to have fixed the issue. > > > > > > I also tried adding a stick-table using this peers group to my config > (this > > > test cluster didn't actually have any stick-tables), but it still > fails at > > > startup with the same error. > > > > James, just to confirm, does it fail to start from a cold start or only > > on reloads ? > > I'm trying with this config and this command: > > global > stats socket /tmp/sock1 mode 666 level admin expose-fd listeners > stats timeout 1d > > peers p > peer peer1 127.0.0.1:8521 > peer peer2 127.0.0.1:8522 > > listen l > mode http > bind 127.0.0.1:2501 > timeout client 10s > timeout server 10s > timeout connect 10s > stick-table size 200 expire 10s type ip peers p store server_id > stick on src > server s 127.0.0.1:8000 > > $ ./haproxy -D -L peer1 -f peers.cfg -p /tmp/haproxy.pid > $ ./haproxy -D -L peer1 -f peers.cfg -p /tmp/haproxy.pid -sf $(pidof > haproxy) -x /tmp/sock1 > $ ./haproxy -D -L peer1 -f peers.cfg -p /tmp/haproxy.pid -sf $(pidof > haproxy) -x /tmp/sock1 > $ ./haproxy -D -L peer1 -f peers.cfg -p /tmp/haproxy.pid -sf $(pidof > haproxy) -x /tmp/sock1 > > For now I can't figure how to reproduce it :-/ If you manage to modify > this config to trigger the issue that would be great! > > Willy > -- James Brown Engineer
