Hi Maksim, On Tue, Apr 16, 2019 at 07:28:28AM +0200, Willy Tarreau wrote: > > So I agree upon another thread activity. The unique thing about > > these servers - all of them use haproxy-agent to set up weights of their > > backends. Other instances with no haproxy-agent in their configs don't > > produce cores. > > Great, this will definitely help me validate my hypothesis. I'm not sure > the fix will be easy but I'm back to this.
OK so I could finally figure what the problem was and fix it. The upper level function used to expect to be called with the server's lock held while it is responsible for choosing the server... As you can expect, it didn't have good chances to resist to concurrency. I've merged the fix into 2.0-dev and backported it into 1.9-maint. Feel free to update to latest 1.9 git or snapshot. Thank you very much for your report, it was extremely helpful! Willy
