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:whm-plugin-cache-manager-error-status [2019/02/04 21:41]
Lisa Clarke [Unexpected Error Encountered! See webcachemgr.log for more information] Proofreading
litespeed_wiki:cpanel:whm-plugin-cache-manager-error-status [2020/01/02 15:51]
Michael Alegre [Fatal Error Encountered During Action Execution]
Line 14: Line 14:
 **Cause:** This most commonly indicates that the installation is invalid in some way, such as a broken backup/​testing installation that was detected during scan. **Cause:** This most commonly indicates that the installation is invalid in some way, such as a broken backup/​testing installation that was detected during scan.
  
-**Resolution:​** Most of the time these installations can be ignored without issue. In the rare case where an installation is working as expected but is still detected with this error, please [[#​still_need_help|contact our support team]] for further investigation.+**Resolution:​** Most of the time these installations can be ignored without issue. In the rare case where an installation is working as expected but is still detected with this error, ​please running command ''​lsws/​admin/​misc/​lscmctl --update-lib''​ and trying again. If this still does not resolve the issue please [[#​still_need_help|contact our support team]] for further investigation.
  
 ===== Timeout Occurred During Action Execution ===== ===== Timeout Occurred During Action Execution =====
Line 78: Line 78:
  
 The cPanel MultiPHP Manager showed PHP 7.2 (alt-php72) was set to the system default PHP version, and all accounts inherited it. It appeared something was wrong with alt-PHP72 in this case. Changing the default to ea-php72 solved the problem, and all LiteSpeed Cache enabling errors disappeared.  ​ The cPanel MultiPHP Manager showed PHP 7.2 (alt-php72) was set to the system default PHP version, and all accounts inherited it. It appeared something was wrong with alt-PHP72 in this case. Changing the default to ea-php72 solved the problem, and all LiteSpeed Cache enabling errors disappeared.  ​
 +===== Could not include missing file =====
 +  /​home/​user/​public_html - Could not include missing file /​home/​user/​public_html/​wp-load.php.
  
 +=====  Could not find matching document root =====
 +  /​home/​user/​public_html/​blog_old - /​home/​user/​public_html/​blog_old - Could not find matching document root for WP siteurl/​servername example.com.
 +
 +===== Unexpected Error Encountered! Error establishing a database connection =====
 +  /​home/​user/​public_html - Unexpected Error Encountered! Error establishing a database connection.
 +
 +===== Detected WordPress version as x.x. Version 4.0 required at minimum =====
 +  /​home/​user/​public_html/​example.com - Detected WordPress version as 3.4. Version 4.0 required at minimum.
 +
 +===== Undefined variable: wp_version =====
 +  /​home/​user/​public_html/​__MACOSX - Notice: Undefined variable: wp_version in /​usr/​local/​lsws/​add-ons/​webcachemgr/​src/​WPCaller.php on line 1145 Notice: Undefined variable: wp_version in /​usr/​local/​lsws/​add-ons/​webcachemgr/​src/​WPCaller.php on line 1146 Detected WordPress version as . Version 4.0 required at minimum
 ===== Still Need Help? ===== ===== Still Need Help? =====
  
 If you are still running into issues after learning about the cases above, please [[https://​www.litespeedtech.com/​support|contact our support team]] for further assistance. If you are still running into issues after learning about the cases above, please [[https://​www.litespeedtech.com/​support|contact our support team]] for further assistance.
  • Admin
  • Last modified: 2021/10/06 15:19
  • by Lisa Clarke