delivery notification

Discussion in 'General' started by Dani, Nov 20, 2007.

  1. Dani

    Dani New Member

    hey I'm getting loads of these now with the new 3.3 release

    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.
    2007-11-20 20:08:22.012 [NOTICE] No request delivery notification has been received from LSAPI process:-2, possible run away process.



    any way to know what it is? Without really using heavy debug loading on a live server? :)
  2. mistwang

    mistwang LiteSpeed Staff

    You do not need to worry about it if there is no "oops" "503" errors in the log.
    It is normal when a user cancel a request in the middle, but the PHP process is till processing it, then the PHP process was assigned to another request. Eventually, the PHP process will be restarted if won't respond.
    Last edited: Nov 20, 2007
  3. Dani

    Dani New Member

    ok guess i'll have to stop using info logging then :) thx mistwang

Share This Page