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:php:detached_mode [2018/09/17 20:38]
Jackson Zhang [PHP Auto Configuration for Different Control Panels]
litespeed_wiki:php:detached_mode [2018/10/28 16:50]
George Wang [For a User]
Line 27: Line 27:
   touch <​user_home_dir>/​.lsphp_restart.txt   touch <​user_home_dir>/​.lsphp_restart.txt
   ​   ​
 +To make it compatible with CloudLinux mod_lsapi CRIU feature, server will restart PHP by ''​mod_lsapi_reset_me''​ as well 
 +  ​
 +  touch <​user_home_dir>/​mod_lsapi_reset_me
 +
 The user can also restart detached PHP processes from the '​Advanced'​ page of the [[litespeed_wiki:​cpanel:​cpanel-plugin|LiteSpeed Web Cache Manager cPanel plugin]], accessible from within their cPanel dashboard. The user can also restart detached PHP processes from the '​Advanced'​ page of the [[litespeed_wiki:​cpanel:​cpanel-plugin|LiteSpeed Web Cache Manager cPanel plugin]], accessible from within their cPanel dashboard.
  
Line 46: Line 50:
  
 ===== PHP Auto Configuration for Different Control Panels ===== ===== PHP Auto Configuration for Different Control Panels =====
-In previous ​version lower than LSWS 5.2.x, ​there is a "​External App" section to setup PHP external apps and a "​Script Hander"​ section to setup PHP handlers. ​+In previous ​versions of LSWS (5.2.x and earlier), external apps and PHP handlers ​are set up via the **External App** and **Script Hander** sections, respectively.
  
 {{ :​litespeed_wiki:​php:​lsws5.3-php-detached-mode-php-externalapp.png?​800 |}} {{ :​litespeed_wiki:​php:​lsws5.3-php-detached-mode-php-externalapp.png?​800 |}}
  
-On LSWS 5.3,  PHP external app and PHP script handler ​configurations are not required ​anymore ​and they will be autoconfigured by the web server. If you run upgrade from 5.2.x or previous ​version, external apps settings will be carried over. Actually ​you can delete all PHP external apps and PHP handlers and LSWS will still be working ​fine. If you install a new fresh LSWS 5.3 installation,​ most likely you won't see any PHP external apps and PHP handlers defined there anymore. If you see such, don't worry and it is normal for LSWS 5.3. If you still want to define external apps manually, it is ok, and LSWS will honor the settings which actually override the LSWS 5.3 built-in external apps definition. ​+On LSWS v5.3 and abovethese configurations are no longer ​required. External apps and script handlers ​will be autoconfigured by the web server. If you upgrade ​to v5.3 from an earlier ​version, ​the external apps settings will be carried over. (However, ​you could delete all PHP external apps and PHP handlers and LSWS would still work fine.)
  
-LSWS 5.3 auto-detects ea-php and alt-php ​handlers. ​Currently, it auto-detects up to 7.Two handlers: application/​x-httpd-ea-php71 and application/​x-httpd-alt-php71 are now pointing ​to separate handlersprior to 5.3it all points to the lsphp71 handler configured+If you install a new fresh LSWS 5.3 installation,​ you probably won't see any PHP external apps or PHP handlers ​defined thereDon't worryThis is normalIf you still want to define external apps manuallyyou can do soLSWS will honor these settingsand they will override ​the built-in external apps definition
  
-How to configure PHP setting then if there are no external apps defined there anymore? While a new "​PHP"​ tab has been created in LSWS Web Admin Console ​and you can set configuration there to detached ​PHP.+Currently, ​LSWS auto-detects apps and handlers up to PHP 7.3. Two handlers: ''​application/​x-httpd-ea-php71''​ and ''​application/​x-httpd-alt-php71''​ now point to separate handlers, where prior to 5.3, both pointed to the lsphp71 handler configuration
  
-Configurations set under "​php" ​tab/<​phpConfig>​ section, ​is served ​as default for auto-detected PHP handler, so memory limit set there will apply to all detected PHP handlers. ​The explicitly configured PHP handler still use its own configuration.+So, how do you configure PHP settings if there are no external apps defined there anymore? See the new **PHP** tab in the Web Admin console to adjust the configuration. 
 + 
 +Configurations set under the **PHP** ​tab or in the ''​<​phpConfig>​'' ​section, ​serve as the default for auto-detected PHP handlers, so the memory limit set there will apply to all detected PHP handlers. ​An explicitly configured PHP handler ​will still use its own configuration.
    
 {{ :​litespeed_wiki:​php:​lsws5.3-php-detached-mode-php-tab.png?​800 |}} {{ :​litespeed_wiki:​php:​lsws5.3-php-detached-mode-php-tab.png?​800 |}}
Line 69: Line 75:
 Change the PHP binary path: Change the PHP binary path:
 {{ :​litespeed_wiki:​php:​lsws53-php-override2.png?​800 |}} {{ :​litespeed_wiki:​php:​lsws53-php-override2.png?​800 |}}
 +
 +
 +===== Troubleshooting =====
 +
 +  * [[litespeed_wiki:​php:​detached_mode:​handlers | Managing ea-phpxx and alt-phpxx differences between LSWS v5.3 and previous versions]]
 +
  • Admin
  • Last modified: 2020/02/26 22:53
  • by Lucas Rolff