Symptoms
After LiteSpeed has made a new release available, an update notification is not visible in the Web Console.
Description
The server checks once a day to see if a new version has been pushed to the autoupdate queue, and then sends a notification if one is found. The new available update will then appear within the Admin Console for you to upgrade to.
Update notifications are typically sent out by your server about a week after they officially published and announced at the LiteSpeed:
Most often, if you are not yet seeing the new version as available, you'll just need to wait until the update is made available to your server. If it's been multiple days past a week since the update was officially published and announced, the update notification on your server might not be working due to an issue with the files under the following directory:
/usr/local/lsws/autoupdate/
Use the resolution below if you suspect that you should see an update notification in your Admin Console, but it is not there.
Resolution
Option #1 - Regenerate files within the lsws autoupdate directory
- Login to the server via SSH as the root user
- Create a backup of the autoupdate directory:
cp -rv /usr/local/lsws/autoupdate /root/lsws-autoupdate-backup$(date +.%Y-%b-%d-%H-%M-%S)
- Remove the .last file:
rm /usr/local/lsws/autoupdate/.last
- Hard restart LiteSpeed by executing the following commands on the same line but separated by a semicolon:
/scripts/restartsrv_apache --stop; /scripts/restartsrv_apache --start
- If that does not resolve the issue, you may try removing all of the files within the autoupdate directory. However, be careful not to delete the directory its self:
rm /usr/local/lsws/autoupdate/*
- Again Restart LiteSpeed:
/scripts/restartsrv_apache --stop; /scripts/restartsrv_apache --start
Option #2 - Manually Upgrade via the Command Line
- Login to the server via SSH as the root user
- Run the following command:
/usr/local/lsws/admin/misc/lsup.sh -f -v <version>