Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:lslb:installation [2017/10/20 18:59] Johathan Kagan |
litespeed_wiki:lslb:installation [2019/05/17 21:31] Kacey Schroeder [Upgrade] |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| - TCP port for web administration interface. | - TCP port for web administration interface. | ||
| - The "root" user has option to enable "chroot". The installer will setup the initial chroot environment automatically. We strongly recommend not enabling it unless you are familiar with "chroot". You can always enable it later with an upgrade installation. | - The "root" user has option to enable "chroot". The installer will setup the initial chroot environment automatically. We strongly recommend not enabling it unless you are familiar with "chroot". You can always enable it later with an upgrade installation. | ||
| - | - The "root" user can also choose to run LiteSpeed Load Balancer as a service which starts automatically at system startup. | + | - The "root" user can also choose to run LiteSpeed Load Balancer as a service which starts automatically at system startup. **"Would you like to have LiteSpeed Load Balancer started automatically when the machine restarts [Y/n]?"**, select "Y". If you miss this step during the installation, you can manually install the lslb.service startup script by running\\ ''/usr/local/lslb/admin/misc/rc-inst.sh'', then\\ ''chkconfig lslb on''. |
| ===== Testing ===== | ===== Testing ===== | ||
| - There are a couple of ways to control the server process. For detail information please see Administration Guide. To start the server, simply run ''[your_install_dir]/bin/lslbctrl start.'' | - There are a couple of ways to control the server process. For detail information please see Administration Guide. To start the server, simply run ''[your_install_dir]/bin/lslbctrl start.'' | ||
| - | - If the default port for normal web service was not changed during installation, point your browser to **http://[address]:8090/**, otherwise replace "8090" with actual port used. "[address]" should be the IP address or domain name of Load Balancer machine. Use "localhost" if it is accessed from the same machine. Load Balancer will try to route request to a default LiteSpeed Web Server installation on localhost, port 8088, if it does not work, try next step. If the default port for web administration interface is not changed during installation, point your browser to **http://[address]:7090/**, otherwise replace "7090" with actual port used. "[Address]" should be the IP address or domain name of your load balancer machine. Use "localhost" if it is accessed from the same machine. The welcome page of administration interface should be loaded, click "Log on" link and use the administrator's username and password specified during installation to log on. For detailed information regarding configuration, please refer to our Configuration Guide, or click "help" link on top of each page. | + | - If the default port for normal web service was not changed during installation, point your browser to **http://[address]:8090/**, otherwise replace "8090" with actual port used. "[address]" should be the IP address or domain name of Load Balancer machine. Use "localhost" if it is accessed from the same machine. Load Balancer will try to route request to a default LiteSpeed Web Server installation on localhost, port 8088, if it does not work, try next step. |
| + | - If the default port for web administration interface is not changed during installation, point your browser to **http://[address]:7090/**, otherwise replace "7090" with actual port used. "[Address]" should be the IP address or domain name of your load balancer machine. Use "localhost" if it is accessed from the same machine. The welcome page of administration interface should be loaded, click "Log on" link and use the administrator's username and password specified during installation to log on. For detailed information regarding configuration, please refer to our Configuration Guide, or click "help" link on top of each page. | ||
| - If your server uses firewall, please make sure that localhost is trusted. For instance, Linux with IPTables should include a rule ''ALLOW INPUT from LO''. | - If your server uses firewall, please make sure that localhost is trusted. For instance, Linux with IPTables should include a rule ''ALLOW INPUT from LO''. | ||
| - If the web administration interface is inaccessible either, please take a look at the error log - ''[your_install_dir]/logs/error.log'' | - If the web administration interface is inaccessible either, please take a look at the error log - ''[your_install_dir]/logs/error.log'' | ||
| Line 51: | Line 52: | ||
| * A new release is available | * A new release is available | ||
| * Upgrade from a trial license to production license | * Upgrade from a trial license to production license | ||
| - | * Upgrade production license from N CPU to M CPU license. | + | * Upgrade production license from an N worker processes to a M worker process license. |
| The built-in update agent will check new release periodically and automatically download new package and send email notification about the new release. Server upgrade can be performed via the web admin interface by clicking the upgrade link in the version management page. | The built-in update agent will check new release periodically and automatically download new package and send email notification about the new release. Server upgrade can be performed via the web admin interface by clicking the upgrade link in the version management page. | ||