Just created an issue now: https://github.com/haproxy/haproxy/issues/671
Thanks, Sander
On 6/9/20 2:07 PM, Илья Шипицин wrote:
it is a good report. backtraces are very useful
is there github issue filled for it ? if no, can you please create one ?
I hope, it won't be lost that way
вт, 9 июн.
it is a good report. backtraces are very useful
is there github issue filled for it ? if no, can you please create one ?
I hope, it won't be lost that way
вт, 9 июн. 2020 г. в 15:13, Sander Hoentjen :
> Is there anybody with a clue? If I need to supply more info I can do so,
> of course.
>
> Kin
Is there anybody with a clue? If I need to supply more info I can do so,
of course.
Kind regards,
Sander
On 6/2/20 4:12 PM, Sander Hoentjen wrote:
Hi list,
Some time ago (around april 21st) we were using 1.8.13 and we switched
from nbthread = 1 to nbthread = 4
This seemed stable for us, b
Hi list,
Some time ago (around april 21st) we were using 1.8.13 and we switched
from nbthread = 1 to nbthread = 4
This seemed stable for us, but 2 weeks ago we started seeing hangs (100%
CPU haproxy processes)
We then updated to haproxy 2.0.14. The hangs are gone, but instead we
see disapp
4 matches
Mail list logo