LiteSpeed Enterprise just upgraded itself to Openlitespeed!

MarkD

Hi All

We have just had a situtation with our overnight apt updates where one of our LSE webservers "upgraded" itself to OLS.

To fix it, we used Enhance to switch to OLS (because Enhance thought it was still running LSE) and then switched back to LSE.

Whilst this did fix it, we are still seeing under Version manager that there is an "update" available to upgrade to 1.8.3 which is OLS!
Version

For context, we have had this server in production for over a year and I believe we originally had OLS installed for testing when we first spun it up but we switched to LSE within the first week of creating it so it has been running happily ever since.

Is this the first OLS upgrade that has been released since we all upgraded to v12 maybe and hence why we are only seeing the problem now?

I have just checked and removed all of the apt sources for OLS as our other servers, running the same software, were not showing those sources and now running apt update && apt upgrade is all clean and not trying to automatically upgrade LSE which is good!

Kosta

I always do this on LSE or OLS since V12 enhance even though they are not connected.
It’s recommended from lite speed.

If problems still exist, you can try removing all the files in the autoupdate folder and restarting LiteSpeed Web Server. The files in the autoupdate folder will be regenerated when your server checks for updates.

rm -rf /usr/local/lsws/autoupdate/*

MarkD

twest

MarkD wow that's really bizarre, at least you figured out a fix by removing the repos. Another issue with apt repos to worry about sheesh!

cPFence

MarkD

This likely happened because the LSE license check failed, could be due to a temporary outage, DNS issue, or a brief block, and the system automatically fell back to OLS. Might be worth checking the logs to pinpoint the exact cause.

Kosta

I think it’s because enhance doesn’t bother to update the versions into their package.
When enhance deploys lse is coming 6.0 version with some old files in auto update folder where they currently causing issues when we do try to update as most likely currently it’s some new kind of files codes required into auto update folder….

gmakhs

cPFence it's a bug in enhance and litespeed.
Enhance for some reason doesn't make good clean up if opsn litespeed was there so when litespeed is installed after , versions get mixed up .
I contacted litespeed about the issue but something is different on the setup and their solution didn't work, so I will be letting.enhsnce know

kelsallp

gmakhs Its nothing to do with cleanup - I have the same issue and this was a fresh version 12 install with Litespeed Enterprise.

AdamM

I had the same problem tonight... I was very surprised... Enhance team needs to look into this.

twest

AdamM did your affected server(s) have OLS installed previously? Is ols in the servers apt repo?

AdamM

twest I think yes.

twest

AdamM dang, I'm gonna have to double check all my servers repos. I'm sure I installed ols on one or two of them for testing at some point lol.

Aliysa_Enhance

Just a heads up to let you know that we're looking into this now - updates to follow

JohnB

Aliysa_Enhance Nice to see Enhance people actually engaging here 🙂 Now everyone is calm rather than speculating

twest

Strangely I couldn't find any OLS repos, but one server did have an ELS repo, which is strange because all the servers are setup the same way so IDK why the repo is there. Updates for ELS have always been run via the LS control panel, I think I prefer that method too.

On the plus side I did find some more repos to get rid of, like the one server I was testing netdata on still had its repo - don't need that breaking an enhance update some day. I think a quarterly repo check/cleanup is going to have to be added to our SOP, the repos have become too dangerous with Enhance to not keep a close eye on them.

gmakhs

twest I think eventually they need to short that out, we cant spent extra admin time for such issues

twest

Is everyone affected by this using cpfence? Wondering if it's related since there's a lot of talk about it iñ the cpfence thread.

MarkD

twest No, the server we had this happen on was running cpguard

gmakhs

twest someone mentioned cpfence said they run and apt update that maybe caused it .

In my opinion cpfence should disable auto updates and everything will be fine

cPFence

kelsallp

twest

Yes, running apt update seems to trigger the LSE upgrade automatically, but to clarify—cPFence doesn’t initiate or perform any webserver upgrades. We don’t touch your webserver binaries or packages. More info here.

kelsallp

I have had the same - using ELS, and using cpfence. All sites down from the same time as the cpfence update, and ELS has changed to OLS.

AdamM

On the server I had the problem with I also use cpfence.

kelsallp

appcd-cli change-webserver lite-speed

This fixed the problem for me - sites are back up as if nothing happened.

Still worried about the fact that the LS control panel is showing an available upgrade to 1.8.3 i.e. OLS.

xyzulu

See https://community.enhance.com/d/2692-litespeed-enterprise-just-upgraded-itself-to-openlitespeed/11

The only connection to cpfence is that apt update runs when cpfence update is pushed out… an OLS update was pushed out via apt, only Enhance can explain what happened here.

kelsallp

xyzulu The only connection to cpfence is that apt update runs when cpfence update is pushed out… an OLS update was pushed out via apt, only Enhance can explain what happened here.

True - need the answer from Enhance. It should be safe to run apt update.