Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the copy-the-code domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pb-seo-friendly-images domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the johannes domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121
No request delivery notification has been received from LSAPI application, possible dead lock. - PC✗3
No request delivery notification has been received from LSAPI application, possible dead lock.

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

On a small VPS runing CyberPanel and NextCloud the NextCloud pages were loading forever. When checking the cyberpanel error log the following error stood out:

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

image 3 1024x498 - No request delivery notification has been received from LSAPI application, possible dead lock.

After restarting the LiteSpeed service, NextCloud started loading but after a few minutes failed again with the same error. upon rechecking the error log again, I noticed that the LSWS service upon restart re-creates swap file and unlocks pid file [/tmp/lshttpd/lsphp.sock.pid]

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

but when going to the /tmp/lshttpd folder the last modified date wasn’t changed, indicating that for some reason (permissions) LiteSpeed failed to recreate them. For a quick fix, instead of changing the permissions, simply stop litespeed web service, rename the directory and restart litespeed. That way Litespeed recreates the entire lshttpd folder in /tmp.

service litespeed stop
mv /tmp/lshttpd/ /tmp/lshttpd1/
service litespeed start
whoami
Stefan Pejcic
Join the discussion

I enjoy constructive responses and professional comments to my posts, and invite anyone to comment or link to my site.