cPFence maybe because the issue is already resolved, and I am looking for a solution to another problem ?
xyzulu
The issue can be replicated easily, I have a website that runs out of memory, and not allowed to swap, as long as the website (with approximately 4000 users online ) has not enough ram 503 errors are given (which is perfectly normal reaction ) .
At this point the threshold of litespeed is met 1 503 per second , for 30 seconds and litespeed should gracefully restart.
It doesn't restart, I can tell it doesn't restart by checking the uptime on litespeed realtime stats
As for the website I already solved the issue by increasing the memory to a higher limit which makes sense for such traffic .
