Installed OLS through repository then updated through lsup.sh for debug

[Colcol]

Hi forum

Newbie questions about installing/upgrading/downgrading OLS for debug purposes.

KB states not to mix up OLS installation and subsequent upgrade methods:

https://openlitespeed.org/kb/how-to-upgrade-openlitespeed/
"In order to avoid complications, always upgrade or downgrade using the same method you used to install OpenLiteSpeed originally.

Please don’t use the lsup.sh script if you installed OLS through the LiteSpeed repository. In that case, you should continue to use package management commands to upgrade OLS."

But to identify a bug, KB says to install GDB and then rebuild OLS through lsup.sh.

https://openlitespeed.org/kb/submit-openlitespeed-bug-report/
"If the call stack information does not show up here, please install GDB first, followed by an OLS debug build:
yum install gdb
/usr/local/lsws/admin/misc/lsup.sh -b -s -v <version>"

If OLS is installed initially through the Litespeed repository and then upgraded through lsup.sh, then what complications exactly are likely to occur?

I installed OLS initially through the Litespeed repository, then rebuilt through lsup.sh for debug purposes, and then reverted back to the standard OLS through lsup.sh -v <version>.

Everything now seems to be working ok at the moment, but will problems occur when I try to update OLS through the Litespeed repository next time? Or will other problems occur in due course? Any ideas?

 

[Cold-Egg]

I just tested it on a test server, I don't think there will be an issue with OLS, feel free to give it a try.

 

[Colcol]

I just tested it on a test server, I don't think there will be an issue with OLS, feel free to give it a try.

Thanks. Will give it a try when apt update indicates a new version of OLS.

In the meantime, OLS seems fine having installed initially through the package manager and then debugged/updated through lsup.sh

I am guessing the "complications" cited in the KB...

https://openlitespeed.org/kb/how-to-upgrade-openlitespeed/
"In order to avoid complications, always upgrade or downgrade using the same method you used to install OpenLiteSpeed originally.

...could perhaps relate to the version of OLS known by the package manager becoming out-of-step with the OLS version running through an lsup.sh update?