Failed to generate the realtime reports!

Discussion in 'Install/Configuration' started by DraCoola, Apr 29, 2009.

  1. DraCoola

    DraCoola Member

    Firstly, I suddenly got this :

    [​IMG]



    Secondly, I switch 4.0.2 to 4.0.1 in hoping to fix that error.

    Switched to 4.0.1.
    But still got that error and plus I cannot switch back to 4.0.2 again.
    I even cannot switch LSWS to Apache in order to reinstall this LSWS to 4.0.2.
    Stucked.
    In this stucked 4.0.1, LSWS cannot use to access https and cannot read files with 400 chmoded.

    Any help? George?
  2. mistwang

    mistwang LiteSpeed Staff

    /tmp is full I think. clean it up.
  3. DraCoola

    DraCoola Member

    whoa... you are right!
    but... how to do that safely?
    rm -rf * on /tmp ?

    Thank you
  4. mistwang

    mistwang LiteSpeed Staff

    I think it is safe to remove PHP session files, and /tmp/lshttpd/swap
  5. DraCoola

    DraCoola Member

    Your words is my command!
    I'll do that, George!
  6. DraCoola

    DraCoola Member

    Update

    Still stucked...
    Cannot switch back to 4.0.2 through WHM LSWS plugin :(
  7. DraCoola

    DraCoola Member

    still cannot switch to 4.0.2 and apache....
    still cannot access https....

    would you mind to help me to look at these issue...

    thank you!
  8. auser

    auser Super Moderator

    reinstall 4.02 may resolve the issue
  9. DraCoola

    DraCoola Member

    but reinstall needs to switch to apache first...
    while i still got :
    ----------------------------------------------------------------------
    "LiteSpeed Web Server Control Operation ... Switch to Apache

    LSWS is still running. Fail to stop within 30 secs

    LiteSpeed is still running! Failed to switch to Apache. Please try again!"
    -----------------------------------------------------------------------
  10. DraCoola

    DraCoola Member

    my clients are starting terrorize me by phone now...
    they cannot login to their forum and/or their member area on their websites....
  11. DraCoola

    DraCoola Member

    anyone know how to stop LSWS and then start apache manually from console?
    so then I can start to reinstal 4.0.2 immediately...

    thanks in advance.
  12. auser

    auser Super Moderator

    FYI:

    cd /usr/local/lsws/bin
    ./lswsctrl stop

    cd /usr/local/apache/bin
    ./apachectl start
  13. DraCoola

    DraCoola Member

    Thank you auser,

    But still LSWS forcing to start as the only webserver.
    Code:
    root@medusa [/tmp]# cd /usr/local/lsws/bin
    root@medusa [/usr/local/lsws/bin]# ./lswsctrl stop
    [OK] lshttpd: stopped.
    root@medusa [/usr/local/lsws/bin]# cd /usr/local/apache/bin
    root@medusa [/usr/local/apache/bin]# ./apachectl start
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    [OK] Send SIGUSR1 to 24651
    /usr/local/apache/bin/httpd: line 38: 0=0: command not found
    root@medusa [/usr/local/apache/bin]#
    
  14. DraCoola

    DraCoola Member

    is there any other way to stop this LSWS?
    does just kill LSWS pid will safe to do?

    can't hold any longer... thank you...
  15. mistwang

    mistwang LiteSpeed Staff

    Just do

    killall -9 lshttpd

    then

    try restart LSWS see if it fix itself.
  16. anewday

    anewday Moderator

    Set "Auto Reload On Changes" to NO in the admin console and do:

    service lsws stop
    service httpd start
    service httpd restart
  17. DraCoola

    DraCoola Member

    The fixing steps are :

    1. killall -9 lshttpd
    2. restart LSWS <--- not fix it self
    3. again, killall -9 lshttpd
    4. start Apache
    5. reinstall 4.0.2 from scratch

    pheww...

    thanks for all helps, really appreciated :)
  18. mistwang

    mistwang LiteSpeed Staff

  19. DraCoola

    DraCoola Member

    Actually, the main problem that pushed me to run easyapache and then re-setting LSWS is : the cpu load.
    Switch to LSWS makes CPU spike randomly to 40-50 from 2.x - 3.x
    I don't know what caused this.

    Just spikes quickly to 10-20-30-40-50... and then go down to 2.x - 3.x again.
    In next couple minutes the CPU load go to super high again and again and again....

    Anyone has the same issue?
  20. DraCoola

    DraCoola Member

    The CPUs are getting wild again....

    [​IMG]

    :(

Share This Page