Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
litespeed_wiki:licenses:transfer-or-release-a-license [2018/11/26 16:53] Kacey Schroeder [How to Release Existing License] |
litespeed_wiki:licenses:transfer-or-release-a-license [2021/02/11 16:48] (current) Jackson Zhang |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| To migrate your current license: | To migrate your current license: | ||
| - | - back up your current serial.no and license.key under lsws/conf. | + | - back up your current serial.no and license.key under /usr/local/lsws/conf/. |
| - | - Verify your current license on the old server. You can use it to check whether you need to migrate your license after your hardware upgrade.<code>old_server:lsws/bin/lshttpd -V </code> | + | - Verify your current license on the old server. You can use it to check whether you need to migrate your license after your hardware upgrade.<code>old_server:/usr/local/lsws/bin/lshttpd -V </code> |
| - | - Migrate the license from your old server. <code>old_server:lsws/bin/lshttpd -m</code> | + | - Migrate the license from your old server. <code>old_server:/usr/local/lsws/bin/lshttpd -m</code> |
| - | - Verify your migrated license in your old server, you should have 3 days overlap for a smooth transition. LSWS process on your old server will automatically shut down after 3 days, so make sure you are ready to register for the new license when you ready to migrate.<code>old_server:lsws/bin/lshttpd -V</code> | + | - Verify your migrated license in your old server, you should have 3 days overlap for a smooth transition. LSWS process on your old server will automatically shut down after 3 days, so make sure you are ready to register for the new license when you ready to migrate.<code>old_server:/usr/local/lsws/bin/lshttpd -V</code> |
| - In your new server, or the same server after hardware upgrade, register a new license. Assume you already copied over the same directory over. | - In your new server, or the same server after hardware upgrade, register a new license. Assume you already copied over the same directory over. | ||
| - | * Before you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". Also make sure you have "serial.no" in lsws/conf already. If there is no "serial.no" file there, you should create one and place your serial no into that file before you run "-r": <code>new_server:lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under lsws/conf or lsws/). | + | * Before you run "-r" option, make sure there is no other license related files in the /usr/local/lsws/ and /usr/local/lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". Also make sure you have "serial.no" in /usr/local/lsws/conf already. If there is no "serial.no" file there, you should create one and place your serial no into that file before you run "-r": <code>new_server:/usr/local/lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under /usr/local/lsws/conf or /usr/local/lsws/). |
| * If your new license key is not in the lsws/conf, move the new license.key and serial.no to lsws/conf. <code>new_server:mv lsws/license.key conf/</code> Usually this step is not necessary. | * If your new license key is not in the lsws/conf, move the new license.key and serial.no to lsws/conf. <code>new_server:mv lsws/license.key conf/</code> Usually this step is not necessary. | ||
| - | - Verify the license in your new server. <code>new_server:lsws/bin/lshttpd -V</code> | + | - Verify the license in your new server. <code>new_server:/usr/local/lsws/bin/lshttpd -V</code> |
| - | - If everything is ok, do a graceful restart. <code>new_server:lsws/bin/lswsctrl restart</code> | + | - If everything is ok, do a graceful restart. <code>new_server:/usr/local/lsws/bin/lswsctrl restart</code> |
| - Now your old and new copy will parallel run for 3 days, make sure your DNS will be refreshed by then. | - Now your old and new copy will parallel run for 3 days, make sure your DNS will be refreshed by then. | ||
| - In emergency situation, if you cannot make your production server online, you can temporarily apply a trial license and create a ticket with license department from client area. You can use "Release License" option as well. | - In emergency situation, if you cannot make your production server online, you can temporarily apply a trial license and create a ticket with license department from client area. You can use "Release License" option as well. | ||
| - | * If you changed your mind or plan after you did migration on the old server and haven't registered on the new server, you can continue to use the old server by registering a new key. After migration, your backed up license.key will no longer work. So just register a new one, because it has been migrated and allowed to register on any server including your old server. <code>old_server:lsws/bin/lshttpd -r</code> | + | * If you changed your mind or plan after you did migration on the old server and haven't registered on the new server, you can continue to use the old server by registering a new key. After migration, your backed up license.key will no longer work. So just register a new one, because it has been migrated and allowed to register on any server including your old server. <code>old_server:/usr/local/lsws/bin/lshttpd -r</code> |
| - | * When you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". | + | * When you run "-r" option, make sure there is no other license related files in the /usr/local/lsws/ and /usr/local/lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". |