LiteSpeed compatibility issue with cPanel > cPanel blocking LiteSpeed

Discussion in 'Install/Configuration' started by vivek, Mar 2, 2008.

  1. mistwang

    mistwang LiteSpeed Staff

    Maybe cPanel restarts LSWS more frequently. Load will be higher during restart. There is no other changes that could result in higher load.
  2. mistwang

    mistwang LiteSpeed Staff

    Probably later today, or tonight.
  3. aww

    aww New Member

    Question: given this new situation of cpanel killing other servers, is it save to rebuild apache while litespeed is running?

    I had to rename httpd back temporarily to even make easyapache run, it wanted to lookup the old version in the file and refused to run otherwise
  4. aww

    aww New Member

    second question: after I use easyapache to rebuild apache, apparently cpanel destroys whatever else is in the /usr/local/apache/bin folder

    is litespeed's wrapper going to notice that it's gone/missing and handle it or do I need to re-create the wrapper now?

    sigh...
  5. mistwang

    mistwang LiteSpeed Staff

    Please check the parameter log file at /opt/lsws/logs/ap_cmd_param.log.
    See what command parameter has been used by easyapache to check "httpd".
  6. aww

    aww New Member

    There's no such file in that directory.
    In fact all the file dates end with 2007

    I'm trying a find -name for it without luck.
  7. mistwang

    mistwang LiteSpeed Staff

    The path to the log file should be in the wrapper script. take a look.
  8. aww

    aww New Member

    There is no more wrapper script. It got wiped out since I did the easyapache rebuild and nothing has been put back in place.

    Strangely my server has been running fine for the past few days without any downtime without the wrapper. Maybe cpanel fixed the issue or maybe I've just been lucky and there have been no httpd restarts.
  9. aww

    aww New Member

    Oh duh. I know this is going to sound completely silly but I rarely go into the litespeed web admin panel and did not realize there were new options for the wrapper. That was completely left out of all the instructions ;)

    So I see the new monitoring option and wrapper and have set them correctly and now I see that litespeed has created the wrapper and renamed httpd to the bak file.

    I take it there is an extra step to switch back to apache now when desired - the httpd has to be renamed back manually?
  10. vivek

    vivek New Member

    Sorry to say ,but this wrapper is causing high server load, expecially when cpanel is doing httpd restart
  11. mistwang

    mistwang LiteSpeed Staff

    Yes, the load will be higher when LiteSpeed restarts, as all PHP processes need to be restarted as well.
    However, cPanel do not use restart, it stop then start, then stop, start again, so it make the load even higher, I don't know why cPanel need to restart httpd multiple times.
  12. aww

    aww New Member

    Please note on upgrading to 3.3.9 I get this minor error:

    So I'm not sure what's trying to run the old script or what?
    Everything does work fine afterwards though...

Share This Page