Possible dead lock

[Slewrate]

Hi there,

Now and then, the website stops respondig and this error appears on the OLS logs:

No request delivery notification has been received from LSAPI application, possible dead lock.

I did try the fixed suggested here:

Possible dead lock [LSAPI application] - Help | Page 2 | OpenLiteSpeed Community and News

But nothing changed with that.

What does possible dead lock exactly mean?

Thanks
Alex

 

[Cold-Egg]

Hi Alex,
Possible to get the output of "top" command when the issue happens again?

 

[Slewrate]

Hi,

I managed to solve (it seems) the issue by applying:

maxConns 500
env PHP_LSAPI_CHILDREN=500
env LSAPI_AVOID_FORK=1
env LSAPI_SLOW_REQ_MSECS=2000 [this is to monitor bad PHP scripts]
env LSPHP_Workers=50

However, now what happens is the following:

Every now and then, I get "The sever did not respond" on the browser, while you're browsing the website. The connection is reset.

Thanks
Alex

 

[Cold-Egg]

Check the server load, if it's not a powerful server, please reduce both maxConns and PHP_LSAPI_CHILDREN numbers.

 

[Slewrate]

It's a bare-metal 2388G server with 128GB of ram and nvme drives.

I have reduced these values to:

  maxConns                100
  env                             PHP_LSAPI_CHILDREN=100
  env                             LSAPI_AVOID_FORK=1
  env                             LSAPI_SLOW_REQ_MSECS=2000
  env                             LSPHP_Workers=50

and I have also done:

memSoftLimit            4096M
  memHardLimit            8192M

But this keeps appearing on the logs:

[UID:1002][1088285] Reached max children process limit: 100, extra: 0, current: 100, busy: 100, please increase LSAPI_CHILDREN.

 

[Cold-Egg]

I see, it means you need to increase the maxConns and PHP_LSAPI_CHILDREN numbers.

If the "The sever did not respond" on the browser, while you're browsing the website. The connection is reset. " still exists, please submit to support@litespeedtech.com for further support.