Am 22.02.2018 um 13:00 schrieb Frank Schreuder:
> I'm running haproxy 1.8.4 with a heavy work load.
> For some reason some workers die every now and then with the following error
> in the log:
> Feb 22 05:00:42 hostname haproxy: [ALERT] 052/045759 (9950) : Current
> worker 3569 exited with code 134
Code 134 implies the worker was killed with SIGABRT. You could check
whether there is a core dump.
When grepping through the code I notice one abort() in cache.c that
could possibly be executed in production. Are you using the new cache
that was added in haproxy 1.8?