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

[Pouya Darabi]

Hi

my openlitespeed logs is full of this error!

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

what is wrong?

openlitespeed version 1.3.12

[Pouya Darabi]

any solution?
I upgraded litespeed to 1.4.13

but my logs are full of these errors!

[David]

I now can reproduce it. I will fix it soon.
Thanks for your feedback.

On 11/1/2015 5:06 PM, Pouya Darabi wrote:

any solution?
I upgraded litespeed to 1.4.13

but my logs is full of these errors!

--
You received this message because you are subscribed to the Google Groups "OpenLiteSpeed Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlitespeed-deve...@googlegroups.com.
To post to this group, send email to openlitespee...@googlegroups.com.
Visit this group at http://groups.google.com/group/openlitespeed-development.
For more options, visit https://groups.google.com/d/optout.

[David]

Sorry I replied a wrong email. O:-)
I can reproduced the LOG of [DEBUG] of the compreessbuf as below

[DEBUG] [modcompress---] compressbuf [-->] in 168, consumed: 168, written 10, flag in 0, buffer has 0.
[DEBUG] [modcompress---] compressbuf end of stream set.
[DEBUG] [modcompress---] compressbuf [-->] in 0, consumed: 0, written 115, flag in 3, buffer has 0.

And that one was fixed and patch was released to github.

Thanks.
David

[Kevin Fwu]

Hi Pouya,

As mentioned in the log, there was no request delivery notification received from the LSAPI.  This means that the PHP process got hung up on something.

Since it got hung up on both 1.3.12 as well as 1.4.13, it is likely a php script issue, but it could be from the server as well.

In order to properly diagnose the issue, please try the following steps:

- Turn on debug logging for OLS.

- run 'top' in a terminal.  Once it is up and running, try forcing the error to occur.  If you see 'lsphp5' at the very top using 100% cpu, it is likely a bug in the php script causing it to loop infinitely.

- run strace on the lsphp5 processes.

1. In a terminal, type ps aux | grep lsphp5 
2. The first number after the username are the process IDs. 
3. run strace with the process IDs.  ex strace -p 1402 -p 1403 -p 1404 -p 1405 for if I have four lsphp5 processes with pids 1402-1405.
4. Try to force the issue again.  
5. Once the issue occurs, check to make sure that all the processes are still outputting.  If one is no longer printing, it is likely stuck on a system call, which caused the debug message.

If neither of these options were the issue, could you please send us the debug log?  By default, it is at $SERVER_ROOT/error.log

If you don't want to attach the debug log here, you may email me the log.

Hope this helps,

Kevin