Comment 3 for bug 1882504

Hi,

a status update: as discussed inthe IRC, This issue seams related to the setup itself a process called ksocket is eating all the ram and cpu of the machine while the stack is happening. This particular server seams to be one of the oldest setups we have, and have issues with newer operating systems (ubuntu > 18, fedora > 29, centos > 7.7). so i am going to try it on another setup now and see if there is any issues there.

Thanks.