Upgrade to 2.2.4 stopped server

[pcguru]

Hi!

I upgraded my server running 2.2.2 to 2.2.4 and guess what? The server never restarted.

Running /etc/init.d/lsws start gave no information at all, annoying.
Logs said absolutely nothing about starting/stopping. Last entry was the stopping before the first restart.

Running /$srv_root/bin/lswsctrl start told me this:

[ERROR] You are not authorized to use this binary, please purchase upgrades.
[ERROR] Failed to start lshttpd!

Actually I don't know for how long my license is valid since I'm not in charge of that, but this behaviour was a bit unexpected for an enterprise product.

Changing the three symlinks back to the 2.2.2 executables got the server back online.

Why did this happen? And is there anything else than changing the symlinks I need to do to ensure safe operation on the 2.2.2 release?

[xing]

The symlink is safe for production use. Future litespeed upgrades will modify the symlinks to the new version. Just make sure if and when you upgrade in the future, make sure the symlinks are proper in the bin directory as you have manually changed them.

The following messages:

[ERROR] You are not authorized to use this binary, please purchase upgrades.
[ERROR] Failed to start lshttpd!

Is something we are investigating right now. Please stay the course with 2.2.2 and we will fix this in a upadated release. Both 2.2.3 and 2.2.4 are very minor upgrades so should not affect your production stability when running 2.2.2.

[xing]

pcguru,

We have identified the license verification problem. 2.2.3+ version requre us to issue new licenses for those that purchased "owned" version of the license.

We will be notifying all our customers shortly to make this transition as smooth as possible.

If you like to accelerate this process of your company, email me at xing@litespeedtech.com directly.