Upgrade to 5.1.13 from quite an old version?

Discussion in 'Install/Configuration' started by PSS, Feb 17, 2017.

  1. PSS

    PSS Well-Known Member

    Re: https://www.litespeedtech.com/support/forum/threads/lsws-5-1-13-released.14663/#post-96407

    What are the "focused DDoS attacks detected just a few hours ago" ?

    I have run a server with an older PHP version and older Litespeed (very stable), so now if I update it to 5.1.13 should all go fine without need to update php or something else, will there be any implications?

    LS Enterprise v4.2.21
    PHP 5.6.1 (litespeed) (built: Oct 5 2014 17:48:51)
     
  2. Pong

    Pong Well-Known Member Staff Member

    should be no problem on php configuration. since you have a very old version,
    To be safe, may try
    /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.19
    then
    /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.13
     
  3. PSS

    PSS Well-Known Member

    Thanks,
    Can I revert to the old version (5.x -> 4.x) at all after getting to 5.x, in case there are problems ?
     
  4. mistwang

    mistwang LiteSpeed Staff

    Yes, you can revert, no problem.
     
  5. PSS

    PSS Well-Known Member

    All seems to work fine, but there is this in the log:
    NOTICE #_AdminVHost:lsapi] [STDERR] PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /opt/lsws/admin/html.5.1.13/service/serviceMgr.php on line 23
     
  6. Pong

    Pong Well-Known Member Staff Member

    Is there any probelm to login to your LSWS Web Admin? If not, may not need to worry. Admin used to use different php binary to serve admin pages. If yes, we may need detailed steps to reproduce it.
     
  7. bobykus

    bobykus Well-Known Member

    What exactly was a target and how did you fix it? We are on 5.1.13 now and looks like our web servers are still affected.
     
  8. Pong

    Pong Well-Known Member Staff Member

  9. bobykus

    bobykus Well-Known Member

    Well,

    Looks like we were experiencing different kind of network issue, not related to the 5.1.13. I read you blog post and now I know what happened and what is fixed. Sorry for disturb you ;) All looks fine now.
     

Share This Page