Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
litespeed_wiki:cpanel:multi-litespeed-processes [2019/03/07 18:50]
Jackson Zhang
litespeed_wiki:cpanel:multi-litespeed-processes [2019/05/16 21:02]
Kacey Schroeder
Line 1: Line 1:
-====== How to Use More Cores With a 2-CPU or Above License on cPanel ======+====== How to Use More Cores With License ​with at Least 2 Worker Processes ​on cPanel ======
  
 ===== Setup to use multicores ===== ===== Setup to use multicores =====
-You can boost your website'​s benchmark performance by selecting a higher-CPU license. If you have a 2-CPU or above license ​on cPanel, you can check how many LiteSpeed processes are running in "​top"​. Sometimes you may only see one core being used by LiteSpeed processes. Why?+You can boost your website'​s benchmark performance by selecting a higher-CPU license. If you have a license with worker processes ​or more on cPanel, you can check how many LiteSpeed processes are running in "​top"​. Sometimes you may only see one core being used by LiteSpeed processes. Why?
  
-Websites configured via Apache configuration,​ such as in a cPanel environment,​ are served by one CPU by default. You can add a listener for a site's ''<​IP : Port>''​ in LiteSpeed'​s native configuration. Bind it to two processes to fully utilize the 2-CPU license (or more) in your benchmark test. +Websites configured via Apache configuration,​ such as in a cPanel environment,​ are served by one CPU by default. You can add a listener for a site's ''<​IP : Port>''​ in LiteSpeed'​s native configuration. Bind it to two processes to fully utilize the 2 worker process ​license (or more) in your benchmark test. 
  
 The following shows how to enable two processes for your website for port 80.  Select the IP that is used by your benchmark-testing domain associated with the virtual host.  ​ The following shows how to enable two processes for your website for port 80.  Select the IP that is used by your benchmark-testing domain associated with the virtual host.  ​
Line 17: Line 17:
  
 ===== Troubleshooting ===== ===== Troubleshooting =====
-==== Full stop/start ==== +==== Full Stop/Start ==== 
-If you see "failed to create new listener",+If you see ''​failed to create new listener''​,
   2019-03-07 11:​17:​32.583428 ​   ERROR    HttpListener::​start():​ Can’t listen at address https: Address already in use!   2019-03-07 11:​17:​32.583428 ​   ERROR    HttpListener::​start():​ Can’t listen at address https: Address already in use!
   2019-03-07 11:​17:​32.583462 ​   ERROR    HttpServer::​addListener(https) failed to create new listener   2019-03-07 11:​17:​32.583462 ​   ERROR    HttpServer::​addListener(https) failed to create new listener
   2019-03-07 11:​17:​32.583471 ​   ERROR    [config:​server:​listener:​https] failed to start listener on address *:443!   2019-03-07 11:​17:​32.583471 ​   ERROR    [config:​server:​listener:​https] failed to start listener on address *:443!
  
-mostly ​likely you run a graceful restart. You should ​run a full stop then full start to make the setting effective.+most likely you ran a graceful restart. You should ​bring the server to a full stop, and run a full restart ​to make the setting effective. ​Like so: 
   service lsws stop   service lsws stop
   service lsws start   service lsws start
   ​   ​
-==== failed ​to create ​SSL context ​for listener ​==== +==== Failed ​to Create ​SSL Context ​for Listener ​==== 
-Even you run full stop then full start, you may see the following warning message:+Even if you run full stop then full start, you may see the following warning message:
   LEVEL: WARN [config:​server:​listener:​https] failed to create SSL context for listener 208.75.148.57:​443,​ turn SSL off.   LEVEL: WARN [config:​server:​listener:​https] failed to create SSL context for listener 208.75.148.57:​443,​ turn SSL off.
    
-Try to browse the domain ​without any issue. Use top command to check and litespeed ​processes ​shared ​CPU equally without any issue.+Verify that you can browse ​to the domain ​successfully. Use the ''​top'' ​command to check that LiteSpeed ​processes ​are sharing ​CPU equally without any issue.
  
-The error message simply means the ssl is not configured through WebAdmin ( which is actually true, since LSWS will use apache ssl configuration) and Apache ​config ​will fill in the SSL cert.  The error message can be safely ignored as long as SSL is working fine.    ​+The error message simply means the SSL is not configured through WebAdmin (which is actually true, since LSWS will use Apache'​s SSL configuration) and that the Apache ​configuration ​will fill in the SSL certificate.  The error message can be safely ignored as long as SSL is working fine.    ​
  • Admin
  • Last modified: 2019/05/16 21:02
  • by Kacey Schroeder