Title: PHP Dead lock error
Last modified: May 31, 2022

---

# PHP Dead lock error

 *  Resolved [Vishal Lohar](https://wordpress.org/support/users/vlohar08/)
 * (@vlohar08)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/php-dead-lock-error/)
 * Hi,
    I am using WordPress on Openlitespeed. I am facing a weird problem of PHP
   Deadlock. As I am using Openlitespeed I have already contacted them and this 
   is their response.
 * Response ->
 * >     ```
   >     Hello, Vishal:
   >     Thank you for reaching out.
   > 
   >     the error message means: PHP backend problem, either dead lock, or, all PHP process are running code with infinity looping, long run task. So, new request from server cannot be accepted.
   > 
   >     Basically it is your PHP code issue, not on web server side. You can debug your application code, it is out of our support scope.
   > 
   >     Regards
   >     Jackson
   >     ```
   > 
 * Now, I don’t know how to solve this. When i receive this error, everything stops
   working and this happens at least once in a day. I have to restart the server
   to fix it. Restarting everyday is not a solution.
 * Note: I have replaced my domain with example.com.
 * Error Logs ->
    `2022-05-26 17:32:56.012712 [NOTICE] [20614] [172.70.218.209:14744:
   HTTP2-1#example.com] No request delivery notification has been received from 
   LSAPI application, possible dead lock. 2022-05-26 17:32:56.012725 [NOTICE] [20614][
   172.70.188.87:30146:HTTP2-3#example.com] No request delivery notification has
   been received from LSAPI application, possible dead lock. 2022-05-26 17:32:57.016441[
   NOTICE] [20614] [172.70.189.60:23872:HTTP2-1#example.com] No request delivery
   notification has been received from LSAPI application, possible dead lock. 2022-
   05-26 17:32:58.092400 [NOTICE] [20614] [162.158.48.109:41882:HTTP2-1#example.
   com] No request delivery notification has been received from LSAPI application,
   possible dead lock. 2022-05-26 17:32:59.094557 [NOTICE] [20614] [172.70.189.80:
   20518:HTTP2-1#example.com] No request delivery notification has been received
   from LSAPI application, possible dead lock. 2022-05-26 17:32:59.094586 [NOTICE][
   20614] [172.70.218.153:9476:HTTP2-1#example.com] No request delivery notification
   has been received from LSAPI application, possible dead lock. 2022-05-26 17:32:
   59.094596 [NOTICE] [20614] [162.158.227.133:13268:HTTP2-1#example.com] No request
   delivery notification has been received from LSAPI application, possible dead
   lock. 2022-05-26 17:32:59.094607 [NOTICE] [20614] [172.69.239.161:42358:HTTP2-
   1#example.com] No request delivery notification has been received from LSAPI 
   application, possible dead lock. 2022-05-26 17:33:01.020749 [NOTICE] [20614] [
   162.158.31.187:49086:HTTP2-1#example.com] No request delivery notification has
   been received from LSAPI application, possible dead lock. 2022-05-26 17:33:01.020816[
   NOTICE] [20614] [172.70.246.17:16514:HTTP2-1#example.com] No request delivery
   notification has been received from LSAPI application, possible dead lock. 2022-
   05-26 17:33:02.001378 [NOTICE] [20614] [172.70.218.153:9416:HTTP2-1#example.com]
   No request delivery notification has been received from LSAPI application, possible
   dead lock. 2022-05-26 17:33:02.001408 [NOTICE] [20614] [162.158.235.66:33408:
   HTTP2-1#example.com] No request delivery notification has been received from 
   LSAPI application, possible dead lock. 2022-05-26 17:33:03.048868 [NOTICE] [20614][
   172.70.219.12:13474:HTTP2-1#example.com] No request delivery notification has
   been received from LSAPI application, possible dead lock. 2022-05-26 17:33:06.069176[
   NOTICE] [20614] [172.70.188.211:40576:HTTP2-1#example.com] No request delivery
   notification has been received from LSAPI application, possible dead lock. 2022-
   05-26 17:33:06.069204 [NOTICE] [20614] [172.70.218.209:14744:HTTP2-1#example.
   com] No request delivery notification has been received from LSAPI application,
   possible dead lock. 2022-05-26 17:33:06.069214 [NOTICE] [20614] [172.70.188.87:
   30146:HTTP2-3#example.com] No request delivery notification has been received
   from LSAPI application, possible dead lock. 2022-05-26 17:33:07.036262 [NOTICE][
   20614] [172.70.189.60:23872:HTTP2-1#example.com] No request delivery notification
   has been received from LSAPI application, possible dead lock. 2022-05-26 17:33:
   08.012411 [NOTICE] [20614] [162.158.48.109:41882:HTTP2-1#example.com] No request
   delivery notification has been received from LSAPI application, possible dead
   lock. 2022-05-26 17:33:09.004735 [NOTICE] [20614] [172.70.189.80:20518:HTTP2-
   1#example.com] No request delivery notification has been received from LSAPI 
   application, possible dead lock. 2022-05-26 17:33:09.004760 [NOTICE] [20614] [
   172.70.218.153:9476:HTTP2-1#example.com] No request delivery notification has
   been received from LSAPI application, possible dead lock. 2022-05-26 17:33:09.004770[
   NOTICE] [20614] [162.158.227.133:13268:HTTP2-1#example.com] No request delivery
   notification has been received from LSAPI application, possible dead lock. 2022-
   05-26 17:33:09.004779 [NOTICE] [20614] [172.69.239.161:42358:HTTP2-1#example.
   com] No request delivery notification has been received from LSAPI application,
   possible dead lock. 2022-05-26 17:33:16.018509 [NOTICE] [20614] [172.70.188.87:
   30146:HTTP2-3#example.com] ExtConn timed out while processing. 2022-05-26 17:
   34:47.553338 [NOTICE] [20614] [172.70.219.62:38010:HTTP2-1#example.com] [STDERR]
   The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated
   since version 3.1. 2022-05-26 17:34:47.576466 [NOTICE] [20614] [172.70.219.62:
   38010:HTTP2-1#example.com] [STDERR] The Automattic\WooCommerce\Admin\API\Options::
   get_options function is deprecated since version 3.1.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [George Appiah](https://wordpress.org/support/users/gappiah/)
 * (@gappiah)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/php-dead-lock-error/#post-15694224)
 * > Basically it is your PHP code issue, not on web server side. You can debug 
   > your application code, it is out of our support scope.
 * It may be out of scope for the `web-server` software vendor (LiteSpeedTech), 
   but it’s still a server configuration issue. You’re hitting some limit/timeout
   on your server, and that can ultimately be fixed with a tweak in your server’s
   config.
 * I’ll recommend you reach out to your host for help.
 * If you’re using a self-managed server and can’t get any help from your host, 
   see if [**this response**](https://forum.openlitespeed.org/threads/possible-dead-lock-lsapi-application-help.4394/post-12373)
   from another WordPress user on the official OpenLiteSpeed support forum fixes
   your issue.
 * **NB:** If your hosting environment allows you to easily switch webservers, I’ll
   recommend you temporarily switch to another webserver (Apache, Nginx, etc) to
   see if the problem persists or not.
 *  Thread Starter [Vishal Lohar](https://wordpress.org/support/users/vlohar08/)
 * (@vlohar08)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/php-dead-lock-error/#post-15694519)
 * I understand!
    It looks like I will have to figure it out by myself. Tried few
   forum suggestions and I will debug it to find it works or not.
 * Thanks!
 *  Thread Starter [Vishal Lohar](https://wordpress.org/support/users/vlohar08/)
 * (@vlohar08)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/php-dead-lock-error/#post-15707846)
 * I have made the following changes to fix this issue.
 * Modified PHP settings in Litespeed web console.
 *     ```
       Max Connections: 50
       Environment: PHP_LSAPI_CHILDREN=50
                    PHP_LSAPI_MAX_REQUESTS=500
                    LSAPI_PGRP_MAX_IDLE=10
                    LSAPI_AVOID_FORK=1
       Initial Request Timeout (secs): 60
       Connection Keep-Alive Timeout: 60
       Memory Soft Limit (bytes): 4024M
       Memory Hard Limit (bytes): 4024M
       Process Soft Limit: 2400
       Process Hard Limit: 2500
       ```
   
 * Also, In server configuration set CPU Affinity to 1. And disable Gzip compression
   if you are facing any database memory full errors.
    An alternate fix for database
   memory full error is to increase your temporary file storage size.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘PHP Dead lock error’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 2 participants
 * Last reply from: [Vishal Lohar](https://wordpress.org/support/users/vlohar08/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/php-dead-lock-error/#post-15707846)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
