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
Next revision Both sides next revision
litespeed_wiki:cpanel:multi-litespeed-processes [2018/08/08 19:43]
Jackson Zhang
litespeed_wiki:cpanel:multi-litespeed-processes [2019/03/07 21:24]
Lisa Clarke Copyediting
Line 1: Line 1:
 ====== How to Use More Cores With a 2-CPU or Above License on cPanel ====== ====== How to Use More Cores With a 2-CPU or Above License on cPanel ======
 +
 +===== 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 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?
  
Line 7: Line 9:
  {{ :​litespeed_wiki:​cpanel:​enable-litepeed-multi-processes-on-controlpanel.png?​800 |}}  {{ :​litespeed_wiki:​cpanel:​enable-litepeed-multi-processes-on-controlpanel.png?​800 |}}
  
-If you have multi IPs, you can use "​ANY"​ in IP field. Please keep in mind that if you need to switched ​between IP:port and ANY:port, you will need to have a full LSWS stop and start.+If you have multi IPs, you can use "​ANY"​ in "IP Address" ​field. Please keep in mind that if you need to switch ​between ​<​Individual ​IPand ANY, you will need to have a full LSWS stop and start.
  
 {{ :​litespeed_wiki:​cpanel:​multi-processes-443-1.png?​800 |}} {{ :​litespeed_wiki:​cpanel:​multi-processes-443-1.png?​800 |}}
Line 13: Line 15:
  
 It is normal that manually created listener(s) will not show in running in such control panel environment. It is normal that manually created listener(s) will not show in running in such control panel environment.
 +
 +===== Troubleshooting =====
 +==== Full Stop/Start ====
 +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.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!
 +
 +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 start
 +  ​
 +==== Failed to Create SSL Context for Listener ====
 +Even if you run a full stop then a 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.
 + 
 +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'​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: 2020/05/28 16:49
  • by Lisa Clarke