Hi all,

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[9950]: [ALERT] 052/045759 (9950) : Current 
worker 3569 exited with code 134

We never saw this behavior on haproxy 1.7.9, is this a know issue? I'm not able 
to reproduce it as I don't know which request causes this issue.
I'm using "master-worker no-exit-on-failure" now, to lower the impact, 
otherwise it would kill all workers and a restart of haproxy takes some time 
with a lot of SSL certificates.

Another issue I noticed is a much higher memory usage on 1.8.4 compared to 
1.7.9. Maybe growing memory over time is a side effect of seamless reloads?

Thanks,
Frank

Reply via email to